Google AI content opt-out: should you block AI Overviews?

Search Console now has a setting that answers, literally, the question GEO has been asking philosophically for two years: do you want AI to cite you? Google announced the control as a way for "website owners to decide if they want their site to appear in and help ground responses in our generative AI Search features (like AI Overviews, AI Mode or AI Overviews in Discover)." It's a real toggle, it's live, and for most SaaS and content-automation blogs the right setting is the one Google already picked for you: leave it on Include.

This post covers what the Google AI content opt-out actually does, what it doesn't touch, and the narrow set of cases where flipping it to Exclude is the correct call.

What Google's AI content opt-out actually does (and where to find it in Search Console)

The control is a binary switch, Include or Exclude, that decides whether Google's generative Search features are allowed to use and cite your content. It doesn't touch anything else about how Google treats your site.

The toggle lives under Search Console > Settings > Search generative AI

Open Search Console for the property in question, click Settings in the left-hand menu, and look for a section called Search generative AI. That's the whole surface: no separate dashboard, no new report to configure first. Include is the default state, which is worth noting on its own, since a default of "in" tells you which choice Google expects most sites to make.

The rollout was staged. Google began with a subset of UK website owners, "allowing for thorough testing before rolling them out to website owners globally." The UK piece of that wasn't optional on Google's end: the UK Competition and Markets Authority ordered Google to give publishers AI opt-out rights inside a nine-month implementation window, as part of a binding conduct requirement. The toggle became enforceable in the UK on June 17, 2026, and the same setting started appearing on Search Console accounts outside the UK starting in July 2026, according to Search Engine Journal's reporting.

One detail matters more than it looks: the control is property-level, not page-level. You can exclude a domain from AI features; you can't yet exclude one paywalled report while leaving your marketing blog included. Google is under a requirement to ship page-level granularity by March 2027, so this is a temporary limitation, but it's the one that matters most right now if you were hoping to be surgical about it.

What it does not touch: core rankings, indexing, Discover, Google-Extended, Gemini training

This is the part that decides whether the toggle is even relevant to your SEO work. Google states it plainly:

"This control will not be used as a ranking signal for search results outside of these generative AI Search features."

Read that as written. Your position in classic blue-link results doesn't move. Indexing doesn't change. Discover keeps showing your content outside of Discover's own AI summary layer. None of the fundamentals covered in answer engine optimization, direct answers, verifiable facts, clean structure, stop mattering for regular Search just because you flipped this switch.

The toggle also doesn't reach three things people assume it does. It doesn't touch Google-Extended, the separate crawler directive that governs whether your content can train Gemini; that's a robots.txt decision you make independently, the same way robots.txt already splits training crawlers from search crawlers for OpenAI and Anthropic's bots. It doesn't touch Merchant Center or Google Ads participation. And it doesn't override any existing robots.txt rule you've already set. Search Engine Journal confirms all three: the setting is scoped narrowly to AI Overviews, AI Mode, and Discover's AI features, full stop.

There's one side effect Google hasn't formally addressed. Top Stories carousels increasingly render inside AI Overviews rather than the classic carousel position: nearly 1 in 6 U.S. trending news queries, about 15.5%, now place Top Stories inside an Overview, and the UK rate runs higher at 17.46%, per the same Search Engine Journal analysis. If your Top Stories placements are already living inside that surface, opting out of AI features may pull those placements with them. Google hasn't confirmed or denied it. If you run a news-adjacent property, that's worth testing on a low-stakes property before you flip the switch on your main one.

The AI Overviews SEO tradeoff: what opting out protects vs. what it forfeits

Opting out protects exactly one thing: it removes your content from Google's generative Search features entirely. It doesn't protect your rankings, because those were never at risk from staying in. That asymmetry is the whole tradeoff, and it's worth stating in Google's own words a second time, because it's the fact that makes this decision easy for most sites:

"Sites that opt out will not receive traffic or impressions from our generative AI features."

That's a full exclusion, not a dial you can turn down partway. You either remain eligible to be one of the sources an AI Overview or an AI Mode answer cites, or you're invisible on both surfaces, on every query, for the whole property. There's no middle setting that reduces exposure while keeping some citation upside.

What you forfeit by choosing Exclude is real and growing. Google's own numbers put AI Overviews at more than 2.5 billion monthly active users and AI Mode at more than 1 billion, which is not a niche experiment at this point, it's most of Google Search's active user base touching a generative surface in some form. AI Overviews and AI Mode also cite largely different URLs for the same query, so being eligible for one doesn't automatically cover the other; our breakdown of how AI Mode and AI Overviews differ walks through why query fan-out pulls from a wider, different source set. Opting out takes you out of both pools at once.

The counter-argument, that AI Overviews cannibalize clicks a blue link would have earned, is real but incomplete. It describes the downside of staying in without weighing the upside: a citation is still a visible placement at the top of the page, still carries your brand and your link, and still beats not being on the page at all. Rahul Jain, CEO of Noble, put it directly in the same Search Engine Journal piece: "Opting out of Google's AI Overviews will hurt most publishers more than it helps." The people telling you to flip this switch by default are mostly reacting to AI Overviews as a concept, not to what this specific control actually trades away.

