noindex and AI Overviews

noindex is supposed to be applied intentionally. In practice it shows up by accident more often than any other indexing directive. Common culprits we have run into:

• Staging environment configuration that leaked to production. A Next.js or WordPress site ships with noindex on staging, the env-flag flips, but a static <meta name="robots" content="noindex"> stays in the head.
• CMS templates with a "private" toggle that defaults to noindex for new pages. A content editor forgets to flip it.
• The none shorthand. <meta name="robots" content="none"> is shorthand for noindex, nofollow. Many editors do not realize.
• X-Robots-Tag: noindex in a CDN rule for a path that grew to include important URLs.
• unavailable_after dates that have already passed. A page set to unavailable_after: 31-Dec-2024 becomes equivalent to noindex starting January 1.

Any of these will remove the page from AI Overviews silently. There is no warning, no Search Console alert until the page actually drops from results.

Find the directive

Check three locations in this order:

1. HTML meta tag:

   <meta name="robots" content="noindex">
   <meta name="robots" content="none">
   <meta name="googlebot" content="noindex">
   

2. HTTP response header (X-Robots-Tag):

   X-Robots-Tag: noindex
   X-Robots-Tag: googlebot: noindex
   

3. unavailable_after:

   <meta name="robots" content="unavailable_after: 31-Dec-2024 23:59:59 GMT">
   

The fastest way to find which one is firing on a live URL is Google Search Console's URL Inspection tool: it shows you exactly what Google saw. The free AI Overview Checker will also flag noindex from either source.

Remove it

If the page should appear in Search and AI Overviews, remove the directive entirely. Do not replace it with index, follow (that is the default; setting it adds noise without adding value).

If you have a real reason to keep some pages out of AI Overviews but in Search, noindex is not the right tool: it removes the page from Search entirely. Use nosnippet instead. That keeps the page in Search but removes it from AI features.

Verify

After removing the directive, request re-indexing via Search Console's URL Inspection tool, then wait. Indexing usually catches up within a few days. AI Overview eligibility returns once the page is back in the index.

• Setting noindex to "control" AI Overview appearance. It removes the page from Search entirely. Use nosnippet to keep Search but remove AI Overviews.
• Forgetting that <meta name="robots" content="none"> means noindex, nofollow. This catches teams that grep for "noindex" specifically and miss the shorthand.
• Leaving staging noindex in production. Always tie the directive to an environment variable, never hardcode in the template.
• Using noindex on category or filter pages by default. Sometimes those are the pages you most want cited (a well-curated category page can be the AI Overview source).