nosnippet directive: how it kills snippets and AI Overviews
A nosnippet or max-snippet:0 directive removes your search-result snippet — and with it, featured-snippet and AI-Overview eligibility. Find pages carrying it free and remove it unless suppression is intentional.
What it means
A page carries a nosnippet or max-snippet:0 directive — in the HTML <meta name="robots"> tag or an X-Robots-Tag HTTP header. Google will show the page's title in search results but no descriptive text beneath it. A functionally identical directive, max-snippet:0, has the same effect; max-snippet:150 would instead cap the snippet length rather than eliminate it.
Why it matters
The snippet is the primary text users read before deciding to click, so removing it depresses click-through on informational queries. More consequentially, Google builds AI Overviews, featured snippets and answer boxes from the same snippet-extraction mechanism nosnippet disables — a page with nosnippet cannot appear in an AI Overview no matter how well it answers the query. It is often accidental: a template copied from a paywalled page, an over-broad CMS plugin rule, or a test directive that was never reverted.
How to fix it
- Locate the directive: check the HTML
<head>(curl -s URL | grep -i robots) and the response headers (curl -I URL). - If it is in a
<meta>tag and unintentional, remove it or replace it withmax-snippet:150(a length cap) orindex, follow(no restriction). - If it comes from
X-Robots-Tag, update the server or CDN rule that injects the header. - Wait for Googlebot to recrawl — you cannot force snippet appearance via Search Console.
Example
<meta name="robots" content="index,nosnippet">
<!-- or the equivalent: -->
<meta name="robots" content="index,max-snippet:0"><meta name="robots" content="index,max-snippet:-1">
<!-- -1 = no snippet-length limit; or simply omit the directive -->nosnippet and max-snippet:0 both remove your search snippet AND make the page ineligible for featured snippets and AI Overviews. Remove them unless suppression is a deliberate choice.
When it's not a problem
nosnippet is appropriate for paywalled or subscription content, or legal/confidential documents published at a public URL but not meant for search consumption. For merely limiting snippet length, prefer a nonzero max-snippet:X over full suppression.
How Crawlinx detects it
We check the robots meta tag and X-Robots-Tag header for nosnippet or a max-snippet:0 directive (whitespace-tolerant). Either one suppresses the snippet, so the page is flagged.
How common is it?
44 audited sites in our corpus currently show this issue. The breakdowns below show which platforms, gatekeepers, verticals and countries are most exposed.
FAQ
- What does nosnippet do?
- It tells Google not to show any text snippet for the page in search results. It also removes the page from featured snippets and from AI Overview citations, which can cut click-through sharply.
- Is max-snippet:0 the same as nosnippet?
- Effectively yes — a maximum snippet length of zero means no snippet. Use max-snippet:-1 for no length limit, or a positive number to cap the snippet without removing it.
- When would I intentionally use nosnippet?
- For paywalled or sensitive pages where you don't want any text exposed in results. Otherwise it usually costs you clicks and AI-answer visibility for no benefit.
Related guides
Audit your own site — free
157 checks, internal PageRank, render-diff. No signup, results in ~30s.