Google's AI opt-out control is live for every site. Should you use it?

On 31 August 2026 Google finished rolling out the Search Console setting that lets any site owner remove their content from AI Overviews and AI Mode. The question arrived in a lot of inboxes the same week, usually phrased as "can we turn off the thing that is eating our clicks?" You can. It is worth understanding what the switch does before you reach for it, because it does not do the thing most people want it to do.

What the control actually is

Google Search Console now carries a setting, at the property level, that governs whether your content is eligible for Google's generative AI surfaces. It launched on 3 June 2026 for a subset of UK site owners, after the UK's Competition and Markets Authority pushed for site-owner controls over AI Overviews. Google began honouring exclusions on 17 June 2026, and the worldwide rollout completed on 31 August 2026. Every verified property now has it.

Two details matter more than the headline. The control is property-level: you cannot exclude your blog and keep your product pages in, unless those live on separate verified properties. And it blocks two distinct uses at once — appearing as a cited link inside an AI answer, and being used as grounding material for the answer's text. You cannot keep the citation and refuse the grounding, which is what a lot of publishers would actually like.

Alongside it, Google shipped the AI performance report, which shows impressions from AI Overviews and AI Mode broken down by page, country, device and date. It combines both surfaces into one figure, and it carries no click data and no query data. That limitation is the reason this decision is harder than it looks: the report tells you how often you appeared, and nothing about what appearing was worth.

The three mechanisms people confuse

Most of the bad advice circulating about this control comes from treating four separate mechanisms as interchangeable. They are not, and two of them will cost you traffic you did not intend to give up. Here is what each one actually does.

The Google-Extended row is the one that catches experienced teams. A great many sites added User-agent: Google-Extended / Disallow: / to robots.txt in 2023 and 2024 believing it kept them out of AI Overviews. It never did, and it still does not. If that line is in your robots.txt, it has been quietly excluding you from Gemini grounding for two years while your content continued to feed AI Overviews exactly as before. Worth checking this week, whichever way you decide on the new control.

The nosnippet row is the trade the new control was built to eliminate. Before June 2026, keeping a page out of AI Overviews meant giving up its ordinary snippet, which for most pages costs far more than the AI feature ever did. Anyone still using nosnippet as an AI-blocking tactic should move to the Search Console control and get their snippets back.

What you actually give up

Start with the honest version of the traffic argument, because the traffic argument is real. Pew Research Center's behavioural study of 68,879 real Google searches found that users clicked a traditional search result on 8% of searches where an AI summary appeared, against 15% where one did not. Clicks on links inside the AI Overview itself occurred in roughly 1% of cases. Sessions ended after the search 26% of the time with an AI summary present, against 16% without. AI Overviews suppress clicks. That is measured, not disputed.

The error is the inference that follows: that removing yourself from the AI Overview restores the click. It does not, and this is the pivot the whole decision turns on. The control removes your site from the answer. It does not remove the answer from the results page. The AI Overview still generates for that query, built from whichever sources remain — which on a commercial query means your competitors, review aggregators, marketplaces and forums. Your blue link stays exactly where it was, below the same summary, now without your name in it.

So the real comparison is not "AI Overview versus ten blue links". It is "an AI answer that cites you versus an AI answer that cites someone else". Framed that way, most commercial sites are choosing whether to be present in the answer their buyers read, not whether the answer exists.

Work out your own number first

The AI performance report gives you impressions with no clicks, so you cannot read the answer directly off a dashboard. You can bound it, which is enough to make the decision. Four steps, about twenty minutes:

1. Pull AI impressions by page for the last three months from the AI performance report in Search Console. Note the top 20 pages and the total.
2. Pull the same period from the standard Search performance report and calculate your site-wide organic CTR. This is your best available proxy for what an impression is worth to you.
3. Set the upper bound. AI impressions multiplied by your organic CTR. This is the most traffic that could plausibly be at stake, and it is an overestimate, because clicks from within AI answers run far below normal SERP CTR — Pew measured around 1%.
4. Set the realistic band. Somewhere between AI impressions × 1% and AI impressions × your organic CTR. If the top of that band is not a number that changes a business decision, the whole question is smaller than it feels, and you should spend the afternoon on something else.

Two cautions on interpretation. Impressions are not uniform: a fraction of your pages will carry most of them, and those are usually definitional or comparison pages rather than money pages. And the number you produce is what you lose by opting out. There is no corresponding gain column, because opting out does not move your ranking and does not remove the AI answer. That asymmetry is the point.

A decision framework by business model

The right answer genuinely differs by what your content is for. It splits cleanly on one question: is your content the product, or the route to the product?

If you are in the top two rows, the control is genuinely useful and it is the first time Google has offered it without a snippet penalty attached. If you are in the bottom four, the honest reading is that you are annoyed about AI Overviews, which is reasonable, and that switching yourself off is not a response to it.

Treat it as a decision, not a test

