Skip to main content
Beta: Front-End Checklist is currently in beta. Some issues are still being fixed. Thanks for your patience.
SEOMedium

Audit all noindex pages

Lists and reviews all pages blocked from indexing to ensure critical content is accessible.

Utilities
Quick take
Typical fix time 10 min
  • Identify all pages using the `noindex` directive in meta tags or headers
  • Verify that critical pages (products, articles) aren't accidentally blocked
  • Ensure `noindex` is correctly applied to thin content, admin, or utility pages
Why it matters: An incorrect `noindex` tag can completely remove important pages from search results, while proper usage helps manage crawl budget and prevents duplicate content issues.

Rule Details

Regularly auditing your noindex directives ensures that you are only blocking pages that don't provide search value, such as staging environments, admin panels, or internal search results.

Code Example

<head>
  <!-- Use this for utility pages like 'Thank You' pages or internal search results -->
  <meta name="robots" content="noindex, follow">
  
  <!-- For pages that should be completely ignored -->
  <meta name="robots" content="noindex, nofollow">
</head>

Why It Matters

  • Visibility: Prevents accidental exclusion of high-value pages from Google and Bing.
  • Crawl Budget: Helps search engines focus their limited crawl resources on your most important pages.
  • De-indexing: Useful for removing outdated or sensitive pages from search results without deleting them.
  • Strategic Control: Allows you to manage which versions of content (e.g., filtered lists) are available for indexing.

Exceptions

  • Staging, utility, login, account, or internal search pages may intentionally use different crawl or index signals if they are not meant to rank.
  • Temporary migration states can produce noisy intermediate signals; flag the live production URL pattern, not one-off transition artifacts.
  • When redirects, canonicals, robots directives, or indexability signals conflict, fix the strongest final signal first instead of reporting every downstream symptom as a separate blocker.

Standards

  • Use these references as the standard for the final search-facing HTML, metadata, and crawl behavior.
  • Check the implementation against Google Search Central: Search Essentials before treating the rule as satisfied.
  • Check the implementation against Google Search Central documentation before treating the rule as satisfied.

Verification

Automated Checks

  • Inspect rendered HTML and HTTP headers to confirm the expected metadata or crawlability signal is present.
  • Test the affected URL with Google Search Console or equivalent tooling where relevant.
  • Re-crawl a representative page set after deployment.

Manual Checks

  • Confirm the change does not create conflicting canonical-url, robots, or structured-data signals.

Use with AI

Copy these prompts to use with your AI assistant, or install the MCP server to use directly from Claude, Cursor, or Windsurf.

Check

Verify implementation

Verify that the `noindex` directive is only applied to pages that should not appear in search results.

Fix

Auto-fix issues

Remove `&lt;meta name="robots" content="noindex"&gt;` from pages that should be indexed and ranking.

Explain

Learn more

Explain the difference between `noindex` and `disallow` in robots.txt and when to use each for optimal SEO.

Review

Code review

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.

Sources

References used to support the guidance in this rule.

Further Reading

Tools and supplementary material for exploring the topic in more depth.

Google Search Console
search.google.comTool

Rules that often go hand-in-hand with this one.

Avoid conflicting indexability signals

Detects conflicting signals between robots.txt, meta robots, X-Robots-Tag headers, and canonical tags

SEO
Robots Meta Conflict

Detects pages blocked by robots.txt that also carry noindex meta tags, creating a paradox where the directive is never read.

SEO
Make important pages indexable

Identifies important pages blocked from search engine indexing by noindex, robots.txt, or other directives

SEO
Schema + Noindex Conflict

Detects pages that carry rich result schema markup but are blocked from indexing via noindex or robots.txt.

SEO

Was this rule helpful?

Your feedback helps improve rule quality. This stays internal for now.

Loading feedback...
0 / 385