AI Overviews SEO: Google's Opt Out, And When To Use It

Google put the off switch on its own controls page today, and the switch does exactly what publishers spent eighteen months asking for. Flipping it is still the wrong AI Overviews SEO decision for almost every commercial site, and the reason sits in the scope column rather than in the politics.

The change itself is small. Google updated its Control what you share with Google Search page with two new sections, one titled for the robots meta tag, data-nosnippet and X-Robots-Tag, and one titled for the Search generative AI control, and said the point was to keep its content controls page current with the options site owners already have. No new capability shipped. What shipped was placement.

Placement is what makes it worth writing about. A setting buried in Search Console under Settings is a setting your SEO lead knows about. A setting listed on Google's canonical page about controlling your content is a setting your general counsel knows about, and that is a different conversation with a different set of people in the room.

TL;DR · 60 SECONDSGoogle's October 21, 2026 documentation update adds the Search generative AI control to the same page as the robots meta tag, data-nosnippet and X-Robots-Tag. Those four names cover three scopes. The Search generative AI control is site-wide per Search Console property, with include as the default, exclude, and inherit from parent, and it removes links and impressions from AI Overviews, AI Mode and generative AI features in Discover while leaving ranking, indexing and AI training alone. Nosnippet is page level and kills the regular text snippet on every Google surface as the price of blocking AI input. Max-snippet caps the same input with a character limit and stays snippet-compatible, though Google states the cap does not bind where permission was granted separately through structured data or a license agreement. Data-nosnippet is text level and Google's documentation does not extend it to AI Overviews or AI Mode at all, which means the one control teams reach for first is the one with no documented effect on the surface they are worried about. Our verdict: max-snippet is the lever, exclude is a legal instrument rather than a visibility instrument, and nosnippet is a mistake you make once.

What Google Changed In Its Content Controls Documentation

Google rewrote its Control what you share with Google Search page on October 21, 2026, adding two sections that between them name four controls: the robots meta tag, data-nosnippet, X-Robots-Tag, and the Search generative AI control. Nothing new was built. The page simply caught up with the options that already existed, alongside a separate URL structure documentation change the same morning.

The Search generative AI control is the one most teams have not touched. It lives in Search Console under Settings, it reached every property worldwide on August 31, 2026, and it offers three states: include, which is the default and lets your content appear in and ground generative responses, exclude, which hides your content and links from those features, and inherit from parent, which follows a parent property and is the default when one exists.

Google is specific about the surfaces it governs: AI Overviews, AI Mode, and generative AI features in Google Discover, with a note that the list may change over time. Google is equally specific about what it does not govern. In Google's words, the control "only affects whether your content can appear in certain Search generative AI features," and it is not a ranking or inclusion signal for other parts of Search. It does not stop AI training, which is what Google-Extended is for. It does not remove your site from Search, which is what noindex is for. It does not override Merchant Center or Google Ads choices.

AUG 31

2026, the day the Search generative AI control finished rolling out to every property worldwide

1 to 2

days Google says exclusion takes to apply, before caching and propagation across its systems

states in the control: include, exclude, or inherit from the parent property

clicks reported in Search Console's generative AI performance report, which counts impressions only

THE PART THAT MATTERS OPERATIONALLYChild properties can override a parent's setting, and Google notifies parent owners when they do. On a brand with a property per subdomain and a property per market, the control is not one decision. It is as many decisions as you have properties, and any of them can drift.

Four Names, Three Different Blast Radii

The Search generative AI control works site-wide per property, nosnippet and max-snippet work per page, and data-nosnippet works on a marked section inside a page, so the four names now grouped in one documentation section cover three different blast radii. Reading that section as a menu of equivalent options is the error the grouping invites.

CONTROL	SCOPE	WHAT IT STOPS	WHAT IT LEAVES RUNNING
Search generative AI control	Site-wide, per Search Console property, inheritable by child properties	Your content and links appearing in AI Overviews, AI Mode and generative AI features in Discover, plus the impressions they would report	Normal Search results, indexing, ranking, AI training, and Merchant Center or Google Ads choices
nosnippet	Page level, via robots meta tag or X-Robots-Tag	Text snippets on every Google surface, and use of the page as a direct input for AI Overviews and AI Mode	Indexing and ranking, plus a static image thumbnail Google may still show when it serves the user better
max-snippet	Page level, with a character limit you set	Snippet length, and how much of the content may be used as a direct input for AI Overviews and AI Mode	Extraction where permission was granted separately, for example through structured data or a license agreement with Google
data-nosnippet	Text level, on a marked element inside the page	The marked section from appearing in search result snippets	Anything Google documents for AI Overviews or AI Mode, and structured data inside the element, which stays usable

