Audit pages excluded from search results by noindex directives in HTML or response headers. Check whether important products and articles are blocked by mistake, identify affected routes, and explain appropriate corrections.
Use when auditing metadata, crawlability, structured data, or indexability related to Audit all noindex pages. Verify the rendered HTML and HTTP response rather than relying only on source files.
Run score Not tested
See how to installReviews noindex directives that exclude pages from search results and checks whether they apply to the right pages. It examines meta tags and HTTP response headers to find important content, such as products and articles, that may have been excluded by mistake.
The review uses rendered HTML and actual HTTP responses, rather than judging from source files alone. It identifies affected URLs or templates and explains how to verify the page output after corrections.
Use it when reviewing settings for pages you want to appear in search results. It also helps check exclusion policies for admin and utility pages. When deciding how to control search visibility and crawling, it explains the distinction between noindex and the disallow rule in robots.txt.
noindex and check whether any product pages or articles are included.”Assessment requires checking rendered HTML and HTTP responses. Source settings alone do not establish what the page ultimately returns to search engines.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).
Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 23, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
An incorrect noindex tag can completely remove important pages from search results, while proper usage helps manage crawl budget and prevents duplicate content issues.
noindex directive in meta tags or headersnoindex is correctly applied to thin content, admin, or utility pagesVerify that the noindex directive is only applied to pages that should not appear in search results.
Remove <meta name="robots" content="noindex"> from pages that should be indexed and ranking.
Explain the difference between noindex and disallow in robots.txt and when to use each for optimal SEO.
Review metadata generation, rendered HTML, structured data, and response headers related to Audit all noindex pages. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/seo/all-noindex-pages
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
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.