Opt Out of AI Overviews Without Losing Rankings

Yes, you can leave Google's AI surfaces without touching your rankings — Search Console's Search generative AI control removes your links and content from AI Overviews, AI Mode and generative features in Discover, and Google states plainly that it "isn't used as a ranking or inclusion signal affecting other parts of Search." But the control is property-level, not page-level, it's all-or-nothing across all three surfaces, and the levers that are page-level today (nosnippet, max-snippet) buy their AI protection by deleting your ordinary organic snippet. Rankings are protected. Traffic is a different question — and it's usually the wrong lever that costs you.

The two levers publishers keep mixing up

Two sentences from Google's own documentation, both true, pointing in opposite directions. From the crawler docs: Google-Extended "does not impact a site's inclusion in Google Search nor is it used as a ranking signal in Google Search." From the Search Console help: the generative AI control "isn't used as a ranking or inclusion signal affecting other parts of Search."

They sound interchangeable and govern completely different things. Google-Extended is a robots.txt token covering training of future Gemini models and grounding in Gemini Apps and Grounding with Google Search on Vertex AI — it does nothing to AI Overviews or AI Mode. The Search Console control does the reverse: out of AI Overviews, AI Mode and Discover's generative features, with training untouched.

So the two most common moves cancel each other out. Disallow Google-Extended to "get out of AI answers" and you stay fully present in AI Overviews, having quietly deleted yourself from the Gemini assistant — a surface that never appears in Search Console's AI report, so the loss is invisible exactly where you'd look for it. Flip Exclude to "stop Google training on our archive" and you've stopped nothing of the kind. Diagnose the grievance first: training points to the robots.txt token, appearing in answers points to the toggle.

What the Search Console control actually does

It lives in Settings → Search generative AI with three states: Include (the default), Exclude, and Inherit from parent. Child properties inherit from the closest configured parent, defaulting to the top-level domain — which matters more than it sounds, because property segmentation is the only granularity on offer.

Exclude stops Google linking to you in the covered features and stops your content grounding answers there: it "won't be eligible to be used as an input to generate an AI response or preview." Changes generally propagate within one to two days, though Google warns caching can delay some content, so don't read week one as the result. Covered surfaces are AI Overviews, AI Mode and generative features in Discover, and Google expects to update that list. Untouched: blue-link ranking and indexing, Merchant Center, Google Ads, model training, and grounding in the Gemini app or Vertex AI. One switch spans three surfaces that retrieve very differently, which is why our breakdown of how Gemini, AI Overviews and AI Mode each source their answers is worth reading first.

The control exists because of regulation, not product strategy: the UK's Competition and Markets Authority imposed a Publisher Conduct Requirement on 3 June 2026. Google began respecting the setting on 17 June, starting with UK properties and reaching some US and international properties from around 9 July. The rollout is still partial, so if you can't find the setting, you haven't misconfigured anything.

One date for the calendar: page-level grounding controls aren't required until 3 March 2027, with the main publisher controls in force from 3 December 2026 and the first compliance report due 3 January 2027, per the CMA's compliance timetable. Google argued page-level controls needed extra engineering time and was granted nine months rather than six. Until then, page-level opt-out does not exist in Search Console.

Every Google AI lever, and what each one costs you

Lever	Operates at	What it stops	What it costs you
GSC Search generative AI → Exclude	Property (with inherit-from-parent)	Links to you and use of your content to ground AI Overviews, AI Mode, Discover generative features	All impressions and traffic from those surfaces. Explicitly not a ranking or inclusion signal.
nosnippet	Page	Text snippet and video preview, plus use "as a direct input for AI Overviews and AI Mode"	Your organic snippet on every query in Search
max-snippet:[n]	Page	Caps snippet length and how much content may be a direct input for AI Overviews and AI Mode	A truncated snippet
data-nosnippet	HTML element (span, div, section)	Specific passages from snippets	Only that passage — the surgical option
Google-Extended	robots.txt path rules	Gemini training, plus grounding in Gemini Apps and Vertex AI	Gemini-assistant visibility. Nothing in AI Overviews or AI Mode.
noindex / Disallow: Googlebot	Page / path	Everything	All of Google Search

Two notes from the robots meta tag documentation. data-nosnippet is the only element-level control Google offers, and Google may extract it before or after rendering — so never toggle it with JavaScript. And nosnippet genuinely works as an AI control, which is the trap: it also strips your snippet from ordinary results, so on a commercial page you're paying a permanent CTR tax for protection you could have bought more cheaply.

