Use when auditing robots meta tags. Applies to any important landing page, article, or product page that should appear with a description in search results.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Pages with nosnippet display without a description in search results, reducing click-through rates and making it harder for users to understand whether the result is relevant to their query.
Check the <meta name='robots'> tag and X-Robots-Tag response header for each important page. Flag any that contain 'nosnippet' or 'max-snippet:0'. Confirm these pages intentionally suppress snippets.
Remove 'nosnippet' from the <meta name='robots'> content attribute on important pages. Replace with 'max-snippet:-1' to explicitly allow full-length snippets, or simply omit snippet directives to use the default (allowed).
The nosnippet directive tells Google not to display a text snippet (description) for your page in search results. Without a snippet, users see only the page title and URL—this reduces click-through rates and is rarely the intended behaviour for content pages.
Check all pages for <meta name='robots' content='...'> tags. Parse the content value and flag any that include 'nosnippet' or 'max-snippet:0'. Generate a report of affected URLs, their page type, and whether the nosnippet directive is intentional. Also check X-Robots-Tag response headers.
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.
日本語の概要は準備中です。原文の説明を表示しています。