Review blog posts, landing pages, and guides for readability. Estimate reading difficulty, identify long sentences and jargon, and simplify wording and paragraph structure so broad audiences can follow the content more easily.
Use when reviewing content pages for user experience and SEO. Applies to blog posts, landing pages, how-to guides, and any long-form content intended for a broad audience.
Review the instructions the agent will receive before you install.
Content written beyond the reading level of the target audience increases bounce rates and reduces time-on-page—both engagement signals that correlate with search rankings.
Analyse this page's content for readability. Calculate or estimate the Flesch-Kincaid Grade Level. Identify sentences longer than 25 words, paragraphs longer than 4 sentences, instances of passive voice, and domain jargon that could be simplified. Report the estimated reading grade level.
Simplify the identified sentences and paragraphs: break long sentences at conjunctions, replace passive voice with active voice, substitute jargon with plain-language equivalents. Target a Flesch Reading Ease score of 60+ (Grade 8 or below for general audiences). Use subheadings to break up text every 200–300 words.
Readability measures how easy content is to understand. When content is written above the typical reading level of the audience, users leave faster (higher bounce rate) and spend less time reading (lower dwell time). These engagement signals influence search rankings indirectly. Clear writing also improves conversion rates and user satisfaction.
Extract the text content from the page body (excluding navigation, headers, footers). Calculate or estimate the Flesch-Kincaid Grade Level. Count: sentences longer than 25 words, paragraphs with more than 4 sentences, passive voice instances, and words with more than 3 syllables that could be simplified. Report the grade level and top 5 most complex sentences.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/reading-level
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create and review custom 404 pages that help visitors recover from broken or moved links through search and navigation. Check the rendered page and HTTP response so missing content returns a proper 404 status.
Audit or create a dedicated About page that explains a website’s purpose and identifies its people or organization. Review the rendered output and supporting information, including expertise and contact details, to find gaps.
Review and add automated accessibility checks for components, pages, and continuous integration workflows. Use axe-based tools to detect structural and attribute issues, while identifying checks that still need keyboard or screen reader testing.
Review sign-in, registration, multi-factor authentication, and account recovery for accessibility barriers. Find blocked paste, difficult code entry, and inaccessible backup methods, then suggest authentication paths that support password managers, autofill, or device approval.
Review form errors, success messages, and live updates so screen reader users receive important notifications. Check the HTML delivered to the browser, announcement settings, display duration, and dismissal controls, then identify specific elements that need changes.
Review HTML tables so screen reader users can understand how headers and data relate. Check header markup, table descriptions, and merged cells, then identify specific fixes and ways to verify them.