Read the fourth row twice. Data-nosnippet is the control engineering teams reach for first, because it is the one that lives in the markup they already own and needs no Search Console access and no site-wide sign-off. Google's documentation describes it against search result snippets and says nothing about AI Overviews or AI Mode, while explicitly noting that structured data inside a data-nosnippet element remains usable for search results. Wrapping a paragraph in it and reporting upward that the content is now excluded from AI answers is a claim Google's own documentation does not support.

1The equivalence trapFour controls in one section read as four ways to do one thing. They are three scopes and two owners: Search Console for the site-wide switch, the codebase for the other three. Any policy document that lists them as alternatives is already wrong.

2The markup shortcutData-nosnippet is the cheapest to deploy and the only one with no documented effect on AI Overviews or AI Mode. Cost of deployment and strength of effect run in opposite directions here, which is exactly backwards from how teams pick.

3The permission overrideMax-snippet caps AI input, except where permission was granted separately through structured data or a license agreement with Google. A cap with a documented exception is a cap you have to audit, not a cap you set once and forget.

Why Nosnippet Is The Wrong Lever For AI Overviews SEO

Nosnippet removes a page from AI Overviews and AI Mode by removing it from snippets everywhere, which makes it the most expensive AI Overviews SEO decision on the menu: the regular text snippet goes with it. Google's robots meta tag documentation states the directive "applies to all forms of search results (at Google: web search, Google Images, Discover, AI Overviews, AI Mode)" and "will also prevent the content from being used as a direct input for AI Overviews and AI Mode."

That coupling is the whole problem. A page with no snippet is a blue link with a title and a URL competing against results that get three lines of persuasive text. You have not protected the page. You have entered it in the same race with one hand tied, and you have done it to avoid a surface that Google, as of mid October, is showing more inline links in and placing them higher in the response after publishers complained about traffic. We walked through that shift when AI Mode started showing more links while still withholding click data, and the direction of travel has not reversed since.

The lever most teams should be using instead● LIVE

<!-- Caps extraction without surrendering the snippet. -->
<meta name="robots" content="max-snippet:120">
 
<!-- Same directive, served at the header level. -->
X-Robots-Tag: max-snippet:120
 
<!-- What nosnippet costs you, for comparison: -->
<!-- no text snippet anywhere, including web search. -->
<meta name="robots" content="nosnippet">

Max-snippet is the proportionate control. Google states that the character limit also governs how much of the content may be used as a direct input for AI Overviews and AI Mode, so you keep a snippet, you cap the extraction, and you choose the number. The caveat is real and worth writing into the policy: Google says the limit does not apply where a publisher granted permission separately, for example through structured data or a license agreement, so a site with rich structured data should verify behavior rather than assume the cap binds everywhere.

“Nosnippet is not an AI opt out. It is a snippet opt out that happens to include AI, and the snippet is the part you were going to miss.”

Exclusion Deletes The Report That Would Judge It

Exclusion zeroes the only report that could tell you whether exclusion was worth it, because Search Console's generative AI performance report counts impressions from the exact surfaces the control removes you from. Flip it and the series flatlines by design, which is indistinguishable from the outcome you were hoping to measure.

The report was announced on June 3, 2026 and covers impressions from AI Overviews, AI Mode and generative AI features in Discover, broken out by page, country and date. It does not report clicks, click-through rate, average position or triggering queries, it reports AI Overviews and AI Mode together rather than separately, and clicks from those features are folded into regular Web search totals. We went through the limits of that report when it landed, in what the generative AI performance report actually measures.

So the before and after you would need does not exist. Before exclusion you have impressions with no clicks attached. After exclusion you have no impressions and a Web search click total that moved for reasons you cannot separate. Google does suggest using the report to estimate the effect of a change, which is honest advice and still leaves you estimating from a number that was never tied to revenue. Exclusion is reversible on paper, within one to two days plus caching, and that reversibility is worth less than it sounds when you cannot tell what the first flip did.