What "not a ranking signal" does and doesn't promise

Google's promise is narrow and specific. The CMA's conduct requirement goes further, barring Google from penalising publishers who use the controls, "for example by downranking their Search Content, or otherwise disadvantaging them, relative to opted-in Search Content." Between them, your positions and your indexing are about as protected as written commitments get.

Neither says anything about features that render inside AI surfaces — which is where news publishers should slow down. NewzDash found the Top Stories carousel rendering inside the AI Overview in 15.5% of US cases and 17.46% of UK cases where Top Stories appears on trending-news results, peaking at 35.05% in Entertainment. The two placements are mutually exclusive, and John Shehata's read is that the Search Console exclusion "will likely prevent the publisher from appearing in Top Stories embedded inside AI Overviews" — an outcome Google hasn't explicitly confirmed. For a news brand that's roughly one in six trending-news placements handed to a competitor, on top of the citations you meant to give up.

One open question nobody has answered with evidence: whether losing AI-surface impressions and clicks eventually feeds back into engagement-derived systems. Google's statement covers direct use as a signal, nothing more. The honest label is unproven — not "safe," not "risky."

The number that should drive this decision

The strongest argument against opting out isn't a slogan, it's Seer Interactive's three buckets. Across 53 brands, 5.47 million tracked queries and 2.43 billion organic impressions between January 2025 and February 2026, Seer measured organic clicks per million impressions on informational queries in three states: about 33,500 with no AI Overview, about 20,743 when an AI Overview appears and the brand is cited, and about 9,445 when it appears and the brand isn't.

Sit with the second and third numbers, because on an AIO-present SERP those are your only two options. Citation is worth +120% more clicks per impression than no citation, while still running −38% below a no-AIO baseline you can't get back. Opting out doesn't remove the AI Overview from the page; it permanently assigns you to the 9,445 bucket. Apply those rates to ten million monthly impressions on AIO-present informational queries and you're choosing between roughly 207,000 and 94,000 clicks — about 113,000 a month, forgone deliberately. Seer's own framing: "A citation is an advantage relative to everyone else on the same AIO-present SERP. It's not a return to the pre-AIO baseline."

Two scope notes. Those are informational-query rates from one 53-brand panel, not a constant. And the backdrop is harsher than any single study: SparkToro's read of Similarweb's US web panel found 68.01% of Google searches ended without a click in January–April 2026, up from 60.45% in 2024. That same panel puts AI Mode at only 0.34% of searches despite Google reporting over a billion monthly AI Mode users — so whatever you decide here, you're mostly deciding about AI Overviews.

And the number Google won't give you

Here's the uncomfortable part: you can't model that trade-off with the data Google supplies. The Generative AI performance report gives impressions only — no clicks, no CTR, no queries — with AI Overviews and AI Mode combined and Labs data excluded. Impressions also count differently by aggregation: two of your URLs in one AI response are a single impression at property level but two at page level, so those totals never reconcile.

The CMA asked for impressions, click-throughs and click-through rate, disaggregated per publisher. Google has shipped the first of three, and practitioners noticed — Search Engine Journal's coverage captured Glenn Gabe's "AI reporting coming to GSC! Awesome! No click data. NOT Awesome" alongside Aleyda Solís's more forgiving "it's a start."

It gets one turn worse. AI Mode clicks and impressions have sat inside the main Performance report since 16 June 2025 with no filter to isolate them. Flip Exclude and your headline clicks will fall, with no clean way to attribute that fall to the surfaces you just left rather than to everything else that happened that fortnight. As Reuters Digital's Phil Andraos told Digiday: "There's not enough data. If there was, we could make that decision very quickly."

Which explains the gap in the record: across months of coverage in Digiday, Press Gazette, Search Engine Journal and Search Engine Land, nobody has named a major publisher that flipped Exclude and published the traffic outcome. One new button, zero public experiments. Go first and you're the case study.

Your rankings can't backfill an AI opt-out

The last defence publishers reach for is "we rank well, we'll be fine." That held when AI citations tracked the top 10. They don't any more.

Ahrefs analysed 863,000 keyword SERPs and 4 million AI Overview URLs and found only 37.9% of AI Overview citations come from pages ranking in the top 10 for the same query, down from roughly 76% in July 2025; 31.2% come from positions 11–100 and 31.0% from beyond 100. BrightEdge's nine-industry tracking from May 2024 to September 2025 landed lower still, at 16.7% overlap with top-10 results. Trackers disagree on the figure; they agree on the direction.

