SEOIndustry Guide12 min readPublished June 29, 2026

UK-first · effective June 17 · covers three surfaces, not Gemini

Search Console’s New AI Overviews Controls

Google has added a Search Console toggle that controls whether your pages appear in AI Overviews, AI Mode and AI Overviews in Discover — but not the Gemini app. It rolled out UK-first under a CMA mandate and took effect June 17, 2026. Here is how the inheritance hierarchy works, how fast changes propagate, and why most sites should measure first and stay opted in.

DA
Digital Applied Team
Senior strategists · Published June 29, 2026
PublishedJune 29, 2026
Read time12 min
Sources7 primary
AI Overviews users
2.5B
monthly · Google-stated
AI Mode users
1B+
monthly · Google-stated
Propagation
1–2days
some content longer
Surfaces covered
3
Gemini app excluded
not training

Google Search Console now has a control that decides whether your content appears in AI Overviews, AI Mode and AI Overviews in Discover. It launched UK-first on June 3, 2026 under a binding order from the UK’s competition regulator, and it took effect on June 17. For the first time, a publisher can be pulled out of Google’s AI answers while staying fully indexed and ranked in ordinary search results.

That separation is the whole point — and it is also where most teams get the decision wrong. Opting out does not protect your rankings because rankings were never at risk; what it removes is impressions and clicks from a set of surfaces Google says now reach billions of people every month. The control is narrow, the inheritance rules are unintuitive, and one large product surface — the Gemini app — sits entirely outside its scope.

This guide is the mechanics-and-judgement version: exactly what the toggle covers, how to measure your current AI-surface exposure before you touch it, how the parent-to-child property inheritance cascade behaves, how the control differs from Google-Extended and noindex, and a site-type decision matrix for who should actually consider excluding. Every figure here is sourced; where a number reaches us through secondary reporting, it is flagged as such.

Key takeaways
  1. 01
    The toggle covers three AI surfaces — and only three.AI Overviews, AI Mode, and AI Overviews in Discover. It does not cover the Gemini app, and it does not control AI training. Opting out of Search AI leaves your content fully exposed inside Gemini.
  2. 02
    Opting out never touches your regular rankings.Google states the control is not used as a ranking or inclusion signal for the rest of Search. Excluding removes AI-surface traffic and impressions only; conventional blue-link results, Merchant Center and Ads are unaffected.
  3. 03
    Properties inherit the setting from their nearest parent.By default a property follows the closest ancestor that has changed its control; with none configured, it follows the top-level domain. A subdomain is a child of its domain — but a different TLD, like a .co.uk versus a .com, is not.
  4. 04
    Measure first using the Generative AI performance report.Google shipped a companion report showing which pages surface in AI answers and how many impressions they earn. Quantify what you would forfeit before deciding — for many sites the exposure is smaller than feared.
  5. 05
    Most sites should stay in; it is UK-only for now.With AI Overviews and AI Mode growing fast, blanket opt-out means leaving a rising discovery channel. The control is live for a subset of UK owners; Google plans a global expansion after UK testing, with no date announced.

01What It ControlsOne toggle, three surfaces — and a notable carve-out.

The new setting lives in Search Console under Settings → Search generative AI. Its job is narrow and specific: it governs whether your content can be used to generate answers in three Google features. Everything else about how Google crawls, indexes and ranks your site is untouched by it. Glenn Gabe, the SEO consultant who surfaced Google’s detailed documentation in late June, summarised the mechanics that trip people up most.

Covered
AI Overviews
Generated summaries atop search results

The AI-written answer block that appears above traditional results. Google says this surface now reaches 2.5 billion monthly users — a vendor-stated figure announced at I/O 2026.

Excluded → zero impressions
Covered
AI Mode
The conversational search experience

Google's chat-style search surface, which it says passed 1 billion monthly users with queries more than doubling each quarter since launch. Both are Google-stated, with no independent audit.

Excluded → zero impressions
Covered
AI Overviews in Discover
Generative summaries inside Google Discover

The AI-generated layer within the Discover feed. The toggle treats it as part of the same Search-AI surface family, so an exclusion applies here too.

Excluded → zero impressions
NOT covered
The Gemini app
Separate product surface · same model

Content can still surface inside the Gemini app even after you opt out of Search AI. It runs on the same model family but through a different product and inference pipeline, and is explicitly outside the toggle's scope.

Stays exposed
The carve-out that matters
The single most under-reported limitation: the Search Console toggle does not cover the Gemini app. A publisher who excludes their content from AI Overviews and AI Mode can still find it summarised inside Gemini. If your goal is to keep content out of every Google AI product, this toggle alone does not get you there — and no current control fully does.

02Measure FirstQuantify your exposure before you touch the switch.

