Audit important pages for settings that interfere with search indexing, including noindex directives, HTTP headers, and robots.txt rules. Identify accidental restrictions, suggest configuration fixes, and guide follow-up checks in Google Search Console.
中文简介正在准备中。当前显示英语简介。
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.
安装前可以查看交给 AI 代理的指令内容。
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
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示英语简介。