How to Opt Out of Google AI Overviews: Your Options in 2026

There is no simple "off switch" for Google AI Overviews — and that is the first thing to get straight. Google does not offer a per-page toggle that quietly removes you from AI-generated answers while leaving everything else untouched. What it does offer is a set of controls with real trade-offs: a property-level switch in Search Console that excludes your entire site from AI Overviews, AI Mode, and generative features in Discover; snippet controls like nosnippet and max-snippet that stop Google from using your text as AI input but also shrink or remove your normal search snippets; and data-nosnippet for hiding a single passage. Below are the honest options, in the order most site owners should consider them.

Why Google never built a simple toggle

AI Overviews are not a separate product with a separate index. Google has confirmed that AI Overviews and AI Mode run on the same index, ranking systems, and quality signals as regular search. When you see an AI-generated answer, it was assembled from pages Google already crawled, indexed, and ranked — the model reads those pages (Google calls this grounding, a form of retrieval-augmented generation) and writes an answer with links back to the sources.

That architecture is exactly why a clean per-page "keep me in results but never in the AI answer" switch was hard to build. Back in February 2026, Google's Sulina Connal acknowledged in London that letting publishers skip AI Overviews was a major engineering challenge. Google did eventually ship a site-level answer — the Search Console control covered below — but there is still no page-level switch that affects only AI answers and nothing else. Every page-level tool Google offers works through the same snippet system that powers your ordinary search listings, which means the trade-offs below are unavoidable.

Option 1: The Search Console "Search generative AI" control (the closest thing to a real opt-out)

In 2026 Google rolled out a dedicated control in Search Console, documented in its official help pages, that lets a verified site owner manage participation in Search's generative AI features. Google says the control became available to all websites worldwide on August 31, 2026.

Here is how to use it:

1. Open Google Search Console and select the property you want to manage.
2. Go to Settings > Search generative AI.
3. Choose "Exclude my site's links and content from Search generative AI features."