None of this means the control is meaningless. Paul Bannister, Chief Strategy Officer at Raptive, gave the sharper read on what it actually is: "Giving publishers a front-end toggle for AI Overviews or AI Mode is not real control; it is Google offering publishers a light switch while keeping the power plant running." That's a fair description of the limits here. You can turn off citation. You can't turn off Google's underlying use of the open web to build these systems, and you can't yet control it page by page. What you're deciding is narrower than "how much AI touches my content." You're deciding whether you're eligible to be the source it names.

Why a content-automation and GEO-focused blog should almost never flip this to Exclude

If your blog exists to get found, and increasingly to get cited, opting out works against the reason the blog exists. This is the most direct case for leaving the default alone.

A SaaS or dev-tool blog built for organic growth is playing exactly the game AI Overviews and AI Mode reward: answer the question clearly, back it with a verifiable source, structure it so a model can lift a clean passage. That's the same discipline behind showing up in Google AI Overviews in the first place, and it's wasted the moment you exclude yourself from the surface it was built for. You'd be doing the work of AEO and disabling the one Google surface where that work pays off directly.

The backdrop that produced this whole feature also argues against reaching for it reflexively. The CMA's order exists because publishers like People Inc. reported roughly 800 million fewer Google-referred visits between Q1 2024 and Q1 2026, a traffic decline large enough to trigger a regulatory intervention. That's a real, publisher-scale problem, and it's the argument for the control existing at all. It is not, on its own, an argument for any given site to use it. A publisher losing hundreds of millions of visits a year and a five-person SaaS blog trying to build initial topical authority are not making the same trade, even though the checkbox in front of them is identical.

There's also a governance angle worth separating out. Choosing not to appear in AI Overviews is a visibility decision, not a quality or safety one; it doesn't say anything about whether your content is trustworthy, which is a different question covered by does Google penalize AI content and the actual editorial standard that governs rankings. Confusing the two is how a team ends up flipping a switch meant for licensing disputes to solve a problem, AI-authorship anxiety, that this toggle was never built to address.

If you already run citation tracking, you have the clearest local argument of all: check whether AI-referred traffic and AI mentions are showing up before you shut the door on the surface producing them. Our guide to AI citation tracking covers the GA4 setup and the blind spots in measuring that traffic. If the number is climbing, or even nonzero, opting out throws away a channel you can already see working.

When opting out actually makes sense: paywalled, licensed, or liability-sensitive content

There are legitimate reasons to flip this to Exclude, and they share a pattern: they're economic or legal, not competitive.

• Content you license or sell separately. If a research report, a premium newsletter, or a data product is the actual product, a free AI-generated summary competing with the paid version is a real business risk, not a theoretical one. This is the exact scenario the CMA order was written around.
• Paywalled or subscription reporting. A publisher whose revenue depends on the click, not the citation, has a different calculation than a SaaS blog whose revenue depends on being found in the first place. If an AI summary satisfies the reader before they hit your paywall, you've lost the sale the click was supposed to produce.
• Pages carrying real legal or compliance exposure. Content where being quoted out of context creates liability, regulated financial guidance, certain healthcare claims, anything reviewed by legal for exact phrasing, is a reasonable candidate, especially since AI-generated summaries strip the surrounding disclaimers and context that made the original page compliant.
• Sites where the traffic math has already turned negative. If you can show, with your own analytics, that AI Overview appearances are net-reducing clicks on a specific content type without a compensating citation benefit, you have evidence, not a hunch. That's a higher bar than "AI Overviews might be doing this," and it's the bar worth clearing before you touch the property-wide switch.

Notice what's absent from that list: "we're a SaaS blog and don't want to help train Google's AI," "we're worried about AI-written content getting penalized," and "everyone else in our space is turning it off." None of those are reasons this control was built for, and none of them survive contact with what Google states the control actually does.

A short checklist before you touch the toggle

Before you change the setting on any property, work through this in order:

1. Confirm what you're actually deciding. This toggle controls AI Overviews, AI Mode, and Discover's AI features only. It is not your Google-Extended training setting, not your robots.txt, and not a ranking lever.
2. Check whether the content is genuinely licensed, paywalled, or liability-sensitive. If none of those apply, the default answer is to leave Include as-is.
3. Look at your own AI citation data first. If you're not already tracking AI referral traffic, set it up before deciding you don't want it.
4. Remember it's property-wide today. You can't protect one report while keeping the rest of the blog included, so weigh the decision against your whole domain, not one page.
5. Revisit it once page-level controls ship. The March 2027 deadline changes the calculus for teams with a genuine mixed-content case: most of the property visible, a narrow slice excluded.
6. Don't confuse this with an AI-quality decision. If the actual concern is whether AI-assisted content should rank at all, that's a separate, already-answered question, not a reason to flip this switch.

This toggle is the closest Google has come to a literal answer key for a question the GEO and AEO space has been arguing about in the abstract: does being cited by AI actually matter to you? For a blog built to compound organic and AI-search visibility, the honest answer is almost always yes, which means the setting stays on Include, and the more useful work is making sure your content earns the citation once it's eligible for one.

Deciding whether to be cited by AI shouldn't require a Search Console setting and a spreadsheet. Try Lyra to ship posts already structured, sourced, and fact-checked for the surfaces that reward exactly that, then talk to the founder if you want to walk through the setup.

Try Lyra → · Talk to the founder