Can You Control What AI Overviews Shows From Your Page?

Can you control what AI Overviews shows from your page?

Yes, partly, and the controls are older than you think. Google's robots meta tag documentation covers directives that now explicitly apply to AI Overviews and AI Mode. They let you suppress preview text or cap its length. What they do not give you is a way to make Google quote you more, or quote the part you prefer.

I want to be precise about scope before anything else. Everything below comes from Google's own documentation and applies to Google's systems. It is not a general standard, and it does not tell you how ChatGPT, Perplexity, or Claude treat your pages.

That distinction matters because a lot of advice in this space quietly treats one vendor's directive as a law of physics. It is not. It is one company's published contract with publishers, and it can change.

What does nosnippet actually do in 2026?

Google's documentation defines nosnippet as an instruction to not show a text snippet or video preview in the search results for that page. The important part for anyone working on AI visibility is the scope statement that follows it, because that is where the modern behaviour is spelled out.

Google says nosnippet applies to all forms of search results, listing web search, Google Images, Discover, AI Overviews, and AI Mode. It then adds that it will also prevent the content from being used as a direct input for AI Overviews and AI Mode. That second clause is the one people miss, and it is doing a lot of work.

So nosnippet is not a display preference. Per Google's own wording it removes your text from the input, not just from the output. If you were hoping to stay in the answer while hiding your preview, that is not what this directive does.

What makes max-snippet the more useful lever?

Because it is a dial rather than a switch. Google's documentation describes max-snippet as an instruction to use a maximum of a given number of characters as a textual snippet, and says it will also limit how much of the content may be used as a direct input for AI Overviews and AI Mode.

The two special values are worth committing to memory. Google states that max-snippet set to zero means no snippet is to be shown, and is equivalent to nosnippet. Setting it to minus one means Google will choose the snippet length it believes is most effective to help users discover your content and direct users to your site.

For almost every publisher I work with, minus one is the right answer and they should stop thinking about it. The dial exists for people with a genuine reason to restrict, usually licensing or paywall obligations, not for people hoping to engineer a better preview.

Why does using nosnippet cost you citations?

Because of one sentence on Google's AI features documentation that ties the whole thing together. Google states that to be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet, fulfilling the Search technical requirements.

Read that against the directive definitions and the trade becomes explicit. Eligibility for the supporting link runs through snippet eligibility. Suppress the snippet and you have, by Google's own description, removed the condition that makes the link possible. You have not protected your position in the answer. You have opted out of it.

This is the single most expensive misconfiguration I see discussed as if it were a clever tactic. If your goal is to be the source an answer points at, and I have spent more than 350 articles on precisely that problem, then a blanket nosnippet is working directly against you. It belongs to a different goal entirely.

Can you protect one paragraph without silencing the page?

Yes, and this is the control most people have never used. Google's documentation says you can designate textual parts of an HTML page not to be used as a snippet, at the element level, using the data-nosnippet attribute on span, div, and section elements.

That is the surgical option. A pricing figure you do not want quoted out of context, a client name under an embargo, a disclaimer that reads badly stripped of its surroundings. Wrap that specific element and leave the rest of the page fully eligible.

The practical difficulty is that CMS rich text does not always let you attach attributes to arbitrary elements, so on a Webflow site you may need the affected block to live in a structure you control rather than inside the body field. Check Webflow's own documentation for where custom attributes and head code can be set on your plan before you design around this.

Where does Google-Extended fit, and where does it not?

It is a separate control with a narrower stated scope, and conflating it with the snippet directives is a common error. Google's AI features page points readers to Google-Extended to limit AI training and grounding in some of Google's other systems. Note the wording carefully: other systems.

I am not going to extend that sentence further than Google does, because this is exactly the kind of detail where confident summaries go wrong. If you need to know whether a specific Google surface is covered, read Google's current documentation for Google-Extended rather than an article about it, including this one.

The broader point holds regardless. Crawler and preview controls are a stack of separate switches with different scopes, and reasoning about them as one on or off decision is how sites end up invisible by accident. I have written about the differences in how Perplexity, ChatGPT, and Google AI Mode cite sources, and the same warning applies: one vendor's control is one vendor's control.

Does any of this help you get cited more?

No, and I think that is worth saying plainly because the framing around AEO often implies otherwise. Google's AI features documentation states there are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary, and that there are no additional technical requirements beyond the Search ones.

What Google does describe is a query fan-out technique that AI features use to develop responses, which it says lets them display a wider and more diverse set of helpful links. That is a description of retrieval behaviour, not a lever you operate. The useful inference is about coverage rather than tricks: a page that answers one narrow question well can be pulled in by a query you never targeted.

So the honest strategy stays boring. Be indexable, be snippet eligible, answer real questions directly, and earn the kind of page that deserves to be a supporting link. Everything else in this article is about not accidentally disqualifying yourself. I made that argument at length in why ranking first no longer wins you the citation, and Google's documentation has not given me a reason to revise it.

Who should actually use these directives?

A small minority. Publishers with licensing constraints, sites with paywalled or embargoed content, and anyone with a specific element that is genuinely harmful when quoted alone. For everyone else the correct configuration is to do nothing and let Google choose.

There is one more directive worth knowing so you do not misuse it. Google's documentation says indexifembedded only has an effect if it is accompanied by noindex, and it allows content to be indexed when embedded in another page through iframes or similar tags. It solves a narrow embedding problem and nothing else.

The general rule I give clients is that every robots directive you add is a promise to remember it. Directives set for a reason that expired two years ago are a quiet, permanent tax, and nobody audits them because nobody can see them.

What should you do next?

Check what you are already sending. View source on your most important page and search for nosnippet, max-snippet, and data-nosnippet, then do the same on a template that generates hundreds of pages. If you find a directive nobody can explain, that is your finding for the week, and it may be the reason you are missing from answers. Pair that check with whatever citation reporting you already watch, which for most Webflow owners means the AI citations reporting in Google Search Console.

Then verify against Google's current documentation rather than trusting this article six months from now. I have quoted Google's robots meta tag and AI features pages as they read today, and these pages get revised. A directive's scope is exactly the kind of thing that changes without anyone announcing it loudly.

If you want a second pair of eyes on what your templates are quietly telling Google, reach out. Checking this is fast, and it is one of the few AI visibility problems with a definite answer.