The mechanism is in Google's own documentation: AI Overviews and AI Mode run retrieval-augmented generation plus query fan-out, issuing concurrent related queries rather than summarising the ten results in front of the user. Position three therefore buys far less citation share than it used to, which cuts both ways — rankings won't guarantee citations, and they won't replace the ones you switch off.

Match the lever to the grievance

Run ad-funded scale content and the Seer arithmetic dominates; the case for Exclude is weak. Citation is worth roughly twice the clicks of no citation on the same SERP, and as Search Engine Land's Nick LeRoy put it, "if your content disappears from those experiences, someone else will take its place."

If you're paywalled or licensing-first, the case for excluding is a rights and leverage argument rather than a traffic one — legitimate, with a prisoner's dilemma attached. The Guardian and the Financial Times are among UK brands that signed Google AI content deals, and one industry source told Press Gazette that "if your competitor has a deal and you are opting out, they get the small amount of traffic and the cash." If you're a news publisher, price in embedded Top Stories eligibility before you touch the property switch.

And if what you want is narrower than "out of everything," take the narrower tool: data-nosnippet around the passages you're actually protecting, a max-snippet cap instead of killing the snippet outright, or a separate Search Console property for the archive or paywalled vertical — the only sub-site granularity available before March 2027. "Wait for page-level controls" is a respectable answer, not an absence of one.

Measure what you'd forfeit, including outside Google

Whatever you conclude about Google's three surfaces, none of these levers touch ChatGPT, Claude, Grok or Perplexity — separate crawlers, separate controls. That's why the technical audit and the answer audit are two jobs; our guides to choosing which AI crawlers to allow under Cloudflare's changing defaults and to getting crawler access and llms.txt right in twenty minutes cover the levers Google's help pages don't.

The gap Search Console structurally can't fill is per-engine citation behaviour. Geoptimizer runs your buyers' real questions across ChatGPT, Gemini, Claude and Grok with web search on and reports mention rate, citation rate, prominence and sentiment per engine — so the Gemini-assistant exposure Google-Extended quietly governs becomes a number instead of a shrug. Then verify changes properly: propagation takes one to two days plus caching lag, and AI answers are nondeterministic, so one spot-check proves nothing. Deep Scan before, Deep Scan after, and read the 7-day rolling window with its confidence band rather than a single snapshot.

If you want evidence that crawl volume doesn't translate into being cited, see AI Crawler Log Analysis: Crawl Volume Isn't Citations for a breakdown of crawler logs versus actual citation outcomes across engines.

FAQ

Does opting out of AI Overviews hurt my rankings? Google says no — the control "isn't used as a ranking or inclusion signal affecting other parts of Search," and the CMA separately bars downranking or disadvantaging opted-out content. What isn't promised is placement in features rendered inside AI surfaces, embedded Top Stories being the clearest example.

Does blocking Google-Extended remove me from AI Overviews? No. Google-Extended governs Gemini training and grounding in Gemini Apps and Vertex AI, and Google states it doesn't affect Search inclusion or ranking. Blocking it costs you Gemini-assistant visibility, not AI Overview citations.

Can I opt out of AI Mode but stay in AI Overviews? Not today. The control covers AI Overviews, AI Mode and Discover's generative features as one bundle, and the CMA framework doesn't require per-feature or per-purpose control either — as the PPA's Saj Merali put it, publishers must decide whether their content is "on all search AI features or none of them."

Can I exclude just one section of my site? Only by splitting it into its own Search Console property — a subdomain or path-prefix property with inherit-from-parent set deliberately. Page-level grounding controls aren't required until 3 March 2027.

The bottom line

Google's AI controls do what they say, but they're blunter and worse-instrumented than "page-level and ranking-neutral" suggests: one property switch across three surfaces, a robots.txt token governing an entirely different set of products, snippet directives that charge you your organic snippet, and a report with no clicks in it. Match the lever to the grievance, and measure before you pull anything.

Start with the picture Search Console can't show you — run a free AI Visibility Check to see whether ChatGPT, Gemini, Claude and Grok mention your brand today, then compare Geoptimizer's plans and scan allowances when you want to track the change over time. Know what you'd be giving up before you give it up.