Alongside the control, Google launched a companion Generative AI performance report in Search Console. It shows impressions from AI-generated surfaces and which of your pages are appearing in them. This is the step almost every opt-out discussion skips, and it is the one that should come first: you cannot weigh a trade-off you have not measured. For most sites the answer to “how much AI-surface traffic would I actually lose?” turns out to be smaller than the anxiety around it suggests.

Pull the report, isolate the pages that surface in AI answers, and compare those impressions against the rest of your search footprint. If AI surfaces are a rounding error for your site, opting out buys you nothing and costs you a growing channel. If they are material and you run a content business where the summary may substitute for the visit, you at least have a number to reason about. For a deeper walk through the report itself, see our companion piece on tracking your AI Overviews traffic in Search Console.

Measure-first checklist
Open the Generative AI performance report, export AI-surface impressions by page, and benchmark them against total Search impressions. Only then open Settings → Search generative AI. Treat the report as the evidence base for the decision — not an afterthought once you have already flipped the switch.

03InheritanceThree settings, and a parent-to-child cascade.

The Search generative AI settings page offers three options per property. Understanding how they cascade is the part that catches out anyone managing a multi-subdomain or multi-country setup.

Option A
Include
In

The default for every root property. Your content remains eligible to appear across AI Overviews, AI Mode and AI Overviews in Discover. No action needed to stay here.

Root default
Option B
Exclude
Out

Your content is blocked from the three AI surfaces. You receive no traffic or impressions from them, while regular search ranking and inclusion are unaffected.

Manual opt-out
Option C
Inherit from parent

The default for any property that has a parent. It follows the closest ancestor that has stopped inheriting; if none has, it follows the top-level domain setting.

Child default

The cascade works from the most specific configured ancestor downward. Google’s own example: a URL-prefix property like https://example.com/business/cats inherits from whichever of https://example.com/business/, https://example.com/ or the top-level domain example.com is the closest ancestor that has manually set its own control. Change the control on a parent and every inheriting child below it moves with it — unless that child has been set explicitly, in which case the child’s own setting wins.

The edge case worth committing to memory: inheritance is TLD-scoped, not name-scoped. A subdomain such as blog.example.com is a child of example.com, so it inherits. But example.co.uk is not a child of example.com — different top-level domains are separate roots and configure independently. Teams running per-country domains have to set each one on its own; one opt-out does not carry across your international estate.

“If you haven’t reviewed Google’s support documentation for blocking AI Search, there’s a lot of info there. And that includes how child properties will inherit the settings from parent properties, but that can be overridden at the child property level.”— Glenn Gabe, SEO consultant

04Timing & CostOne to two days to propagate — and exactly what you forfeit.

After you change the control, Google says it generally takes a few days to take effect — typically one to two days, with some content longer because of caching and propagation across Google’s systems. There is a historical wrinkle worth knowing: during the June 3 to June 17 window, the toggle existed but was not yet enforced, so changes made before June 17 had no effect on results. The control only began acting on those settings from its effective date.

What exclusion costs is unambiguous, and Google states it plainly. Opted-out content receives no traffic and no impressions from the AI surfaces — full stop. What it does not cost is anything in conventional Search: Google is explicit that the control is not used as a ranking or inclusion signal elsewhere, and that it does not override Merchant Center or Google Ads participation. That clean separation is the genuinely new capability here.

The case for caution before opting out is the click-through context. Reports suggest AI Overviews have measurably depressed link clicks — data from Pew Research cited by industry observers indicates that roughly 8% of users clicked an underlying link when an AI Overview was present, versus about 15% when one was not. Computed against each other, that is a relative drop of about 47% ((15 − 8) ÷ 15). Separately, analytics firm Chartbeat’s figures, again via secondary reporting, point to Google referrals falling roughly a third across a large publisher panel. Treat both as directional, secondary-sourced signals rather than audited fact — but they explain why publishers are weighing this decision at all.

In Google's words
On exclusion, Mrinalini Loew, General Manager of the Google Search Ecosystem, put it directly: “Sites that opt out will not receive traffic or impressions from our generative AI features.” That is the entire trade — AI-surface reach in exchange for keeping your pages out of AI answers, with rankings held constant either way.

05Three ControlsThe toggle is not Google-Extended, and neither is noindex.

The most common error in AI-control coverage is treating three separate mechanisms as interchangeable. They are not. The Search generative AI control governs whether your content is used to ground real-time AI answers. Google-Extended is a robots.txt signal that governs AI training and Gemini grounding — and has no effect on Google Search, including AI Overviews and AI Mode. Noindex removes a page from Search entirely. The table below is our synthesis of how the three differ; the boundaries are drawn from Google’s own documentation.

