Google AI Overviews Opt Out: What Publishers Need to Know

Publishers have wanted this for two years: a way out of AI Overviews that does not mean leaving Google Search.

It now exists. Google added a toggle to Search Console in early June 2026, effective from 17 June, that removes content from AI Overviews and AI Mode without affecting organic rankings.

It also does considerably less than most coverage suggests, and for the majority of sites switching it on would be a mistake. Here is what it actually does, what it leaves untouched, and who has a genuine case for using it.

What Google Shipped

The control appears in Search Console as a per-property setting, which can be set to include, exclude, or inherit from a parent property.

What it covers:

• AI Overviews
• AI Mode
• AI Overviews within Google Discover

The critical assurance: Google has stated the setting will not be used as a ranking signal. Opting out does not quietly cost you organic position. That was the assurance publishers needed before the control was usable at all, because the previous options all carried a ranking or traffic penalty.

Alongside it, Google began rolling out a Generative AI performance report in Search Console covering impressions, top pages appearing in AI responses, and country and device breakdowns.

Google Did Not Build This Voluntarily

Worth knowing, because it explains the shape of the control.

The UK’s Competition and Markets Authority issued an order on 3 June 2026 — the same day Google announced the feature. It is the first binding legal requirement anywhere compelling a search engine to let publishers opt out of AI-generated summaries without losing normal search visibility.

The CMA had specifically criticised the existing workaround. Publishers were being told to use nosnippet, which the regulator noted was likely to reduce organic traffic because it strips the descriptive text users rely on to decide whether to click. The CMA cited a Google study from before AI features existed finding that reducing detail on publisher content in search cut traffic by around 45%.

That context matters: the toggle exists to dissolve a coupling regulators judged unfair, not because Google identified a publisher need.

Five Levers, Four of Which Get Confused

This is where most publishers go wrong. These controls do different jobs and are not interchangeable.

The most common misconception is that Google-Extended stops you appearing in AI Overviews. It does not. Overviews are constructed from the regular Search index, so blocking the training token has no effect on whether your content appears in a generated answer.

The second is that nosnippet was a targeted fix. It was the only previous exit, and it cost you your ordinary search snippet as well. The new toggle exists specifically to break that trade-off.

What the Toggle Does Not Cover

Three gaps that matter.

The Gemini app. If Google’s standalone assistant draws on your site, this toggle will not stop it. That is a significant omission and one Google is likely to face further questions about.

AI training. Google explicitly directs publishers to Google-Extended for training limitation. The toggle is a display control, not a data control.

Crawling. It is not a crawling instruction. Your content is still fetched and indexed exactly as before.

So a publisher wanting to be out of AI Overviews and out of training and out of the Gemini app needs at least two of these controls, and will still not have complete coverage.

Availability

The rollout is staged rather than global. It reached the United Kingdom first, then France. As of the most recent reporting, publishers in Germany, Austria, and Switzerland could not use it — despite AI Overviews being live in those markets for some time.

Check whether the setting appears in your Search Console property before planning around it.

What You Give Up

Here is the part that makes this a genuinely difficult decision rather than an obvious win.

AI Overviews reportedly reach over 2.5 billion monthly users, and AI Mode has passed one billion. Opting out removes you from the surfaces where Google increasingly expects users to spend their time.

You also lose the click data. Whatever traffic AI features do send — and it is a small fraction of what traditional results send — stops entirely, along with your ability to measure the relationship.

The scale of the underlying traffic problem is not in dispute. One large multi-brand publisher reported a cumulative loss of around 800 million Google sessions between early 2024 and early 2026. Organisations of that size can absorb it. Most cannot.

Which is why the industry response has been ambivalent rather than celebratory. Large publishers are scenario-planning rather than switching: some have blocked Google-Extended, some have opted out of Gemini, and a few are modelling full de-indexing. As one executive put it, options that would have looked suicidal historically are now things nearly everyone has a model for.

Who Should Actually Consider It

A genuine case exists for a narrow set of publishers.

• Subscription and premium publishers, where the content itself is the product and a synthesised summary substitutes for the purchase rather than promoting it.
• Sites with concrete reputation risk, where inaccurate paraphrasing of your material creates liability or brand damage — regulated advice, medical content, legal information.
• Publishers with genuine leverage, negotiating licensing terms and wanting to demonstrate that withdrawal is credible.
• Sites where AI referral traffic is already negligible and measurable brand harm from summarisation exceeds it.

Who Should Not

Most sites, including most publishers.

• If discovery drives your business, removing yourself from the largest discovery surface is a large bet against your own traffic.
• If you monetise on volume, AI Overview citation still produces some traffic, and cited brands appear to fare better than uncited competitors on the clicks that remain.
• If you have not measured your own AI impressions, you are deciding without data. Check the new Search Console report first.
• If the concern is training rather than display, you want Google-Extended, not this toggle.

What to Do Instead

For the majority, the productive response is not withdrawal.

• Check whether the toggle is available in your property, and check the Generative AI performance report if you have it. Establish a baseline before deciding anything.
• Separate the two questions. Display and training are different concerns with different controls. Decide on each independently.
• Give people a reason to click that a summary cannot substitute for — tools, proprietary data, depth, community, things that require the page.
• Publish material only you could produce. Google’s own refreshed guidance points to unique, non-commodity content, page experience, and quality imagery as the levers for AI visibility.
• Revisit quarterly. The controls, the coverage, and the regulatory position are all moving.

Final Thoughts

The opt-out is a meaningful regulatory achievement and a modest practical one. It resolves a genuine unfairness — that leaving AI features previously meant degrading your ordinary search presence — and it leaves the larger economics untouched.

For most publishers the honest answer is to leave it off, measure what AI features are actually doing to your traffic, and spend the effort on being worth citing rather than on being absent. The narrow group with a real case will already know who they are.