Use when auditing a site for accidental noindex directives, investigating why important pages are not appearing in Google Search, or reviewing CMS settings that control indexing at the page or category level.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
A page blocked from indexing cannot appear in search results, regardless of its content quality or backlinks. Accidentally blocking key landing pages, product pages, or blog posts is one of the most impactful technical SEO errors — often silently losing significant organic traffic.
noindex, robots.txt, or X-Robots-Tag headersFor each important page (homepage, key landing pages, product pages, top blog posts): (1) Check <meta name='robots' content='...'> — does it contain noindex? (2) Check X-Robots-Tag HTTP response header — does it contain noindex? (3) Check robots.txt — is the URL's path blocked by a Disallow rule? (4) In Google Search Console, use URL Inspection to confirm the page is indexed. Flag any important page with any form of noindex or robots.txt block.
<meta name='robots' content='noindex'>:
content='index, follow'.robots: { index: false } from the page's metadata.X-Robots-Tag: noindex HTTP header:
vercel.json headers configuration.A page that cannot be crawled or indexed cannot rank, no matter how good its content or how many links point to it. Google explicitly states that noindex and robots.txt blocks prevent pages from appearing in search results. Accidental indexing blocks are among the most common causes of sudden, unexplained drops in organic search traffic.
Parse every page's HTML for <meta name='robots'> or <meta name='googlebot'> tags containing noindex. Check HTTP response headers for X-Robots-Tag with noindex. Cross-reference with robots.txt Disallow patterns. Flag any route in the application where noindex is set unconditionally (rather than conditionally for draft/private content).
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/indexability
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
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.
日本語の概要は準備中です。原文の説明を表示しています。