Comparison of the three Google content controls — the Search generative AI control (the new Search Console toggle), Google- Extended, and noindex — across what each one blocks, where it applies, when it takes effect, and whether it is reversible. Boundaries are drawn from Google Search Console Help and Google Search Central documentation.
ControlWhat it blocksWhere it appliesEffect timelineReversible
Search generative AI control (the toggle)Appearance in AI Overviews, AI Mode, AI Overviews in DiscoverGoogle Search AI surfaces only — not Gemini, not training≈ 1–2 days to propagateYes — switch back to Include
Google-Extended (robots.txt)Use of content for AI model training and Gemini groundingTraining and Gemini — no effect on Search, AI Overviews or AI ModeNext crawl of robots.txtYes — remove the directive
NoindexInclusion of the page in Google Search at allAll of Search — removes the page, AI surfaces includedNext crawl, then de-indexingYes — remove the tag and re-index

The practical takeaway: training and grounding are different problems. If your concern is models learning from your content, that is Google-Extended, not the toggle. If your concern is real-time appearance in AI answers, that is the toggle, not Google-Extended. And if you want a page gone from Search outright, that is noindex — a much larger step that also kills your ordinary rankings. The new control is the only one of the three that removes AI-surface appearance while leaving conventional rankings fully intact.

06Decision MatrixWho should actually opt out — and who almost certainly should not.

Google’s documentation explains the mechanics but offers no guidance on who should use which setting. That gap is where most of the reflexive opt-outs happen. The matrix below maps the decision by site type — synthesised from Google’s documentation, the regulatory scope, and publisher-impact reporting. For the great majority of commercial sites, the recommendation is the same: stay in, and let the performance report, not the headlines, drive any change. If you want the decision walked through as a framework rather than a table, our companion piece on whether you should block Google AI responses pairs the same logic with the GSC AI performance report.

Decision matrix for the Search generative AI control by site type, showing the recommended setting (Include, measure first, or exclude), the rationale, and the key trade-off for news and content publishers, ecommerce, SaaS and B2B, agency and marketing sites, niche and membership content, and local service businesses. This is Digital Applied analysis, not official Google guidance.
Site typeRecommended settingWhyKey trade-off
News / content publisherMeasure first, then weigh ExcludeThe only category where AI Overviews plausibly cannibalises a paid-content or ad-funded model rather than feeding it.Excluding forfeits all AI-surface impressions on a channel Google says reaches billions of users monthly.
Ecommerce / retailInclude (stay in)Product and category pages benefit from appearing in shopping-oriented AI answers; the toggle does not touch Merchant Center or Ads.Little downside to staying in; opting out removes a discovery surface for high-intent queries.
SaaS / B2BInclude (stay in)Comparison and how-to queries are where AI Overviews surface vendor content; visibility tends to support pipeline, not erode it.Opting out trades measurable brand exposure for a hard-to-quantify referral-protection benefit.
Agency / marketing siteInclude (stay in)Being cited in AI answers is itself a credibility signal for a services business; there is no paywalled inventory to protect.Excluding mostly removes your own authority signals from a growing surface.
Niche / membership contentMeasure firstIf the content is the product (courses, research, gated depth), AI summarisation may substitute for the visit.Check the Generative AI performance report before deciding; impressions may be lower than feared.
Local / service businessInclude (stay in)Local-intent queries rarely have a substitutable answer in an AI summary; the click still has to happen to book or buy.Opting out offers almost no upside and removes a free visibility surface.

Notice the pattern: only one row leans toward exclusion, and even then only after measurement. The sites most likely to misread this are non-publishers who opt out reflexively to “protect” traffic that was never at risk — and in doing so remove themselves from a discovery surface Google says is growing quarter over quarter. The matrix is a starting point; pressure-test it against your own Generative AI performance data. If you want help running that analysis across a property estate, our agentic SEO engagements start with exactly this kind of AI-surface visibility audit.

07Regulatory BackdropWhy the UK got it first, and what the timeline requires.

This control did not arrive because Google chose to ship it voluntarily. On June 3, 2026, the UK Competition and Markets Authority issued a legally binding conduct requirement — the world’s first such mandate — ordering Google to give publishers genuine opt-out controls over AI Overviews, AI Mode and related AI features. Google launched the Search Console toggle to a subset of UK owners the same day. The regulatory basis is the Digital Markets, Competition and Consumers Act 2024, under which Google was designated as holding Strategic Market Status in general search in October 2025. For the full SEO-strategy read on that ruling, see our analysis of the CMA’s world-first opt-out order, which covers the regulatory and ranking angle this how-to deliberately leaves aside.

The order sets hard deadlines, and they are worth tracking because they signal how the controls will deepen. The timeline below recomputes each milestone’s distance from the June 3 announcement so you can see the cadence at a glance.