Impression baseline on the affected surfaces100%

Clicks attributable to those surfaces0%

Queries that triggered the appearance0%

AI Overviews separated from AI Mode0%

Decision quality available before and after flipping exclude, scored against the four things a reversible test needs (our framing, applied to what Search Console reports)

WHERE EXCLUSION IS THE RIGHT CALLExclusion is a legal and licensing instrument, not a visibility instrument. If you are negotiating a content license, enforcing a paywall, or acting on counsel's advice about a specific corpus, excluding a property is coherent and the traffic cost is the point. If the motive is a traffic chart you do not like, you are reaching for a switch that cannot give you the attribution you actually want.

Almost Nobody Is Searching For The Off Switch

Search demand for leaving AI Overviews is a rounding error next to demand for competing in them, which is a more useful read on where the market sits than the volume of trade coverage suggests. We pulled US monthly volumes for the obvious phrasings on October 21, 2026 and the shape was lopsided in one direction.

ai overviews optimization, 400 a month, difficulty 39100%

ai overviews seo, 350 a month88%

google extended, 60 a month, difficulty 7815%

turn off ai overviews, 30 a month8%

nosnippet, 20 a month, difficulty 165%

disable ai overviews, 20 a month5%

US monthly search volume, pulled October 21, 2026, scaled against the highest term in the set (ai overviews optimization, 400 a month)

Two phrasings returned no volume row at all: opt out of ai overviews, and how to block ai overviews. Treat the absolute numbers as directional rather than precise, because low-volume terms are the least reliable part of any keyword dataset. The ratio is the finding. The people typing these phrases into Google are overwhelmingly trying to win the surface, not leave it, and the ones trying to leave it are a small enough group that the queries barely register.

That matters for anyone writing the internal recommendation. The opt out reads like a live industry debate because publishers with a licensing strategy are loud and quotable, and their position is rational for them. Their position is not evidence about a B2B software company with a documentation site and a comparison page. Publisher economics and vendor economics point opposite ways on this switch, and borrowing the publisher conclusion without the publisher business model is how a quarter of visibility gets signed away in a meeting. The same confusion ran through the content signals policy that defaulted AI input to off, where the default did the arguing for everyone who never opened the file.

The AI Overviews SEO Decision Belongs At The Property Level

An AI Overviews SEO decision belongs at the property level rather than the brand level, because the Search generative AI control is set per Search Console property, a child property can override its parent, and Google notifies the parent owner when that happens. One company can therefore hold several contradictory positions at once without anyone intending it.

1This weekInventory every property and read its current state

THE MOVES

List every Search Console property, including domain properties, subdomain properties and URL prefix properties nobody has logged into since launch.

Record the Search generative AI setting on each one: include, exclude, or inherit from parent.

Flag any child property whose state differs from its parent, because that is a decision somebody made once and never documented.

DONE WHENDone when a single table shows every property, its current state, and the name of the person who owns that state.

2This weekSeparate the legal question from the visibility question

THE MOVES

Ask counsel whether any content corpus is subject to a licensing position that requires exclusion, and get the answer in writing.

Treat everything outside that corpus as a visibility decision, which means it is measured, not argued.

Write down which properties the legal answer covers, so the exclusion conversation stops expanding into properties it was never about.

DONE WHENDone when exclusion is scoped to named properties for named reasons, and no property is excluded because of a sentiment about AI.

3Next two weeksReplace blanket snippet suppression with capped extraction

THE MOVES

Find every page currently carrying nosnippet and check whether anyone intended to give up its web search snippet.

Convert the ones that were aimed at AI extraction to max-snippet with a specific character limit, and record the number you chose.

Audit pages with heavy structured data separately, since Google states the cap does not bind where permission was granted another way.

DONE WHENDone when no page carries nosnippet without a written reason that acknowledges the lost web search snippet.

4Next two weeksStop crediting data-nosnippet with work it does not do

THE MOVES

Search the codebase for data-nosnippet and list what each instance was meant to achieve.

Correct any internal documentation or compliance answer that calls it an AI Overviews or AI Mode control.

