How to opt out of AI Overviews without losing Search

The short version

Sources: Search generative AI control, AI features and your website, Google common crawlers, Generative AI performance report and Search Console performance report, all read September 2026.

Three controls, three different jobs

Almost every “protect your content from AI” guide collapses three separate Google controls into one instruction, usually “add Google-Extended to your robots.txt”. Google documents them on three different pages, and they do not overlap the way the advice assumes.

The wording matters. Google describes Google-Extended as what publishers use “to manage whether content Google crawls from their sites may be used for training future generations of Gemini models”, and names the systems: Gemini Apps and the Vertex AI API for Gemini. AI Overviews and AI Mode are not in that list. They are features of Google Search, and Google gives them their own switch.

The third row explains why the old advice ever worked at all. Google states that “to be eligible to be shown as a supporting link in AI Overviews or AI Mode, a page must be indexed and eligible to be shown in Google Search with a snippet”. Kill the snippet and you fall out of AI features as a side effect — along with the description under your own listing. It is a real exit through a door you would not choose.

Worth noting that Google’s own surfaces are not in step here. The developer guidance on AI features still points readers to snippet controls and to Google-Extended, and did not mention the Search generative AI control in either of the two passes we made over it. The dedicated control is documented in Search Console Help instead, which is a fair part of why the advice in circulation is out of date.

The control itself, and what it costs

Google describes it in one sentence: “Use the Search generative AI control to manage your site’s inclusion in the following generative AI features on Google Search.” It then lists AI Overviews, AI Mode and generative AI features in Google Discover. You find it “under Settings > Search generative AI in Search Console”.

Three limits are published alongside it, and all three are the kind that change a decision:

• It is not a ranking signal. Verbatim: this control “only affects whether your content can appear in certain Search generative AI features; this control isn’t used as a ranking or inclusion signal affecting other parts of Search”.
• It does not take your content out of Search. Google says “your site’s content may still be used to power Google Search as a whole”. This is an appearance control, not a data-use control.
• It does not touch AI training. Google is explicit that it “doesn’t affect AI training” and points to Google-Extended for that — which is the same distinction as the table above, stated from the other side.

Switching it is also not instant. Google says a change “generally takes a few days” and that “some content may take longer to be excluded due to caching”. That matters mostly because it rules out using this as a quick A/B test: you cannot flip it on Monday and read the result on Wednesday.

What you get, then, is unusually clean for this subject. One switch, scoped to the AI surfaces, with a published statement that the rest of Search is unaffected. Compare that with the equivalent decision on other platforms this site has read at source — where, for instance, pulling an Ezoic integration for more than seven days permanently voids a grandfathered account — and the reversibility here is the notable part.

Impressions yes, clicks no

Google now publishes a Generative AI performance report for Search, covering AI Overviews and AI Mode. It defines its metric narrowly: impressions are “how many times links to your site were shown to a user in a generative AI feature on Google Search”. The usual Search performance constraints apply, including “the 1,000 row limitation”.

No click metric is documented for that report. Meanwhile, in the ordinary performance report, AI traffic is folded in rather than separated: Google states that “clicking a link to an external page in the AI Overview counts as a click” and that for AI Mode “clicking a link to an external page in AI Mode counts as a click”, with standard impression rules in both cases.

Put those together and you get a specific, awkward gap. You can now see how often AI features showed your pages, and you can see your total Search clicks with AI clicks mixed into them — but you cannot isolate what AI features actually sent you. That is precisely the figure the opt-out decision turns on. If AI Overviews are showing you 40,000 times a month and sending nobody, opting out costs you little; if they are sending a third of your traffic, opting out is self-harm. Google publishes the first half of that sum and not the second.

One related limit is documented and worth knowing if your numbers look thin: “Search Console doesn’t include data from experiments in Search Labs, as these experiments are still in active development.” Newer AI surfaces may therefore not be counted anywhere yet.

Google has started paying for AI answers

