Google details how to control AI Overviews with nosnippet and max-snippet

A documentação do Search Central mostra que não existe um interruptor exclusivo para bloquear o AI Overviews e o AI Mode: quem quer sair (ou entrar) dessas respostas geradas por IA usa as mesmas diretivas de robots meta tag que já controlam snippets tradicionais.

Search Central's documentation shows there is no dedicated switch to block AI Overviews and AI Mode: those who want out (or in) of these AI-generated responses use the same robots meta tag directives that already control traditional snippets.

Editor's note: the update date of the official page cited in this article (December 10, 2025) does not match what appears in the source's footer at the time of fact-checking (December 31, 2025); and the claim that these directives already existed specifically for "rich results and featured snippets" was not found explicitly in the documentation consulted, which mentions only "snippet" in a generic way. The technical core of the article, about how the nosnippet, data-nosnippet, max-snippet, and noindex directives control eligibility for AI Overviews, was confirmed in the official source.

Search Central's documentation shows there is no dedicated switch to block AI Overviews and AI Mode: those who want out (or in) of these AI-generated responses use the same robots meta tag directives that already control traditional snippets.

Search Central's documentation shows there is no dedicated switch to block AI Overviews and AI Mode: those who want out (or in) of these AI-generated responses use the same robots meta tag directives that already control traditional snippets.

What Google's documentation actually says

The "AI features and your website" page, part of Search Central (updated on December 10, 2025), clarifies a point that causes confusion among technical SEO professionals: there is no specific tag to "turn off" AI Overviews or AI Mode. Google reuses the same set of robots meta tag directives that already existed to control snippets, rich results, and featured snippets. If a page is indexed and enabled to show a snippet, it is eligible to feed these AI responses; if you block the snippet, you also block participation in generative search AI.

This changes how content teams should think about the decision: it's not "appear or not in AI Overviews", it's "do I want this piece of text to be eligible for any type of fragment (classic snippet, featured snippet, AI Overviews, AI Mode) or not". Granularity exists, but it operates at the HTML level, not at the feature level.

The four directives worth mastering

The document lists four technical mechanisms for controlling indexing and fragment display:

• noindex: removes the entire page from search, including any use in AI Overviews and AI Mode. It's the most radical option, because it also removes the page from traditional results.
• nosnippet: one of the controls listed in Google's documentation to restrict the use of content in snippets, which, according to the same page, also affects eligibility for AI Overviews and AI Mode. The page can remain indexed and appear as a link, just not as a source for a summarized fragment.
• data-nosnippet: an HTML attribute, listed in the documentation alongside nosnippet, max-snippet, and noindex as one of the mechanisms available for restricting content visibility to crawlers.
• max-snippet:[number]: one of the controls listed in the documentation to limit the fragment Google can extract from the page. The documentation cites this directive alongside the others, without detailing the unit of measurement or the behavior of each specific numeric value.

In practice, implementation is simple:

Editor's note: the code in this section was not tested in a real environment. Validate before using in production.

<meta name="robots" content="nosnippet">
<meta name="googlebot" content="max-snippet:160">

To block only a portion of the page, without removing the rest's eligibility:

<p>Este parágrafo pode virar snippet normalmente.</p>
<p data-nosnippet>Este trecho nunca deve ser usado como resumo por IA ou snippet.</p>

Technical requirements for AI Overviews eligibility

Google is direct about what's needed for a page to feed these responses with a supporting link: the page must be indexed and able to show a snippet, meeting the standard technical crawling requirements (unblocked robots.txt, CDN and hosting accessible to Googlebot, relevant content in text rather than just image or video). There's no parallel "AI optimization" checklist: the same SEO fundamentals that already applied to appearing in rich results apply here, including structuring data consistent with the visible text on the page and making discovery easier through internal links.

It's worth noting that this snippet control is different from the control over using content to train AI models or generate grounding for other Google products: for that, there's the Google-Extended agent, handled separately in robots.txt and documented on its own. Anyone who wants to block use in AI training without blocking appearance in AI Overviews needs to adjust that other layer, not nosnippet.

The CTR trade-off embedded in the decision

Here's the point that matters to those who measure traffic: blocking a snippet is an all-or-nothing decision regarding fragments, but not regarding search as a whole. A page with nosnippet continues to rank and appear as a regular link, it just loses the chance of having its text quoted inside the AI Overviews card or in AI Mode responses.

This creates two opposite risk scenarios:

• Leaving it open: your content can be summarized within the AI response, which reduces the need to click for those who just wanted quick information, but also increases brand visibility as a cited source, with a chance of clicks from those who want to dig deeper. Google itself states, in the document, that it has observed that clicks made from results with AI Overviews are of higher quality, in the sense that users tend to spend more time on the destination site.