Google now gives every site owner a switch for its AI answers — and most bloggers have never looked at it. The Search generative AI control in Google Search Console lets you pull your content out of AI Overviews, AI Mode, and generative features in Google Discover, while staying in regular Google Search. It rolled out to all websites worldwide on August 31, 2026, and on October 21, 2026, Google folded it into its main “control what you share with Google Search” documentation, which is why you’re hearing about it now. Coverage of that documentation refresh from Search Engine Watch and PPC Land confirms the same key detail: the update organized existing controls rather than launching a new feature.
Here’s the short answer up front: for most small blogs, staying in is still the better default — but the decision is real, it’s reversible, and it’s yours to make with eyes open. The control is site-wide, not per-page, and opting out costs you whatever impressions and clicks those AI surfaces would have sent you. What it does not do is just as important: it doesn’t hurt your regular rankings, it doesn’t stop Google from training AI models on your content, and it doesn’t remove you from Search. If anyone tells you flipping this switch is a protest that “takes your content back” from AI, they’re selling you something that isn’t true.
I’ve watched this debate swing from panic to shrug and back again all year, and the honest version is less dramatic than either extreme. This guide walks through exactly what the control does, the four things bloggers most often get wrong about it, a decision framework for your own site, and the page-level alternatives if you only want to protect some of your content.
What the Search generative AI control actually does
The control lives in Search Console under Settings, and it offers three choices: include (the default), exclude, or inherit from a parent property. If you run one blog on one domain, you almost certainly have one property and the choice is simply include or exclude. If you run several properties — say, a domain property and a URL-prefix property for a subdomain — a smaller property can inherit the parent’s setting unless an owner overrides it, so check before you change anything.
Choosing exclude means your site’s links and content stop appearing in AI Overviews, AI Mode, and generative AI features in Discover, and your content is no longer used to ground those AI responses. Google says excluded sites receive no impressions or traffic from those features. That’s the cost, stated plainly: you are giving up a growing surface of Google Search, not just a trickle.
Google also says three things the control is not:
- It is not a ranking signal. Excluding your site from AI features does not push your regular blue-link results down. Your classic search presence stays as it was.
- It does not affect AI training. If your worry is that Google’s models learned from your writing, this switch does nothing about it. Google points publishers to Google-Extended, a separate robots mechanism, for training-related choices — and even that story has a wrinkle, which I’ll get to below.
- It does not override Merchant Center or Google Ads choices. Those surfaces have their own settings.
Exclusion generally takes effect within one to two days, though Google warns caching can delay some content. In other words, don’t flip the switch on Monday morning and expect every AI answer citing you to be gone by lunch. Plan for a few days of lag, and don’t judge the results of the change in the first week.
The four mistakes bloggers keep making about this switch
Mistake 1: Thinking “opt out” means “Google can’t use my content at all”
This is the big one, and it’s understandable, because Google’s controls have overlapping names. The Search generative AI control governs one thing: whether your content shows up in and grounds Google’s generative Search features. It is not a training opt-out. Google-Extended is the separate mechanism Google documents for certain Gemini and Vertex AI training uses. And even there, the picture is murkier than a clean opt-out suggests: in 2025, testimony in the US antitrust proceedings revealed that when Gemini was placed inside the search organization to power AI Overviews, the search team could use publisher data that publishers had opted out of for training — “for use in search,” as Google’s DeepMind VP put it at the time. The lesson isn’t that controls are useless. It’s that each control has a narrow, specific job, and you should never assume one switch covers everything.
Mistake 2: Flipping it in anger after a traffic drop
Traffic drops hurt, and the temptation to “punish” Google by opting out is real. But opting out removes you from AI surfaces entirely — including the citations that now sit higher in AI answers since Google’s October 15, 2026 redesign, which moved inline source links up and made them more prominent. If your pages are the kind that get cited — specific, well-sourced, directly useful — opting out trades away the one AI placement that actually sends clicks. Before you flip anything, check your numbers: open Search Console’s Performance report, look at the Generative AI features report (in beta), and see whether your AI impressions are rising, flat, or negligible. The Generative AI report shows impressions by page, country, device, and date — but, critically, it does not show clicks, average position, or queries as of October 2026. Impressions are a visibility metric, not a traffic metric. A page can rack up AI impressions while its clicks flatline, and that’s a real pattern publishers are seeing. Make the decision on your own data, not on vibes.
Mistake 3: Using noindex or robots.txt to “block the AI”
This is the most expensive mistake on the list. Adding noindex to a page removes it from regular Google results too — a far bigger hit than most bloggers intend. Blocking a page with robots.txt has its own trap: Google has to crawl a page to read the instructions on it, and Google’s own guidance warns that a blocked URL can still show up in results. If you want to keep a page in Search but out of AI answers, the Search generative AI control (site-wide) or snippet rules (page-level, below) are the tools built for that job. Don’t reach for the sledgehammer when the scalpel is sitting right there.
Mistake 4: Assuming you’re already opted out — or already in — without checking
Include is the default for every property. If you’ve never touched the setting, you’re in. But if a predecessor, an SEO contractor, or an old experiment changed it during testing, you could be excluded without knowing it — and quietly missing AI-surface impressions. The check takes thirty seconds: Search Console, Settings, Search generative AI. While you’re there, note whether your property inherits from a parent. Inherited settings are the classic “but I never changed anything” surprise.
The decision framework: stay in, opt out, or go page-level
There’s no universal right answer here, because the sensible choice depends on what your content is, how it earns, and where your readers come from. Work through these four questions honestly:
1. Does your content earn when someone reads the full page? If your money comes from display ads, affiliate clicks, email signups, or a product sale that needs the full article, then AI answers that satisfy the question on the results page are a real threat to you — but so is invisibility. A cited source link in a prominent AI answer still sends some readers through, and it’s the only AI placement that does. For ad-supported blogs, staying in and fighting to be the cited source usually beats disappearing entirely. If your content is the kind AI answers can fully replace in two sentences — a definition, a single fact, a simple conversion — the click was probably already lost, and opting out at least stops your work from powering the replacement for free. That’s a principled stand, and for some publishers it’s the right one, but go in knowing it likely won’t restore the lost clicks.
2. Is your content the kind AI answers cite, or the kind they summarize? Pages that get cited tend to be specific: named products, real prices, dated rules, step-by-step processes, original data. Pages that get summarized and skipped tend to be generic. If your blog is full of the first kind, the AI surface is working for you at least some of the time. If it’s full of the second kind, the switch matters less than rewriting the content — a hard truth, but a useful one.
3. How much of your traffic comes from Google at all? A blog that gets 80% of its visits from Google Search faces a different risk calculation than one that gets 30% from search and the rest from newsletters, social, and direct visits. The less dependent you are on Google, the freer you are to make the principled choice. And if you’re heavily dependent, the single best investment isn’t this switch — it’s building a direct channel (an email list, a community) so the next Google change doesn’t decide your income. Publishers who’ve weathered this year’s AI shift keep saying the same thing: use search to help people discover you, then build a relationship that gives them a reason to return directly.
4. Do you have a measurement plan? Whatever you choose, decide in advance how you’ll judge it. If you opt out, compare your regular Search clicks and impressions for the four weeks before and after, and watch for whether total clicks rise, fall, or stay flat — remembering that AI-surface clicks were never separately reported anyway. If you stay in, track your Generative AI impressions per page and look for the pages that earn them; those are your citation winners, and they’re worth updating and strengthening. Don’t flip the switch and forget it. Revisit the decision quarterly, because Google keeps changing both the surfaces and the controls — the UK Competition and Markets Authority timetable requires page-level AI controls by March 3, 2027, which will make this whole decision more granular than today’s all-or-nothing switch.
If you only want to protect some pages: the page-level tools
Because the Search Console control is site-wide, bloggers with mixed content — say, a free blog plus a paid course library, or news posts plus evergreen guides — often want something narrower. Google’s snippet rules are that narrower tool:
- nosnippet on a page hides its text snippet and keeps its content from being used directly in AI Overviews and AI Mode. Use it for pages where the snippet itself is the whole value — a pricing page, a short reference table, a paid resource summary.
- data-nosnippet wraps specific parts of a page — a paragraph, a table, a price list — so just that section stays out of snippets while the rest of the page remains eligible. This is the most underused tool in the bunch, and the most practical for bloggers: protect the one section that AI answers would otherwise lift wholesale, keep everything else working.
- max-snippet limits how long a snippet can be, which is a middle ground between full eligibility and nosnippet.
- X-Robots-Tag applies the same rules to non-HTML files like PDFs, which matters if you sell or share downloadable guides.
These are page-level, they take effect as pages are recrawled (days to weeks depending on crawl frequency), and you can verify them with Search Console’s URL Inspection tool — compare the stored version against a live test, since the two can differ for a while after a change.
What I’d actually do on a small blog
If this were my blog, here’s the order I’d work in. First, verify the setting — don’t assume. Second, pull the Generative AI impressions report and identify my top ten AI-surfaced pages; those pages get refreshed first, because they’re already winning citations. Third, apply data-nosnippet surgically to the sections I don’t want lifted verbatim — usually a proprietary table or a hard-won price comparison — rather than nuking the whole site. Fourth, keep the site-wide switch at include, and revisit it when page-level controls arrive in 2027 or if my numbers tell a different story. And fifth, spend more energy on the email list than on the switch, because the list is the only traffic source no platform update can take away.
That’s not a rule for everyone. A publisher whose entire catalog is reference material that AI answers reproduce in full may reasonably choose exclude, accept the lost AI impressions, and focus on direct and social traffic instead. The point is to choose deliberately, from your own data, with a clear picture of what each control does and doesn’t do.
Google’s October documentation refresh didn’t launch a new feature — it organized existing controls into one place. That consolidation is genuinely useful, because for the first time the seven ways to keep content out of Search sit on a single page, from robots meta tags to the AI control itself. Read that page, check your setting, and make the call. The worst option isn’t opting in or opting out. It’s never looking at the switch at all.
For the companion angle — how to actually get cited in AI answers rather than opting out of them — see our guide on Google AI search source links. And if your traffic has been swinging without an obvious cause, our Search Console performance report delay guide explains why your data sometimes lags the reality by days.
Frequently Asked Questions
Does opting out of Google’s AI features hurt my regular search rankings?
No. Google states that the Search generative AI control is not used as a ranking signal for search results outside the generative AI features. Your regular blue-link rankings are unaffected by the choice, in either direction.
Will opting out stop Google from training AI models on my content?
No. The control governs inclusion in AI Overviews, AI Mode, and generative features in Discover. It does not affect AI training. Google directs publishers to Google-Extended, a separate robots mechanism, for training-related choices.
How long does it take for an opt-out to take effect?
Google says exclusion generally takes effect within one to two days, though caching can delay some content. For page-level snippet rules, allow days to weeks depending on how often Google recrawls the page, and verify with the URL Inspection tool.
Can I opt out only some pages, not my whole site?
Not with the Search Console control — that one is site-wide per property. For page-level control, use nosnippet, data-nosnippet, or max-snippet on individual pages or sections. True page-level AI controls are tied to the UK regulator’s timetable, which requires them by March 3, 2027.
If I opt out, will I lose all Google traffic?
No. Opting out removes you from AI Overviews, AI Mode, and generative Discover features only. Your regular search results, including image, video, and news results, remain. You will, however, give up whatever impressions and traffic those AI surfaces would have sent.
Where exactly is the setting?
In Google Search Console, go to Settings, then look for the Search generative AI section. You’ll see include (the default), exclude, or inherit from a parent property. Check the inherited status before changing anything, especially if you manage multiple properties.