Keep the instances that genuinely exist to shape search result snippets, which is the job Google documents for it.

DONE WHENDone when no policy document or client answer claims data-nosnippet excludes content from AI answers.

5Before the next board updateBuild the baseline you will want if the question returns

THE MOVES

Export generative AI impressions by page and country now, while you are still included, and store the series outside Search Console's retention window.

Pair it with Web search clicks for the same pages so a future change has two series to compare rather than one.

Name the ten pages that carry the most generative AI impressions, because those are the pages an exclusion decision actually spends.

DONE WHENDone when the cost of exclusion can be stated as a page list with numbers attached, not as a principle.

The underlying skill here is not knowing the controls. It is refusing to let a control's convenience decide its scope, which is the same discipline that separates real generative engine optimization services from a checklist, and the same reason a property by property audit opens every engagement we take. The teams getting this right are the ones treating inclusion as the default and extraction limits as the dial, which is also how the sites that earn citations in ChatGPT got there: by being easy to quote correctly rather than hard to quote at all.

DO THIS NEXTOpen Search Console, go to Settings, and read the Search generative AI state on every property you own before anyone asks you about it in a meeting. If a child property says exclude and nobody on the call knows who set it, you have found the real problem, and it is not Google's documentation. Then export your generative AI impressions by page while you still have them, because the switch is cheap to flip and the baseline is not cheap to recover.

What is the Search generative AI control?A Search Console setting under Settings that governs whether your site can appear in AI Overviews, AI Mode and generative AI features in Discover. It has three states: include, which is the default, exclude, and inherit from parent. It reached all properties worldwide on August 31, 2026.

Does excluding my site hurt normal Google rankings?Google says the control only affects whether content can appear in certain Search generative AI features and is not a ranking or inclusion signal for other parts of Search. Normal results, indexing and ranking continue. What you lose is appearance and impressions on the generative surfaces.

Does nosnippet keep me out of AI Overviews?Yes, and it also removes your text snippet from web search, Images and Discover. Google's documentation says the directive applies to all forms of search results and prevents the content being used as a direct input for AI Overviews and AI Mode. The cost is rarely worth it.

Does data-nosnippet block AI Overviews?Google's documentation does not say so. It describes the attribute against search result snippets and notes that structured data inside the element remains usable for search results. Do not report it internally as a control over AI Overviews or AI Mode.

What does max-snippet actually cap?Snippet length and how much of the content may be used as a direct input for AI Overviews and AI Mode. Google states the limit does not apply where permission was granted separately, for example through structured data or a license agreement, so audit rather than assume.

How long does exclusion take to apply?Google says content is excluded within one to two days after the control goes live, with some content taking longer because of caching and propagation across its systems. Reversal runs on the same timetable, which makes the switch quick and the measurement baseline slow.

Does the control stop AI training on my content?No. Google points to Google-Extended for training, and to noindex for removing a site from Search altogether. The generative AI control covers appearance in specific Search features, not training and not indexing, and conflating the three is the most common error in policy documents.

Should a B2B software company exclude?Almost never. Publisher licensing economics drive the loud version of this argument and do not transfer to a vendor whose documentation and comparison pages are how buyers shortlist. Cap extraction with max-snippet and keep the impressions you can still measure.

What if different properties have different settings?That is likely, and Google allows it: a child property can override its parent, and the parent owner gets notified. Inventory every property, record its state and its owner, and treat any undocumented exclusion as a defect rather than a policy.

See where you are cited today

A free snapshot audit of your rankings and AI citations before we ever talk.

Schedule a free consultation

Josh BernsteinMANAGING PARTNER, SOMETHING INC.

Josh leads work at the intersection of SEO and generative engines at Something Inc., helping B2B brands get ranked and cited across every major AI engine.

Google Shipped The AI Overviews Off Switch. Leave It Alone.

What Google Changed In Its Content Controls Documentation

Four Names, Three Different Blast Radii

Why Nosnippet Is The Wrong Lever For AI Overviews SEO

Exclusion Deletes The Report That Would Judge It

Almost Nobody Is Searching For The Off Switch

The AI Overviews SEO Decision Belongs At The Property Level

See where you are cited today

Keep reading

Let us be the last SEO agency you ever work with