Should You Opt Out of Google's AI Overviews?

For most of the time AI Overviews have existed, opting out of them meant accepting a real cost: the only tool for the job was nosnippet, and turning it on also stripped the normal text snippet from your regular search results. You could not remove yourself from the AI answer without also making your ordinary listing worse. That changed in 2026. Google now has a dedicated control that takes you out of AI Overviews and AI Mode without touching your ranking or your regular snippet, and as of the end of August 2026 it is available to every site worldwide.

So the mechanics are finally clean. The decision is not. Being able to opt out is not a reason to, and for most sites it is still the wrong move. This post covers both levers, exactly what each one costs you, and the narrow set of cases where opting out actually makes sense.

What you are opting out of, and what you are not

The dedicated control covers three things at once: AI Overviews (the generated answer at the top of a search results page), AI Mode (Google's full conversational search experience), and the generative AI features in Google Discover. Opt out and your content stops appearing in all three, including as a linked citation inside them.

Those three are not the same size. AI Overviews sit on ordinary results pages and are shown to a large share of searchers whether they asked for them or not, so that is where most of the visibility, and most of the lost-click anxiety, actually lives. AI Mode is a separate surface a user chooses to enter, smaller today though growing. Discover's AI features are smaller still for most sites, and larger for publishers whose traffic already leans on Discover. The control bundles all three, so opting out to deal with AI Overviews also removes you from the other two, with no way to keep one and drop another.

It does not touch anything else, and this is the part worth being precise about, because the fear that opting out quietly damages your normal search presence is the main thing that stops people who genuinely should do it. Google's own description of the control is explicit: it "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 also does not affect AI model training, and it does not override separate choices you have made in Merchant Center or Google Ads.

So opting out of AI Overviews leaves untouched: your ordinary blue-link ranking, your regular result snippet, your eligibility for featured snippets and every other rich result, and whether your pages were used to train Gemini (that is governed by Google-Extended, which is a training signal only and has never affected Search, a distinction we cover in block AI crawlers).

Lever 1: the Search Console control

This is the clean one, and for most people who have decided to opt out, it is the only tool they need.

It lives in Search Console under Settings, then Search generative AI. There are three values:

• Include is the default. Your content can appear in AI Overviews, AI Mode, and Discover's generative AI features, both as ground for the answer and as a linked source.
• Exclude prevents your content from being visible to users in those features, including being linked to inside them.
• Inherit from parent applies the setting of the parent property. This matters if you use a domain property: set Exclude at the domain level and every subdomain and path under it inherits the exclusion unless you override it lower down.

Timing. A change is not instant. Google says it "generally takes a few days", with content excluded within one to two days of the change taking effect, and some pages taking longer because of caching. Plan for about a week before the effect is complete.

Reversibility. You can switch back to Include whenever you want, but the recovery runs on Google's schedule, not yours. Your content becomes eligible again after the setting flips, and then actually reappears as Google recrawls and reprocesses the relevant pages, which for a modest site can take weeks. A two-month opt-out is not a two-month absence, it is two months plus the time it takes to climb back in.

Lever 2: the snippet controls

Before the dedicated control existed, this was the only route, and it still has a place. The robots meta tags limit how much of your page's text Google can show, and because AI features are built partly from that same text, restricting it restricts what those features can quote.

• nosnippet (a robots meta tag or X-Robots-Tag header) tells Google to show no text snippet from the page at all.
• max-snippet:[number] caps the snippet at a set number of characters; max-snippet:0 is effectively the same as nosnippet.
• data-nosnippet is an HTML attribute you put on a specific element (<span>, <div>, <section>) to exclude just that passage while the rest of the page stays quotable.

The cost is the thing to understand. nosnippet and max-snippet:0 do not carve AI features out on their own, they remove your regular search result snippet too. Your listing becomes a bare title and URL with no descriptive text under it, which measurably hurts click-through from ordinary search. Google confirms that using these tags to opt out of generative AI features does not affect indexing or ranking, but a snippet-less result still performs worse in practice because users have less to go on.

Where the snippet controls still earn their place:

• data-nosnippet for surgical protection. You want to stay in AI Overviews generally, but there is a specific block of text (a proprietary definition, a piece of original data, a paragraph you license) you do not want quoted verbatim. Wrap that element in data-nosnippet and leave everything else eligible. The dedicated control is all-or-nothing per property and cannot do this.
• When you do not control the Search Console property. An agency working on a client's content, or a contributor on a large site, may be able to edit page markup but not the property settings. The meta tags are editable at the page level by anyone who can deploy the page.

The two levers, side by side

For a clean, whole-site opt-out, the Search Console control is the right tool and the snippet tags are the wrong one. The snippet tags are for the narrower jobs the control cannot do.

Should you actually do it?

For the large majority of businesses, no. The reasoning is the same one that applies to blocking AI crawlers, and it comes down to a single point: opting out does not send the click to you instead. It sends it to whoever is still in the answer.

When someone asks a question your page could answer and you have opted out, Google does not show a gap where you would have been. It builds the AI Overview from the sources that stayed in, which for a competitive commercial topic means your competitors. The searcher gets a confident answer that does not mention you, and if they do click through, they click through to someone else. You have not recovered the visit, you have removed yourself as a candidate for it.

Opting out also does nothing to make Google's AI quiet about your topic or your brand. The feature keeps answering. It just answers using everyone except you, the same dynamic that leaves an AI guessing about your business once your own pages are out of what it can read.

The case where opting out is defensible

There is one, and it is narrow: your business is the click, and your content is the kind an AI Overview can fully satisfy in place.

This describes some publishers. If your revenue is display advertising or affiliate links on the page, and your highest-traffic content is the sort of factual, self-contained material an AI Overview reproduces completely (a conversion, a definition, a "what year did X happen", a recipe's core steps), then the AI Overview is a direct substitute for the visit rather than a route to it. For that specific combination, being cited without being visited is close to pure loss, and opting out at least removes your content from powering a feature that competes with you.

Even here, the honest move is to measure first, not to opt out on instinct. And even here it is a genuine trade: some readers do click through from an AI Overview citation, and you give those up too.

There is also a values argument, the same one people make for blocking AI training crawlers: any single site opting out changes almost nothing, but a large enough number acting together shifts the picture, and norms have to start somewhere. That is a legitimate reason to opt out even when the individual effect is small. It is a decision about principle rather than performance, and it should be made as one, with the visibility cost understood rather than assumed away.

A quick way to see which side of the line you are on. A recipe or reference site funded by on-page ads, whose top pages are things an AI Overview reproduces in full, loses little by opting out, because a searcher who got the answer was never going to visit anyway, and the page's presence is partly training a feature that competes with it. A SaaS company, a local service business, a shop, or a B2B site is the opposite: the pages appearing in AI features are ones where the buyer still has to come to you to convert, so a citation is a route in, and removing it just moves the buyer's attention to whoever stayed. Most businesses are the second case, which is why "don't" is the default answer.

The reasoning that does not hold up

"I will opt out to force people to click." They will not click. They will read the answer built from other sources. The click you are imagining does not exist as an alternative to the AI Overview, it exists as an alternative to a competitor's citation.

"Being summarised is bad, so being absent is better." Being summarised with your brand named, your positioning stated, and a link to you is worth more than being absent while the summary gets written about your category without you in it. The response to a weak AI Overview appearance is usually to make your page more quotable and better grounded so the answer is built from your facts, not to leave. Our guide to appearing in AI Overviews covers what actually moves that.

"I will opt out now and back in later if it goes badly." You can, but the recrawl lag means you are committing to a longer absence than the calendar suggests, and you will have handed competitors a clean run at the answer in the meantime.

How to decide, with actual numbers

The decision turns on your site's specifics, so pull them before you choose:

Read the generative AI performance report. Search Console has a generative AI performance report, separate from the main performance report. It shows impressions, not clicks, which means it can tell you how much visibility you would give up but not how much traffic. Start with the Pages view: which of your URLs are appearing, and are they your commercial pages or your old blog posts?

Cross-check with your analytics referrals. Traffic that does arrive from Google's AI surfaces shows up in your analytics as referral traffic. It will not reconcile cleanly with the impressions figure, but it is a real number about real visits, and it is the other half of the picture the report cannot give you.

Look at what appears, not just how much. If the pages showing up in AI features are ones where the reader still needs to visit you (a product page, a service page, a tool), the feature is working as a route in and opting out costs you. If they are pages the answer fully replaces, the case is different.

Check your category. Run a few real buyer questions for your industry in AI Mode. If competitors are cited and the topic is clearly one AI Overviews engage with, that is the visibility you would be stepping out of.

Common mistakes

Assuming the opt-out hurts normal search. It does not. Google states plainly that the control is not a ranking or inclusion signal for the rest of Search. The fear that it quietly demotes you is the most common reason people who should opt out do not.

Using nosnippet when you mean the toggle. nosnippet also kills your regular search snippet. If a whole-property opt-out is the goal, the Search Console control does it without that side effect.

Setting Exclude on a domain property without checking inheritance. Every child property inherits it. If you meant to opt out one subdomain, set it there, not at the domain level.

Opting out to protect traffic, then watching traffic fall anyway. The click does not transfer to you. This is the single most common misread of the whole decision.

Treating it as instant and reversible on your timetable. Both directions run on Google's recrawl cycle. Budget about a week out, and weeks back.

Confusing this with an AI training opt-out. They are separate controls. This one is about appearing in Search's AI features; Google-Extended in robots.txt is about Gemini training and does not affect Search at all.

If you have decided to opt out

Whole property, the clean way: in Search Console, open Settings, then Search generative AI, and set the control to Exclude. Confirm which property you are editing, and if it is a domain property, decide whether every subdomain and path should be excluded too. Allow about a week for it to take full effect, then spot-check by running queries your pages used to appear for.

A specific passage only: wrap the element in data-nosnippet, for example <div data-nosnippet>…</div>, and leave the rest of the page eligible.

A whole page, when you cannot access the property settings: add <meta name="robots" content="nosnippet"> to that page's head, and accept that its regular search snippet goes with it.

Then keep watching the generative AI report. If your traffic and conversions hold and the visibility you gave up turns out not to have been sending you anything, the decision was right. If referrals drop, switching back to Include is one setting away, minus the recrawl wait.

Before you decide, see which of your pages Google's AI features actually use and how well those pages are grounded in your own structured data. Run a free AI readiness check at aischemagen.com to see what an AI reads on your site, and whether the answer it builds is coming from your facts or someone else's.