← Back to blog

Technical SEO · September 27, 2026 · 8 min read

Snippet Controls: max-snippet, nosnippet and data-nosnippet in the AI Answer Era

Google applies the same snippet directives to AI Overviews as to classic results — here is what each one removes, and the three cases where restricting pays.

By FluxWriter

Snippet controls are the only supported lever over what Google quotes from your page in an AI answer, and on most sites they were set once by a plugin default nobody read. The popular advice — wrap your best paragraph in data-nosnippet and force the click — gets the trade-off backwards. This guide covers what each directive removes, what it leaves alone, the audit that finds accidental settings, and the three cases where restricting pays.

Why Hiding Your Answer Doesn't Win the Click Back

The logic sounds airtight. If Google quotes your answer, the searcher has no reason to visit, so hide the answer and the visit comes back. It does not.

Snippets are not what earns the click — relevance is, and the snippet is how that judgement gets displayed. A result with no description sits beside a competitor with a clear one, and the searcher picks the one that says what they get. You have not removed the answer from the page. You have removed it from the shop window.

The AI answer version is harsher. Google's documentation states that all three directives apply to AI Overviews and AI Mode as well as classic results. Restrict the text and the generated answer is built from pages that did not — and those pages get the citation link.

Yours still ranks in the blue links underneath. Independent click studies through 2025 put the top result's loss at roughly a third to a half of its clicks under an AI Overview — measured across query sets, not your page, so treat it as a direction, not a forecast.

What Each Directive Actually Removes

Three controls, two levels. The robots meta tag carries two of them, and both govern the whole page. The third is an HTML attribute scoped to a single element.

nosnippet removes the text snippet and the video preview for the page. A static image thumbnail can still show. max-snippet caps the text at a number of characters — 0 behaves like nosnippet, -1 means no limit. data-nosnippet is different in kind. It goes on a span, div or section and removes only the text inside it, which stays indexed and still counts for ranking.

Here is what each one removes:

The last row is there because people reach for it by mistake. noindex is not a snippet control. It is a removal, and the page stops ranking within days. Title generation has no directive at all, and rich results from structured data follow their own rules — check the Rich Results Test after any change.

Where AI Overviews and AI Mode Fit In

Google runs its AI answers on the same index as classic search. There is no separate opt-out. Anything you do to keep your text out of an AI Overview removes it from the ordinary snippet too — Google's own guidance says as much, and every workaround people share depends on pretending otherwise.

The confusion comes from Google-Extended. It is a robots.txt token that governs whether your content trains or grounds Gemini as a product, and Google is explicit that it has no effect on Search — AI Overviews and AI Mode included. Sites that blocked it in 2023 expecting to vanish from AI Overviews in 2024 did not.

Other engines are a separate decision. ChatGPT, Perplexity and Claude fetch with their own crawlers, managed in robots.txt rather than snippet tags. Bing honours the page-level meta directives, though data-nosnippet is a Google attribute with no documented equivalent there, and how far any of it reaches into Copilot answers is undocumented — plan on it not helping.

max-snippet has a quieter effect too. Featured snippets typically run 40–60 words, roughly 250–350 characters. There is no published threshold, but a cap below that range takes the page out of contention for the box at the top, and probably out of AI answer extraction too, though Google has not said so.

The Plugin Defaults You Inherited

If your site runs Yoast or Rank Math, your pages already carry max-snippet:-1, max-image-preview:large, max-video-preview:-1 on every URL. Both plugins have shipped that line by default since roughly 2020. It is the right setting for almost everyone, so the audit question is rarely "what should I add" — it is "who changed it".

The directives exist because of publishers, not SEOs. Google introduced the max-* controls in September 2019, weeks before France's version of the European copyright directive took effect, and for a period showed French press results as bare titles until publishers opted back in. That history is why they live in the same tag as noindex and are just as easy to set by accident.

Accidents come from three places, and none looks like a mistake at the time. A developer copies a staging header template into production, noindex stripped out, nosnippet left in.

