Nosnippet Directive Detection
stableCategory: content-structure · Methodology v4.5
friendly4AI looks for snippet-blocking directives in three places: the content of the <meta name="robots"> tag, the same attribute on <meta name="googlebot">, and the X-Robots-Tag response header.
Signal Source
- Source
https://{domain}- Kind
- html_dom
Score Bands
| Verdict | Condition |
|---|---|
| Pass | no restrictive snippet directives are found — no nosnippet and no max-snippet:0 in meta robots/googlebot or the X-Robots-Tag header |
| Partial | a global snippet restriction exists but data-nosnippet elements show granular control, OR a negative max-snippet value limits snippet length without fully blocking it |
| Fail | nosnippet or max-snippet:0 is present in meta robots/googlebot or the X-Robots-Tag header with no granular control |
Description
This parameter checks whether your page carries a nosnippet or max-snippet:0 directive that stops search engines and AI answer systems from quoting your content. The best outcome is the absence of any such restriction, which earns the top score.
What does this parameter measure?
friendly4AI looks for snippet-blocking directives in three places: the content of the <meta name="robots"> tag, the same attribute on <meta name="googlebot">, and the X-Robots-Tag response header. In each spot it searches for the nosnippet token and for max-snippet:0.
It also counts data-nosnippet attributes on individual elements. Those signal that an author is deliberately choosing which passages may be quoted, rather than blocking the whole page. Direction is what counts here: a clean page has no restrictions at all.
Why does nosnippet matter for AI-readiness?
A nosnippet directive or max-snippet:0 tells engines they may not show a text snippet of your page. AI answer systems that respect snippet controls then refuse to quote you, so your content drops out of generated answers even though the page is still crawled and indexed.
Most parameters measure something you forgot to add. This one is different: the failure is an active opt-out, and these directives suppress AI surfacing directly. Unless you meant to do that, leaving them in place quietly costs you visibility in the exact answers where you want to show up.
How is the score calculated?
Under the v4.5 methodology, this Content Structure parameter runs on a gradient where no restriction is the good result:
- Pass (100) — no
nosnippetand nomax-snippet:0directive in meta robots/googlebot or theX-Robots-Tagheader. Granulardata-nosnippetattributes by themselves don't lower the score. - Partial (50) — a global restriction exists, but either
data-nosnippetelements show the author is exercising granular control, or a negativemax-snippetvalue caps snippet length without fully blocking it. - Fail (0) —
nosnippetormax-snippet:0is set with no granular control.
These bands match the published rubric. Restrictive directives pull the score down, so removing them raises your AI-readiness.
How do I fix nosnippet issues?
- If you want broad AI visibility, strip
nosnippetandmax-snippet:0out of your meta robots/googlebot tags and yourX-Robots-Tagheaders. - Check the HTML meta tags and the response headers both. A directive set at the server level is easy to overlook.
- Need to hold back a few passages? Use per-element
data-nosnippetinstead of a global block, so the rest of the page stays quotable. - When you only want to cap snippet length, set a positive
max-snippetvalue (or leave it off) rather thanmax-snippet:0. - Re-scan and confirm that
meta_robots_nosnippetandx_robots_nosnippetboth report false in the evidence.
Related parameters: page metadata, AI opt-out signals, and structured data.
Version History
- Introduced
- v4.2
- Last changed
- v4.5
Key takeaways
- Signal: https://{domain}
- Category: Content Structure
- Passes when: no restrictive snippet directives are found — no nosnippet and no max-snippet…