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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
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
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when reviewing templates, rendered HTML, or shared components related to Create a custom 404 error page. Validate the final browser-facing markup, not just the source framework abstraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when auditing metadata, crawlability, structured data, or indexability related to Create a dedicated About page. Verify the rendered HTML and HTTP response rather than relying only on source files.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic table markup for screen readers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.
日本語の概要は準備中です。原文の説明を表示しています。