You may be tempted to flip it on for a month and watch what happens. That does not work cleanly, for three reasons. Exclusions take effect within about a day or two but caching can delay it, so your start and end dates are fuzzy. The AI performance report has no click data, so the metric you most want to compare does not exist. And ordinary organic traffic moves for a dozen other reasons in any given month, including core updates, so a single-site before-and-after is not evidence of much.

If you are determined to experiment, the only structurally sound version is a property-level split: a separate verified property, on a separate subdomain, carrying comparable content, with one excluded and one not. Most businesses do not have that setup and should not create it for this.

What to do instead, in most cases

For the majority of sites, the productive response to AI Overviews is not a switch at all. It is the same work that gets you cited rather than summarised away:

• Answer the question in the first sentence under the heading. Extractable answers get cited. Preambles get skipped. We covered the mechanics of this in our guide to optimising for AI search.
• Publish the thing the summary cannot replace. Original data, a pricing model, a comparison table, a method with numbers in it. A summary of a generic explainer is a complete substitute for it; a summary of a calculation is an advert for the calculation.
• Check your AI impressions against your money pages. If your AI visibility is concentrated on definitional posts and absent on service and product pages, that is a content structure problem worth more than the opt-out debate.
• Fix the two robots.txt and snippet mistakes above before you consider anything more exotic. They are more common than anyone admits, and they cost real traffic today.

None of this is new work. It is the work that made pages rank before AI Overviews existed, applied with more discipline about where the answer sits on the page. If the pages carrying your AI impressions are not the pages that generate business, that is a case for better site structure and content design, not for going dark.

Frequently asked questions

What is the Search generative AI control in Search Console?

It is a property-level setting in Google Search Console that decides whether a site's content can appear in and be used by Google's generative AI features: AI Overviews, AI Mode and AI Overviews in Discover. Google launched it on 3 June 2026 to a subset of UK site owners, began honouring exclusions on 17 June 2026, and completed the worldwide rollout on 31 August 2026. It applies to the whole verified property, not to individual pages.

Does opting out of AI Overviews hurt your Google rankings?

No. Google has stated that the generative AI control is not a ranking signal and that using it does not affect a site's position in regular Google Search results. Your pages stay indexed, stay eligible for blue links, and keep their normal snippets. What changes is that the site stops being eligible to appear as a link inside AI Overviews and AI Mode, and stops being used to ground those answers.

Does opting out remove the AI Overview from searches about my brand?

No. The control removes your site from the answer, not the answer from the results page. Google will still generate an AI Overview or AI Mode response for that query using other sources, which for competitive commercial queries usually means your competitors, review sites and forums. This is the single most common misunderstanding about the control: opting out subtracts your voice from the answer rather than restoring the click.

Is the generative AI control the same as blocking Google-Extended in robots.txt?

No, and confusing the two is the most common technical error. Google-Extended is a robots.txt token that governs whether content is used to improve Gemini models and to ground responses in Gemini Apps and Vertex AI. Blocking Google-Extended does not remove a page from AI Overviews or AI Mode, because those features are served from the regular Google Search index crawled by Googlebot. Only the Search Console generative AI control affects AI Overviews and AI Mode.

Can I use nosnippet to stay out of AI Overviews instead?

You can, but it is a blunt instrument. The nosnippet, data-nosnippet and max-snippet directives govern the preview text Google is allowed to show, so applying them removes a page from AI Overviews and also strips its snippet from ordinary search results. That usually costs more traffic than the AI feature ever did. The generative AI control exists precisely so site owners no longer have to make that trade.

How long does the opt-out take to apply, and is it reversible?

Google began respecting opt-out changes on 17 June 2026 and content generally drops out of the AI features within one to two days, though caching can delay it. The setting can be switched back on, but treat it as a decision with a lag in both directions rather than an A/B test: you cannot cleanly measure the effect, because the AI performance report shows impressions with no click or query data, and both exposure and re-inclusion take days to settle.

Who should actually opt out of Google's AI features?

The clearest cases are sites whose content is the product rather than a route to it: subscription and paywalled publishers, licensed research and data businesses, and sites with contractual restrictions on how their content may be reused. For lead generation businesses, e-commerce stores, SaaS products and local service businesses, opting out removes visibility from the surface where buyers now shortlist without recovering any clicks, so the answer is almost always no.

The takeaway

The control is a genuine improvement on what came before: for the first time you can stay out of Google's AI answers without surrendering your search snippet, and Google has been explicit that it carries no ranking cost. It is the right tool for publishers whose content is the product. For everyone else, the arithmetic runs the other way. You would be removing yourself from an answer that will be written regardless, for no recovered clicks and no ranking benefit, on a surface where your buyers are increasingly building their shortlist. Check your robots.txt for the Google-Extended line you forgot about, pull your AI impressions and bound the number, then in all likelihood leave the switch alone and go and make the pages more citable.