CMA implementation timeline for Google publisher controls. Columns show each milestone, its date, the elapsed time from the June 3, 2026 announcement (derived from the milestone dates), and the cadence or status. Deadline figures are from the GOV.UK / CMA press release of June 3, 2026.
MilestoneDateFrom June 3, 2026Status
CMA conduct requirement + GSC toggle launchJune 3, 2026Day 0Announcement
Control takes effect (toggles start changing AI surfaces)June 17, 2026≈ 2 weeksLive for a UK subset
Main publisher controls (opt-out of grounding) requiredDecember 2026≈ 6 monthsHard deadline
Page-level grounding controls requiredMarch 20279 monthsHard deadline

Two clarifications keep this in proportion. First, the order requires Google to carry clear attribution links to source content inside AI answers — opt-out is one lever, fairer crediting is another. Second, the separate fine-tuning restriction the CMA imposed applies to future use only; it does not retroactively pull content already embedded in model weights. A senior Google representative acknowledged at a February 2026 conference that building these publisher controls was “a huge engineering project”, according to secondary reporting of an unnamed source — precisely because the hard part was blocking content from AI features while keeping the same pages indexed and ranked normally in conventional results.

08What It MeansThe strategic read for most sites.

Strip away the regulatory drama and the practical position is steady. A control that removes AI-surface appearance without touching rankings is a genuine win for the narrow set of publishers whose business model is threatened by summary-instead-of-visit dynamics. For everyone else — ecommerce, SaaS, agencies, local services — the correct default is to stay in, because being present in AI answers is a discovery and credibility surface, not a leak. The asymmetry is the whole story: the downside of staying in is mostly hypothetical, while the downside of opting out is a measured loss of impressions on a fast- growing channel.

Looking forward, expect the surface area of these controls to expand rather than contract. The CMA timeline already mandates page-level grounding controls by March 2027, which points toward finer-grained, per-URL decisions instead of one blunt site-wide switch — and Google plans a global expansion after UK testing, though no date has been announced. The teams that win are the ones treating this as a measurement discipline, not a binary panic button: instrument AI-surface impressions now, decide per-property, and revisit as the controls and the underlying click economics evolve. That is the same posture we bring to the broader question of AI Overviews SEO strategy, and it is the right one here too. If you would rather not run that instrumentation yourself, our analytics and measurement service sets up the reporting that makes the opt-out call evidence-based.

09ConclusionA real lever, used sparingly.

The shape of AI-surface control, mid-2026

The toggle separates AI appearance from ranking — most sites should still stay in.

Google’s Search Console control is a meaningful piece of infrastructure: for the first time a publisher can be pulled out of AI Overviews, AI Mode and AI Overviews in Discover while staying fully indexed and ranked. The mechanics that matter are the narrow scope — three surfaces, not the Gemini app and not training — the parent-to-child inheritance cascade, and the one-to-two-day propagation. Get those three right and you understand the control better than most of the coverage around it.

The judgement call is simpler than the discourse suggests. Because opting out never touches rankings, there is no defensive reason to do it; the only real reason is a business model where AI summarisation substitutes for the visit, and even then the move should follow the Generative AI performance report rather than precede it. For the overwhelming majority of commercial sites, the right setting is Include — measured, monitored, and revisited as the surfaces grow.

This is also a preview of a longer arc. A UK-first regulatory mandate produced the first control; finer page-level controls are required by March 2027, and a global expansion is planned. The sites that come out ahead will be the ones that built the measurement habit early — instrumenting AI-surface impressions, deciding per-property, and treating “should we opt out?” as a question with a data answer, not a reflex.

Make the AI-surface call evidence-based

Decide AI Overviews opt-out with data, not reflex.

We help businesses measure AI-surface visibility, decide opt-out by property, and protect organic performance as AI search reshapes the click economy — set up in days, not quarters.

Free consultationExpert guidanceTailored solutions
What we work on

AI-search visibility engagements

  • Generative AI performance audits across a property estate
  • Opt-out decisioning by site type and AI-surface exposure
  • Inheritance mapping for multi-subdomain, multi-country setups
  • Google-Extended vs toggle vs noindex control strategy
  • AI Overviews monitoring and click-economy reporting
FAQ · Search Console AI controls

The questions teams ask before opting out.

It is a toggle in Google Search Console under Settings → Search generative AI that determines whether your content can appear in three Google AI surfaces: AI Overviews, AI Mode, and AI Overviews in Discover. Each property can be set to Include (stay eligible), Exclude (opt out of those surfaces), or Inherit from parent. It is a grounding control — it governs real-time appearance in AI answers, not how Google crawls, indexes or ranks your pages. It launched UK-first on June 3, 2026 under a CMA mandate and took effect on June 17. As of late June 2026 it is available only to a subset of UK website owners, with a global expansion planned but no date announced.