This section is the one part of this page not read from a Google document. It rests on press reporting from September 2026, and we flag it that way because it is the newest and least settled thing here.

Reporting describes an invitation-only programme called the AI contribution pilot, in which Google pays participating publishers when their content contributes significantly to an answer in the Gemini app, AI Overviews or AI Mode. Publishers who accept the terms get a panel in Search Console showing a monthly earnings figure with some history. Google confirmed to reporters that it is an early-stage pilot intended to test how to reward high-quality content on top of the traffic and tools it already provides, and publishers are described as able to leave at any time.

Two details are worth carrying even at second hand. The first is the line Google is reported to draw: content earns when it shapes the answer during generation, while merely being linked to after a response has been produced is reported not to qualify. The second is that nobody outside can see the method — participants are reported to see an earnings number without being told which pages earned it or how it was calculated, and one executive described it as “quite black box”. Early sums are reported as small relative to advertising.

For a site the size of this one’s readers, the practical answer is blunt: there is no application route, no published rate and no published eligibility test, so this is not a plan. What it does change is the shape of the opt-out decision. The surface you would be switching off is the same surface the pilot pays from, so turning it off forecloses an upside you cannot currently measure, quantify or apply for.

What we would actually do

For a small publisher monetising with display ads or affiliate links, the asymmetry points one way. Leaving the AI surfaces on is reversible in a few days and costs nothing you can currently observe. Opting out is also reversible, but it gives up an unmeasured referral stream plus whatever the pilot eventually becomes, in exchange for a benefit nobody can put a number on.

So: leave it on, and go read the generative AI report before you touch anything. If your AI impressions are large and your overall Search clicks have fallen, you at least have the two halves of an argument. If AI impressions are negligible, the whole question is noise for your site and you can stop thinking about it.

Blocking Google-Extended is a separate decision and a genuinely cheap one: Google states that it “does not impact a site’s inclusion in Google Search nor is it used as a ranking signal in Google Search”. If you object to your work training Gemini, that is the lever, and it costs you nothing in Search. Just do not expect it to change what appears in an AI Overview, because Google does not say it will.

The one action we would not take is the old one. Reaching for nosnippet to escape AI Overviews now means accepting a stripped Search listing to achieve something a purpose-built switch does for free.

Related reads: AdSense approval and payout mechanics, how the display ad network entry rules inverted, finding low-competition keywords, building a high-traffic display ad blog, and what Microsoft Clarity actually keeps.

What we could not verify

Stated plainly rather than filled in with figures we could not read at source.

• The AI contribution pilot, entirely. Every detail in that section comes from press reporting, including Google’s own quoted statement. We found no Google help page, blog post or documentation describing the pilot, its rates, its eligibility or its terms. No earnings figure appears anywhere on this page.
• Whether opting out affects the pilot. The obvious question — does using the Search generative AI control remove you from the pool Google pays from? — is answered nowhere we could find. We state the surfaces overlap and deliberately draw no conclusion about the payment consequence.
• Any click data for AI features. Google documents impressions in the generative AI report and counts AI clicks inside ordinary Search totals. We found no way to isolate AI clicks, and we publish no estimate of what share of traffic AI features send.
• Whether the developer guidance is simply behind. Google’s AI features page points to snippet controls and Google-Extended and does not mention the Search generative AI control. We read it twice with different prompts and report the discrepancy rather than assuming which page is authoritative.
• The rollout date of the control. Reporting puts the worldwide rollout of the generative AI reports and control in late August 2026. Google’s help pages carry no date we could read, so no rollout date is asserted above.
• Whether Google-Extended affects AI Overviews in practice. Google names the systems Google-Extended covers and AI Overviews is not among them, which is the basis for the finding above. Google does not anywhere state the negative in so many words, so this is our reading of its published scope rather than a quoted denial.
• Enforcement and effect, entirely. Everything here is published wording. We have not tested the control on a live site, measured how long exclusion really takes, or verified that it works as described.

FAQ