You can now tell Google to leave your site out of its AI answers — without leaving Google Search itself. That sentence would have sounded impossible two years ago, when the only way to block an AI summary was to block Search altogether. Today it is a real switch, sitting inside Search Console, and it forces every publisher to answer a question that used to be theoretical: is being summarized worth more than being visited?
Here’s the short answer. Google’s Search generative AI control, available to all verified sites worldwide since August 31, 2026, removes your property from AI Overviews, AI Mode, and generative features in Discover. Your regular blue-link rankings are not supposed to change. What you give up is every impression, citation, and visit those AI surfaces would have sent you — and, just as important, you hand the answer to your competitors, because the AI Overview itself does not disappear when you leave it.
I have watched this control evolve from a UK-only concession into a global setting, and the most common mistake I see is treating it as a protest vote. It is not. It is a business decision with measurable trade-offs, a days-long lag, and a few sharp edges — like the fact that it does nothing about AI training, and that it works site-wide, not page by page. This article walks through exactly what the switch does, what it does not do, and how to decide before you touch it.
What the opt-out actually is
The control lives in Search Console under Settings, labeled “Search generative AI.” It offers three choices for each property: include (the default), exclude, or inherit from a parent property. That last option matters more than it looks: if you manage a domain property and a narrower URL-prefix property, the smaller one can silently follow the parent’s choice unless an owner overrides it. Check the inherited setting before you change anything, or you may think you flipped one site and actually flipped two.
Choosing exclusion tells Google’s systems not to return your property’s content within the covered AI features, and not to use it as grounding material for their generated responses. Your pages stay crawled and indexed. Your regular rankings are unaffected — Google says the control is not used as a ranking or inclusion signal elsewhere in Search, and the UK Competition and Markets Authority’s June 2026 Publisher Conduct Requirement separately prohibits Google from penalizing publishers for using it, including by downranking them relative to opted-in content.
The timing is not instant. Google’s help text says exclusion generally takes effect within one to two days, with some content taking longer because of caching and propagation across its systems. The same lag applies in reverse when you turn it back on. Treat the switch as a test you run for weeks, not a lever you flick on a bad traffic day.
One more piece of context: this control did not arrive as a generous product decision. Google rolled it out in the UK on June 3, 2026, the same day the CMA imposed its first binding conduct requirement on Google, and completed the global rollout on August 31, 2026. Google refreshed its “control what you share” documentation again on October 21, 2026, folding the Search generative AI control into its main sharing guide alongside the older snippet and indexing controls. That October refresh is why you are hearing about it again now — the switch itself is not new, but Google’s own documentation finally presents it as a first-class option rather than a footnote.
What opting out does NOT do
This is where publishers get hurt, because the gaps are easy to miss.
It does not stop AI training. The Search generative AI control covers surfacing in Search’s AI features only. If your concern is Gemini or other models being trained on your content, that is a separate mechanism: Google-Extended, the robots.txt user-agent token that signals training preferences. Flipping the Search Console switch and assuming your content is out of training data is simply wrong, and it is the single most common misunderstanding in coverage of this topic.
It does not remove the AI answer. When you opt out, Google builds the Overview for your keywords from other sites’ content instead. Your competitors get cited; you do not. If your goal was to starve the AI answer of good information, opting out alone achieves the opposite for your own visibility.
It does not work page by page. The Search Console control is site-wide per property. You cannot exclude your ten highest-value guides and keep your news posts in. Page-level grounding controls are tied to the CMA’s timetable, which requires them by March 3, 2027 — nine months from the June 2026 requirement. Until then, selective exclusion has to be done with the older, blunter tools below.
It does not override Merchant Center or Google Ads choices. Google’s help page is explicit that the control does not change settings you have made in those products. If you run a store or ads alongside your content, check those surfaces separately.
It does not stop crawling. Google still crawls and indexes your pages normally. If you wanted to disappear from Search, this is not the tool — and that is exactly the point. The whole value of the control is that it separates generative visibility from ordinary Search visibility for the first time.
The page-level tools you still need
Because the big switch is all-or-nothing, most publishers will actually use a mix. Here is the honest toolkit, with the trade-off of each:
nosnippet
Add a nosnippet robots meta tag to a page and Google will not show a text snippet for it — and will not use its content directly in AI Overviews or AI Mode. The cost: your regular search snippet disappears too, which can hurt click-through on the very pages you are trying to protect. Use it on pages where the snippet itself is the product — a paywalled answer, a proprietary table, a page whose value dies if it is summarized.
data-nosnippet
Wrap a specific section of HTML in data-nosnippet and only that section stays out of snippets and AI answers. This is the scalpel. A pricing table, a key paragraph, or a data table you spent a week building can be fenced off while the rest of the page stays fully eligible. If you are going to protect anything surgically, start here.
X-Robots-Tag
The same rules, delivered as an HTTP header instead of a meta tag. This is how you apply snippet rules to files that are not web pages — PDFs, downloads, documents. If your best content lives in a PDF, a meta tag cannot help you; this can.
What not to do
Do not reach for noindex to block AI answers. That removes the page from regular Google results entirely — a far bigger hit than most publishers intend, and one that is easy to forget you applied. And do not assume blocking a page in robots.txt hides it: Google has to crawl a page to read its instructions, and its guidance warns that a blocked URL can still show in results. If you change any indexing rule, use Search Console’s URL Inspection tool and compare the stored version with a live test, because the two can differ for a while.
What you actually give up: the numbers behind the decision
A decision this consequential deserves real numbers, not vibes. Here is what the public data says, with the caveats attached.
Pew Research found in March 2025 that when an AI Overview was present, users clicked a traditional search result in roughly 8 percent of visits, versus about 15 percent when no Overview appeared — roughly half. The click-through rate on Overview citation links themselves was about 1 percent. That is a sobering pair of numbers, and it explains why publishers are angry: the Overview both suppresses the old click path and offers a weak replacement.
But the same numbers cut the other way. A 1 percent citation click rate on a query that gets thousands of Overview impressions is still real traffic, and cited brands build recognition that later arrives as branded search or direct visits — traffic that never shows up in an AI report. Seer Interactive’s data, cited in recent coverage, found cited brands earning about 35 percent more organic clicks than uncited ones. I would not treat that figure as gospel, but the direction is consistent with what site owners report: disappearing from the answer does not return you to the old world; it removes you from the new front door.
The traffic damage is also uneven. Chartbeat data reported in October 2026 found search referrals down about 60 percent over two years for small publishers, 47 percent for mid-sized ones, and 22 percent for large ones. If you are a small site, your pain is real and disproportionate — which is precisely why the opt-out tempts you, and precisely why you should measure before you act. A small site that opts out gives up the one surface where a good answer can still outrank a big brand’s domain authority.
That is why the Generative AI performance report in Search Console matters so much. It shows impressions for your pages in AI features, broken down by page, country, and device — but impressions only. No clicks, no click-through rate, no queries, no position, no conversion data. Google has said it is working with site owners on which additional metrics would be useful, but has published no explanation for why clicks were excluded. So you can see how often you appear, but not how often appearing pays. Any decision framework has to live with that blind spot.
The decision table: who should opt out, and who should not
| Your situation | Verdict | Why |
|---|---|---|
| Ad-supported content site whose articles are the product | Test exclusion on a property you can isolate | Your revenue dies when the answer replaces the visit; a test tells you whether AI traffic was ever converting |
| Local business, service provider, or lead-gen site | Stay in | Your goal is recognition and contact, not pageviews; a citation is a free ad |
| Affiliate or comparison site | Stay in, fence key tables with data-nosnippet | Your tables are your edge, but your traffic depends on being in the answer |
| Paywalled or subscription publisher | Consider exclusion for the paywalled property | If the summary gives away the answer, there is nothing left to sell |
| New or small site building authority | Stay in | You need every surface that can introduce you to a reader |
| Site with a few crown-jewel pages and lots of commodity content | Stay in site-wide, fence the crown jewels | The all-or-nothing switch punishes this exact profile; the snippet tools are your answer |
Notice what this table implies: for most publishers, the right answer is not the big switch at all. It is staying in, while using data-nosnippet on the specific assets a summary would cannibalize. The site-wide control is the right tool only when the whole property’s economics break under summarization.
Before you flip the switch: the checklist
If you are leaning toward exclusion, do these five things first, in order:
- Screenshot your baseline. Record 28 days of Search Console data: total impressions, total clicks, and the Generative AI report’s impression counts for your top 20 pages. Without a baseline, you cannot judge the test.
- Check property inheritance. Open Settings for every property you own, including domain and URL-prefix variants, and note which ones inherit. Change only the property you mean to change.
- Separate your surfaces. Decide what is a Search decision, what is a training decision (Google-Extended), and what is a Merchant Center or Ads decision. Write them down as three separate lines. Conflating them is how publishers accidentally break something else.
- Fence the crown jewels first. Before going site-wide, try
data-nosnippeton the tables or sections that worry you most, and watch for two weeks. You may find the surgical option solves 80 percent of the problem. - Set a review date. Exclusion takes days to take effect and days to reverse. Commit to at least four weeks, then compare the same 28-day window. A one-week test tells you nothing but noise.
And if you do flip it, tell your team what you did and why. I have seen sites where one person enabled exclusion during a traffic panic, left the company, and nobody discovered the setting for months. The switch is reversible, but only if someone remembers it exists.
How to turn it on (or off) in Search Console
The steps are short, which is part of the danger — a consequential decision should not feel this easy:
- Open Search Console and select the property you mean to change.
- Go to Settings, then find “Search generative AI.”
- Choose Include, Exclude, or Inherit from a parent property.
- Save, then verify the setting on any child properties that may inherit it.
- Wait at least several days, then check the Generative AI performance report to confirm impressions from AI features have stopped.
Reverse the same steps to opt back in. There is no penalty for testing, no waiting period, and no form to file.
My honest verdict
For the typical independent publisher reading this site, I would not opt out today. The AI answer is becoming the front door to Search whether we like it or not, and being cited — even at a 1 percent click rate — builds the kind of recognition that compounds. The publishers who should test exclusion are the ones whose entire product is the article itself and who can measure the test cleanly: subscription sites, paywalled research, and ad-supported sites where the AI report shows large impression counts on pages that earn nothing from them.
But here is the part I want you to remember if you disagree with me: the switch exists because publishers demanded a choice, and using it is not an act of war against Google. It is a setting, documented, reversible, and explicitly protected from ranking retaliation. The worst outcome is not opting in or opting out — it is never deciding, drifting along on the default while your traffic quietly changes shape underneath you. Measure your AI impressions this week. Then decide on purpose.
For a related publisher-control story, see how Meta delayed its website-crawling terms to November 20 while keeping the crawl clause intact — a reminder that platform controls are negotiated, not granted. And if your site depends on search traffic for revenue, our Google AdSense approval requirements for 2026 guide covers the quality bar that matters regardless of which AI setting you choose.
A worked example: three sites, three decisions
Abstract frameworks are easy to agree with and hard to act on, so here is how the decision plays out for three realistic sites.
The recipe blog with 400 posts and display ads. AI Overviews love recipe queries — they can summarize ingredients and steps in a neat card, and the reader never visits. But this blog’s Generative AI report shows most of its impressions come from broad queries (“easy weeknight dinners”) where it is one of eight citations, not the source of a unique answer. Staying in keeps the brand visible in the answer; the real fix is not the big switch but fencing the site’s unique assets — its tested variations, its substitution tables — with data-nosnippet, and adding content a summary cannot replace, like a printable meal planner or a video walkthrough. Verdict: stay in, fence the crown jewels.
The subscription newsletter that publishes one deep research post a week. Each post takes a week to research, sits behind a partial paywall, and converts readers at a rate the publisher can measure. The AI report shows its posts are being cited heavily, and the summary genuinely gives away the finding — the chart, the number, the conclusion. Free traffic from AI surfaces converts poorly because the reader already got the payoff. Verdict: test exclusion on this property for four weeks against the baseline, and watch subscription starts, not just traffic.
If you cannot tell which of these you are, you probably have not looked at your Generative AI report yet. That is step one, before any switch-flipping.
What the October 2026 docs refresh really changed
It is worth being precise about what happened on October 21, 2026, because coverage has blurred it. Google did not launch a new control that day. It revised its Search sharing guide to include the existing Search generative AI control alongside indexing and removal controls, and added robots meta tags, data-nosnippet, and X-Robots-Tag to the same guide. The documentation changelog describes a refresh of available choices, not a feature launch.
That distinction matters for two reasons. First, if you read a headline claiming Google “just gave” publishers an opt-out, you might think the switch is new and untested — it is not; it has been live globally since August 31, 2026, and in the UK since June. Second, the refresh is still meaningful: Google’s own guide is now the place where all seven ways to keep content out of Search are listed together, with the Search generative AI control explicitly labeled site-wide. For a publisher auditing controls, one authoritative page beats seven scattered blog posts. The external coverage of that refresh, including PPC Land’s breakdown of the seven blocking options and Search Engine Watch’s report on the sharing guide update, is worth reading alongside Google’s own documentation, because both flag the inheritance detail that Google’s guide buries in a diagram.
The broader context is regulatory, and it is moving. The CMA’s Publisher Conduct Requirement came into force in stages, with substantive obligations landing December 3, 2026, and page-level controls required by March 3, 2027. The European Commission’s formal investigation, opened in December 2025, is still running. US litigation has gone the other way for publishers so far — Penske Media’s and Chegg’s antitrust cases over AI Overviews were dismissed by a US judge on October 1, 2026, according to Press Gazette reporting. None of that changes the switch available to you today, but it does mean the control set will keep evolving, and a decision you make now should be revisited when page-level controls arrive in early 2027.
What the AI performance report can and cannot tell you
Let me be blunt about the measurement gap, because it shapes every decision in this article. The Generative AI performance report shows impressions: how often your links appeared in AI features, by page, country, and device. It completed its global rollout on August 31, 2026, alongside the control itself. What it does not show is clicks, click-through rate, queries, average position, citation placement, or conversions.
That means you can answer “are we in the answers?” but not “does being in the answers pay?” You have to bridge that gap with proxies: compare total Search Console clicks for your top AI-impression pages against a period before AI features covered those queries, and watch branded search volume, which captures recognition that later converts. None of these are clean. All of them beat guessing.
Frequently Asked Questions
Does opting out of AI Overviews hurt my Google rankings?
No, according to Google’s documentation and the UK CMA’s conduct requirement. The Search generative AI control is not used as a ranking or inclusion signal for regular Search. Your blue-link rankings should be unchanged; what changes is your presence in AI Overviews, AI Mode, and generative features in Discover.
How long does the opt-out take to work?
Google says exclusion generally takes effect within one to two days, with some content taking longer due to caching and propagation across its systems. The same lag applies when you opt back in, so judge any test over weeks, not days.
Can I opt out just one page or section?
Not with the Search Console switch, which is site-wide per property. Page-level grounding controls are required under the CMA timetable by March 3, 2027. Until then, use nosnippet for a whole page or data-nosnippet for a specific section.
Does the opt-out stop Google from training AI on my content?
No. The Search generative AI control covers surfacing in Search’s AI features only. Training restrictions are a separate mechanism, signaled through Google-Extended. You need both settings if you want both outcomes.
If I opt out, will the AI Overview disappear for my keywords?
No. The Overview still appears, built from other sites’ content. Opting out removes you from the answer; it does not remove the answer from the results page.
Where do I find the control in Search Console?
Go to Search Console, select your property, then Settings, then “Search generative AI.” Choose Include, Exclude, or Inherit from a parent property — and check child properties for inherited settings before you save.