Use when evaluating content pages for SEO quality. Applies to blog posts, product descriptions, landing pages, or any page expected to receive organic search traffic.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Google's Search Quality Rater Guidelines and Helpful Content system reward pages that demonstrate genuine expertise and fully satisfy user intent—low-quality pages are algorithmically suppressed site-wide.
Evaluate this page's content for E-E-A-T signals: Does it demonstrate first-hand experience or expertise? Does it fully answer the apparent search intent? Is the information accurate, specific, and supported by evidence? Is there meaningful depth beyond what competitors cover? Identify specific quality gaps.
Identify the primary search intent for this page. Rewrite or expand the content to: (1) fully satisfy that intent, (2) add specific details, examples, or data not found on competing pages, (3) attribute claims to authoritative sources, (4) add author byline with relevant credentials, (5) update any outdated information.
Google's ranking systems are designed to surface content that demonstrates Experience, Expertise, Authoritativeness, and Trustworthiness (E-E-A-T). Content that is generic, lacks depth, or does not fully answer user questions is classified as 'unhelpful' and deprioritised in rankings. High-quality content is the most durable long-term SEO investment.
Analyse the page content for quality signals: (1) Word count — is the topic covered in appropriate depth? (2) Specificity — are claims backed by data or examples? (3) Authorship — is a named author with credentials visible? (4) Freshness — does the page show a publication or updated date? (5) Sources — are external authoritative sources cited? (6) Originality — does the content offer unique insights not found on competing pages?
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。