The three choices are Include (the default — your links and content can appear in generative AI features and help ground their answers), Exclude (your content is prevented from appearing as links or grounding material in the covered features, and you receive no traffic or impressions from them), and Inherit control from parent (a child property follows its parent property's setting unless you override it).

What this controls, in practice:

• Your site's links and content are removed from AI Overviews, AI Mode, and generative AI features in Google Discover. Google notes the list of covered features can change over time.
• Exclusion generally takes a few days to take effect — most content disappears within one to two days, though cached items can take longer.
• It is not used as a ranking or inclusion signal anywhere else in Search. Your ordinary blue-link rankings are unaffected.
• It does not stop Google from using your content to train AI models. That is a separate decision (see the Google-Extended section below).

This is the right choice for publishers whose business model depends on direct visits — news sites, subscription content, specialist guides — and who would rather lose AI-feature impressions entirely than supply answers that never send a click. One honest caveat from Google's documentation: opting out does not make the AI answer disappear. It gets built from other sites instead, and your competitors' pages may fill the space you vacated. Measure what the features were sending you first, using the Generative AI performance report in Search Console, before you pull the lever.

Option 2: nosnippet — the hard stop for a single page

The nosnippet robots meta tag is the strongest page-level control Google offers. When Google sees it, the page's content is prevented from being used as a direct input for AI Overviews and AI Mode.

<meta name="robots" content="nosnippet">

The catch: it also prevents text snippets and video previews for that page in ordinary search results. Your page keeps its title, its URL, and its ranking — and a static image thumbnail can still appear where Google judges it useful — but the descriptive text under the link disappears. An SEO consultant's 2024 case study demonstrated the trade-off precisely: the protected pages were removed from AI Overviews, and their normal search listings lost their descriptions at the same time.

Use nosnippet when a page should never be quoted, period: legal pages, pages summarizing paywalled or members-only material, internal documentation that accidentally became public. To apply it:

• Add the meta tag to the page's <head> section. In WordPress, most SEO plugins (including Rank Math) let you set this per page or post without touching code.
• For non-HTML files such as PDFs, use the HTTP header equivalent: X-Robots-Tag: nosnippet.
• The page must be crawlable. Google reads meta tags only on pages it actually fetches, so a URL blocked in robots.txt will not have its nosnippet instruction seen.
• Allow time for a recrawl. Google applies the rule after it re-fetches the page, which can take days to weeks.

If you manage robots.txt rules for your site, our free robots.txt generator helps you build the file correctly, and the robots.txt tester checks that your directives do what you think they do before they go live.

Option 3: max-snippet — the volume knob

If nosnippet is an on/off switch, max-snippet is a volume knob. It caps how many characters of your page Google may use in a text snippet — and, by extension, how much of your content may be fed into AI Overviews and AI Mode as direct input.

<meta name="robots" content="max-snippet:120">

Two special values matter. max-snippet:0 means no text snippet at all — the equivalent of nosnippet for text. max-snippet:-1 means no limit, which is what most pages want. If a page carries conflicting rules, the more restrictive one wins: a page with both max-snippet:50 and nosnippet is treated as nosnippet.

This option suits pages where you want to stay visible in search but limit how much of your writing Google can lift into an answer — for example, a 120-character cap that keeps the listing informative while giving the AI model too little to build a full answer from. Be realistic about the side effect: the same cap shortens your ordinary snippets, and shorter snippets typically earn fewer clicks. And note that it does not limit image or video previews, and it does not override permissions you granted elsewhere, such as content you licensed to Google directly or supplied through structured data.

Option 4: data-nosnippet — surgical control for one passage

Sometimes the problem is not the whole page but one section of it: a pricing table that changes weekly, an embargoed detail, a paragraph with licensed text. For that, Google supports the data-nosnippet HTML attribute on span, div, and section elements. Everything inside the marked element is excluded from snippets and from AI input, while the rest of the page stays fully quotable.

<p>Our annual plan is priced per seat.</p>
<div data-nosnippet>
  <p>Current promotional pricing: $49 per seat through Q3.</p>
</div>

Two details worth knowing: it behaves as a boolean attribute, so any value you assign is ignored — its presence is what counts. And it must be present in the HTML Googlebot receives when it fetches the page; adding or removing it with JavaScript after the page loads is unreliable because the crawler may not see the change. Structured data nested inside a data-nosnippet element is generally still read, so you can suppress a passage from snippets without hiding its markup from rich-result processing.

Option 5: noindex — the nuclear option

noindex removes the page from Google Search entirely. It is not really an AI Overviews opt-out; it is an opt-out of being found at all. Only use it when the page should not appear in Google for anyone — which, for most publishers reading this article, defeats the purpose. If your goal is to stay in search but stay out of AI answers, the options above are the ones built for that job.

What does NOT work: the Google-Extended myth

The single most repeated piece of bad advice on this topic goes like this: add User-agent: Google-Extended with Disallow: / to your robots.txt and your content will stop appearing in AI Overviews. It will not.

Google-Extended is a robots.txt product token, not a crawler — there is no separate user-agent string making HTTP requests under that name; Google's existing crawlers do the fetching and the token governs one specific use of what they collected. According to Google's crawler documentation, it lets publishers "manage whether content Google crawls from their sites may be used for training future generations of Gemini models" and for grounding in Gemini Apps and the Vertex AI API. The same documentation states plainly that Google-Extended "does not impact a site's inclusion in Google Search nor is it used as a ranking signal in Google Search."

AI Overviews and AI Mode are surfaces inside Google Search, built on the regular Search index and crawled by regular Googlebot. Google confirmed this distinction back in October 2023, when the feature was still called SGE: blocking Google-Extended did not apply then, and it does not apply now. Add the disallow and you have opted out of Gemini model training. You remain fully eligible to be summarized in an AI Overview the next morning.

That does not make Google-Extended useless — it is the correct, no-SEO-cost tool for the AI-training decision, and many publishers reasonably choose to block it. For more on how it differs from blocking other AI crawlers, see our guides on the complete list of AI crawlers in 2026 and whether blocking GPTBot hurts SEO. Just do not mistake it for an AI Overviews opt-out. Similarly, do not disallow Googlebot itself in robots.txt to stop AI answers — that deindexes your pages from all of Google Search, which is almost never what anyone wants.

Choosing the right option for your situation

• Whole site out of AI answers, rankings untouched: Search Console's "Search generative AI" control, set to Exclude. The cleanest separation Google offers.
• One specific page should never be quoted: nosnippet on that page. Accept the loss of its ordinary snippet.
• Stay visible, limit exposure: max-snippet with a character count that fits your tolerance.
• Hide a single passage: data-nosnippet around that section.
• Stop Gemini training, keep everything else: disallow Google-Extended in robots.txt. No effect on AI Overviews either way.
• Do not want Google at all: noindex (page) or blocking Googlebot (site) — and be sure that is really the decision.

Implement and verify: a short checklist

1. Decide the scope first. Site-wide exclusion and page-level snippet controls solve different problems; mixing them up is how sites accidentally kill their own snippets.
2. Implement one change at a time. Add the meta tag, the attribute, or flip the Search Console toggle — not all three at once — so you can attribute any traffic change.
3. Confirm Google can see the change. Use URL Inspection in Search Console to verify the page is crawled and the directive is in the fetched HTML. Remember that snippet directives only register after a recrawl.
4. Watch the Generative AI performance report. Impressions from AI Overviews and AI Mode should decline as exclusion propagates, typically within days.
5. Revisit the decision periodically. Snippet controls reduce ordinary click-through rates, and the Search Console exclusion hands AI-feature impressions to competitors. What is right today may not be right after your next content audit.

Google documents the property-level control in its official Search generative AI control help page, and the snippet directives in its guide to meta tags Google supports — both worth bookmarking, since Google says it will update the covered feature list over time.

Frequently asked questions

Will opting out of AI Overviews hurt my Google rankings?

No — as long as you use the right control. Google states that the Search Console generative AI control is not used as a ranking or inclusion signal anywhere else in Search, so excluding your site leaves your ordinary rankings untouched. Snippet controls like nosnippet do not change rankings either, but they do remove or shorten your search snippets, which typically reduces click-through rate.

Does blocking Google-Extended stop my content appearing in AI Overviews?

No. Google-Extended only governs whether your crawled content may be used to train future Gemini models and to ground answers in Gemini Apps and the Vertex AI API. AI Overviews and AI Mode are Search features built on the regular Search index, and Google has confirmed since 2023 that the token does not apply to them.

How long does the Search Console exclusion take to work?

Google says exclusion generally takes a few days. Most content disappears from the covered features within one to two days, but cached items can take longer.

Can I opt out of AI Overviews but keep my featured snippets?

Not cleanly at page level. Any snippet restriction strong enough to keep you out of AI answers also weakens your ordinary snippets, because both draw from the same system. The Search Console generative AI control is the only option that separates the two: it excludes you from AI features while leaving ordinary search — snippets included — exactly as it was.

Does the opt-out stop Google using my content for AI training?

No. The Search Console control governs live use inside Search's generative AI features only. Restricting model-training uses is the separate Google-Extended decision, made in your robots.txt.

If I opt out, does the AI answer disappear for that query?

No. The answer is simply assembled from other sites' content. Google is explicit about this in its documentation — which is why it is worth checking the Generative AI performance report first, so you know what visibility you are handing to competitors.