Page Hidden From AI Overviews by nosnippet

Google documents nosnippet and max-snippet:0 as the way to opt a page out of its text snippet, and the same directive keeps the page out of AI Overviews and AI Mode answers. The page still ranks, so nothing about it looks wrong, and the directive is usually set once in an SEO plugin or a CDN rule and forgotten. Crawl Cove's ai-snippet-blocked check reports every indexable page that carries it and names where it is set.

What this finding means

The check reads all three places the directive can live, because they are fixed in different places:

• The <meta name="robots"> tag in the page HTML.
• The Google-only <meta name="googlebot"> tag, which is easy to miss when you have already checked the robots tag.
• The X-Robots-Tag response header, which is set by the server or CDN and never appears in view source.

A real finding quotes the carrier it found:

<meta name="robots" content="index, follow, nosnippet">

or

X-Robots-Tag: max-snippet:0

When more than one carrier sets it, the finding lists all of them and says so, because removing the directive from only one leaves the block in place. Only indexable pages are reported: a noindexed page is already out of every answer, and the noindex check owns that finding.

Why it matters

A page with no snippet still ranks, so the loss is invisible in ranking data. What changes is the result itself: it appears with no description, and Google will not quote it in AI Overviews or AI Mode, which is increasingly where the answer a searcher reads comes from. For paywalled or sensitive content that is the intended outcome. For an explainer, a comparison or a product page you want cited, it is a silent loss of visibility that no amount of content work recovers while the directive stays.

How to fix it

1. Decide whether the page should be quotable. If it is paywalled, legally sensitive or deliberately held back, leave the directive in place and move on; the finding exists to confirm the choice was made on purpose.
2. If it came from a meta tag, find the setting in your SEO plugin or page template. In most plugins it sits under the page's advanced robots settings as a "No Snippet" toggle or a snippet length field set to 0. Switch it off, or set the length to a positive value.
3. If it came from X-Robots-Tag, the fix is in server or CDN configuration:

# Apache (.htaccess): remove or edit a line like
Header set X-Robots-Tag "nosnippet"

# Nginx: remove or edit a line like
add_header X-Robots-Tag "max-snippet:0" always;

4. Remove it from every carrier the finding names. A page that sets it in both the robots tag and a header stays blocked until both are changed.
5. Re-crawl the page to confirm the directive is gone, then check the live result in Google. Snippets return on the next crawl of the page, not immediately.

False positives and edge cases

• A positive max-snippet value is not reported. max-snippet:160 limits the snippet length; it does not remove it, and Google can still quote the page.
• Noindexed pages are skipped on purpose. Reporting them here would describe a page as "hidden from AI Overviews" when it is hidden from search altogether; the noindex finding says that more accurately.
• The check does not judge intent. Paywalled and sensitive pages should carry this directive. The finding asks you to confirm each one, not to remove them all.
• Other engines read the directive differently. The check describes Google's documented behaviour. Bing and the AI crawlers that fetch pages directly have their own controls, which Crawl Cove's AI bot access check covers.

Related reading

Run any single page through the free AI search visibility checker, which reads the same nosnippet and max-snippet:0 directives alongside the robots.txt rules for each AI crawler. For which crawler is which and what blocking each one costs, see AI crawlers and robots.txt and the AI crawler user agents reference. For the opposite problem, where you want the richest result possible, see Featured snippets and rich results.