An editor ticks No Snippet on Yoast's Advanced tab for one post. Less visibly, an admin ticks it in Rank Math's Robots Meta settings for a post type, and every post of that type inherits it.

The third is the theme. It wraps the cookie banner in data-nosnippet, which is fine, and the article body alongside it, which is not.

Any of these on 5% of your pages is worth a morning. On 50% it explains a click-through drop you have been blaming on something else.

How to Audit What Is Set Today

Checking is a crawl, not a guess. Screaming Frog's Directives tab filters for nosnippet and max-snippet, and Sitebulb reports the same set under Indexability. Any page with nosnippet or a max-snippet value under 160 goes on the review list. That pass takes about 20 minutes on a 2,000-page site.

data-nosnippet needs a second pass, because it lives in the body, not the head. Both crawlers can pick it up with a custom search on the attribute name. What you want is the count per template — 1 hit per page from a cookie banner is expected, 5 or more means the theme wrapped something it should not have.

Confirm the effect in Search Console's Performance report: filter to the flagged pages and compare their click-through rate against the site average in the same position band. A nosnippet page holding position 3 with half the CTR of its neighbours is your evidence. Search Console does not break out AI Overview impressions, so this is the closest measurement you have.

Spot-check five results by hand. A result with a title and URL but no description is the directive working.

The Three Cases Where Restricting Pays

Restricting text earns its cost in three situations, and none of them is "AI is quoting me".

Gated or paid content. If the answer is the product — a subscription report, a course module, a licensed dataset — a 300-character extract is a giveaway. Wrap the paid portion in data-nosnippet and leave the preview open, so the result still shows a description that sells the click.

Text that must not be quoted out of context. Legal disclaimers, dosage tables and regulated financial wording all read differently when clipped to 160 characters. Wrapping them protects you from a snippet that states half a rule. Wrap the sensitive block only.

Boilerplate that steals the snippet. This case improves results rather than restricting them. Cookie notices, "related posts" lists and author bios get pulled into snippets when Google finds nothing better near the matched text. Wrapping those blocks pushes the snippet back to your real content. It is the one use of data-nosnippet worth applying site-wide.

Measure every change the same way: CTR before, the edit, then 28 days at stable position before you read anything. A move of more than 2 positions voids the test — you are measuring the ranking change, not the snippet.

Fix: if you cannot name which case a page falls into, remove the restriction. Default to open.

FAQ

Will nosnippet stop my content appearing in AI Overviews?

Mostly, and that is the problem. Google applies the same controls to AI Overviews and AI Mode, so the text will not be quoted — but the page loses its classic description too, and the citation tends to go to a competitor whose text was available. You trade a quote for an absence, not a click.

Does max-snippet affect my rankings?

No. Snippet directives govern what is displayed, not how the page is scored, and a nosnippet page can hold position 1 for years. The cost is click-through rate. Compare it against your site average at the same position — a gap of 20% or more is the signal, a traffic problem rather than a ranking one.

Can I block AI Overviews but keep my normal snippet?

No, and any tag or setting that promises to is not supported. Google runs AI Overviews and AI Mode from the same index with the same controls, so there is no AI-only opt-out at page level. Google-Extended sounds like one, but it governs Gemini as a product and has no effect on Search.

The Practical Takeaway

Crawl the site, filter the Directives report for nosnippet and any max-snippet under 160, and pull the CTR for those pages against the site average at the same position. Remove every restriction you cannot assign to one of the three cases — paid content, text that must not be clipped, or boilerplate that steals the snippet — and leave the plugin default of max-snippet:-1 alone everywhere else. Wrap cookie notices and related-post blocks in data-nosnippet site-wide, then wait 28 days before reading the result. Start with your 20 highest-impression pages this week.

If you are publishing at a volume where per-page settings drift from the template, tools like FluxWriter can help keep new posts landing with the open default intact — but which blocks deserve data-nosnippet, and whether the click-through data says the wrap earned its keep, is still a judgement you make yourself.

← All posts