On August 28, 2026, Google confirmed something publishers had been bracing for: AI Overviews now auto-expand into full, AI Mode–style answers on their own, no Show more tap required. The answer box gets bigger. Your ten blue links slide further down. And most sites still haven’t touched the one lever that controls it.
The click-through cost is real. Ahrefs found the top organic result loses roughly 58% of its clicks when an AI Overview sits above it. But the fix most owners reach for—a blanket robots.txt block—is a sledgehammer for a scalpel problem, and it usually doesn’t even do what they think. By the end of this post you’ll have the exact meta tag values, the Search Console path, and a decision matrix for when opting out actually makes sense.
What actually changed
Until this summer, AI Overviews and AI Mode were separated by a wall you could see. AI Overviews were the inline answer box at the top of the results page. AI Mode was the full conversational SERP you got only after tapping into it. The user had to opt in to the deeper experience.
That wall is gone. Google now says AI Overviews “may dynamically expand for topics where our systems determine it’s most useful for people.” In plain terms, the inline box and the conversational answer share one rendering pipeline now, and Google decides when to show the bigger version. Google frames it as a helpfulness win—users, it says, engage more deeply in follow-up exploration. Publishers read the same change differently.
Here’s the implication that matters. A site owner who chose not to configure anything in 2025 has a different exposure today than six months ago, without changing a single line of their own code. In the audits I run on DACH B2B sites, almost none have touched the robots meta tag for AI surfaces. Most owners don’t know the lever exists, so they’ve defaulted into full participation in a surface that grew while they weren’t looking.
The control surface map
There are three distinct mechanisms, and they do not do the same thing. Confusing them is the single most common misconfiguration the team sees.
robots.txt—governs crawl access only. It tells bots which URLs they may fetch. It does not control whether an already-indexed page renders as an AI snippet. Blocking training crawlers likeGPTBotorClaudeBothere changes nothing about your appearance in Google AI Overviews.- Robots meta tag (in the page
<head>)—governs indexing and snippet behavior, including the directives that feed AI Overviews and AI Mode. This is the only mechanism that gives you page-level control today. - Search Console AI visibility controls—a site-level toggle, no code required. It decides whether your property can appear in and help ground Google’s generative AI answers.
The trap is robots.txt. Blocking Google-Extended stops your content from feeding Google’s AI training data, but as one crawler-analysis put it, “Googlebot and Google-Extended are different crawlers with different consequences, and confusing them is the most expensive robots.txt mistake we see.” Blocking the training crawler does not remove already-indexed pages from AI Overviews, and it does not affect your ranking. If your goal is to stay out of the AI answer itself, robots.txt is the wrong file.
The robots meta tag values you actually need
Google recognizes a small, specific set of directives for AI surfaces. Two of them do the real work. Here’s each one with a use case and a copy-paste snippet.
nosnippet — the nuclear option
Removes all text snippets from every Google surface. Per the documentation, this “applies to all forms of search results (at Google: web search, Google Images, Discover, AI Overviews, AI Mode) and will also prevent the content from being used as a direct input for AI Overviews and AI Mode.” It’s genuinely all-or-nothing: you also lose standard featured snippets and Discover previews. Use it only when you want the page to appear as a bare link and nothing more.
<meta name="robots" content="nosnippet">max-snippet — the surgical version
Limits how many characters of your content can be used, and Google confirms it “will also limit how much of the content may be used as a direct input for AI Overviews and AI Mode.” Setting max-snippet:0 starves the AI answer of usable text while staying a distinct, more precise directive than the blunt nosnippet. Setting max-snippet:-1 is the permissive default: unlimited snippet, full participation.
<meta name="robots" content="max-snippet:0">
<meta name="robots" content="max-snippet:-1">data-nosnippet — the section-level scalpel
When you want to keep a page in AI answers but fence off one block—a price, a proprietary definition, a paywalled teaser—wrap it in the data-nosnippet attribute. Only the wrapped span is withheld; the rest of the page stays eligible.
<p>Public intro that can be quoted.
<span data-nosnippet>Members-only detail Google won’t snippet.</span>
</p>A word on noai and noimageai
You’ll see noai and noimageai recommended around the web. Be careful: these are a community convention aimed at AI training data, and Google’s official robots meta tag specification does not list them as directives it honors for AI Overviews or AI Mode. As Originality.AI documents, major AI firms “have generally done so via robots.txt crawler tokens, such as Google-Extended for Google, GPTBot for OpenAI… rather than honoring the noai meta tag specifically.” For controlling how Google renders your content in AI answers, the honored levers are nosnippet and max-snippet. Treat noai as optional belt-and-suspenders, not the control.
Search Console: the new AI visibility panel
If you don’t want to touch code, Google added a toggle in June 2026. It lives at Settings → Search generative AI in Search Console, and it governs whether your content can be used to generate answers across three features: AI Overviews, AI Mode, and AI Overviews inside Discover. Each property can be set to Include (stay eligible), Exclude (opt out), or Inherit from a parent property.
Two limits to know. First, it’s site-level only as of September 2026—there is no per-URL toggle here, so page-level control still means the robots meta tag. Second, it covers Search AI features and nothing else: the Gemini app and the Vertex AI API sit outside it entirely, and your content can still be summarized there after you opt out. This panel is genuinely new, which is why most Search Console tutorials published before July 2026 don’t mention it—and why the launch wasn’t voluntary. Google announced it the same day the UK’s Competition and Markets Authority ordered the company to give publishers real opt-out controls.
Decision matrix: when to opt out, when to stay in
Opting out is not a virtue. For the B2B service sites I work on, I almost never recommend opting out entirely—the citation upside outweighs the CTR risk on non-transactional pages. The exception is content that needs a consultation to be understood properly, where a clipped AI answer actively misleads a reader into thinking they’ve got the full picture. Here’s how I reason through it by page type.
- High-traffic editorial content—stay in AI Overviews and AI Mode. This is where a citation and a brand mention still earns qualified clicks and authority. Blocking it forfeits the one upside AI surfaces offer.
- Gated or paywalled content—opt out, or fence the teaser with
data-nosnippet. A generative summary that gives away what you charge for is a direct revenue leak; keep the free lede quotable and withhold the rest. - E-commerce product pages—usually stay in. AI Overviews rarely satisfy transactional intent on their own, and presence keeps you in the consideration set. Withhold only price and stock detail if you must, via
data-nosnippet. - Service and landing pages that require a conversation—this is the opt-out case. If a two-sentence AI answer makes a prospect think they understand a nuanced offer, it costs you the call.
nosnippetormax-snippet:0earns its place here.
Whichever way you decide, decide with data, not vibes. If you’re opting out to protect traffic, you need to know first whether the AI answers are even citing you and what they say. A tracker like Cited monitors how ChatGPT, Claude, Perplexity, Gemini, and Google AI Overviews describe your brand and competitors over time—which turns “should we opt out?” from a guess into a measurement. We built it because the audits kept hitting the same wall: owners couldn’t see what the AI surfaces were saying about them.
WordPress implementation walkthrough
Three ways to get the tag onto the page. Pick one—don’t stack them, or you’ll fight yourself over which directive wins.
Yoast SEO
Open the post, scroll to the Yoast box, expand the Advanced tab. Set the meta robots advanced field to No Snippet (or add max-snippet:0 where Yoast allows a custom value). This applies per post, which is exactly the page-level control the Search Console toggle can’t give you.
Rank Math
In the post editor, open the Rank Math panel, go to Advanced, and tick the robots meta option you need (No Snippet), or enter a custom directive in the meta robots field. Same per-post granularity as Yoast.
Manual injection via functions.php
If you’re not running an SEO plugin, or you want a rule that applies to a whole post type, hook wp_head in your theme (ideally a child theme) or a header snippet plugin:
add_action(‘wp_head’, function () {
if (is_singular(‘post’)) {
echo ‘<meta name="robots" content="max-snippet:0">‘ . “\n”;
}
});Verification: confirming Google respects your settings
Don’t assume—check. Use the URL Inspection tool in Search Console, run a live test on the page, and read the Page indexing section: it shows the crawled HTML and the serving directives Google actually detected. If your nosnippet or max-snippet tag is present, it’ll register there.
One common confusion worth killing: Google’s Test robots.txt tool checks crawl rules only—it does not test meta tags, because those live in the page, not the file. Two different mechanisms, two different tools. On timing, expect Google to process robots meta tag changes within 1–14 days, depending on how often it crawls the URL. High-frequency pages update fast; a rarely-crawled service page can sit at the far end of that range.
DACH angle: why German publishers are especially exposed right now
There’s a second reason to care about opt-out beyond traffic, and it landed the same week as the dynamic-expansion news. Starting August 30, 2026, Google’s site reputation abuse manual actions no longer apply to users inside the EEA—the change came in response to an EU Digital Markets Act probe. Instead of a ranking penalty, Google now says “the affected section of the site may be separated in our systems so that, over time, it ranks independently from the rest of the site.”
Read that carefully if you’re a German Mittelstand site. The risk shifts from a visible penalty to a quiet algorithmic split. A separated section—think thin AI-generated content, or a third-party-hosted microsite bolted onto your domain—can lose the authority of your main domain and still surface in AI Overviews on its own. That’s a reputation exposure, not just a traffic one. Tagging that content with nosnippet is proactive hygiene: you keep low-quality material out of the AI answer before it gets separated and starts speaking for your brand without your authority behind it.
Frequently asked questions
Does opting out of AI Overviews affect my regular Google ranking?
No. Google confirmed the opt-out setting is not used as a ranking signal for regular Search. Sites that opt out keep appearing normally in blue-link results and the Discover feed—only AI Overviews, AI Mode, and AI Overviews in Discover are affected.
Can I opt out of AI Mode but keep AI Overviews?
Not with a single switch. The Search Console toggle treats all three AI surfaces as one group, and Google’s honored meta directives (nosnippet, max-snippet) apply to AI Overviews and AI Mode together. There is no clean “AI Mode only” opt-out today.
Does robots.txt blocking stop Google from showing my content in AI answers?
No. Blocking Google-Extended stops AI training use, not AI Overviews rendering. And disallowing Googlebot in robots.txt actually backfires—Google can’t crawl the page to read your nosnippet tag, so the opt-out you intended never registers.
How long does an opt-out take to take effect?
Meta tag changes typically process within 1–14 days, depending on crawl frequency; Search Console toggle changes apply faster. If you’re on WordPress with full-page caching, purge the cache first so Googlebot sees the new tag at all.
Do these controls work in Perplexity and Bing Copilot too?
No. These are Google-only levers. Neither the Search Console toggle nor Google’s meta directives reach Perplexity, Bing Copilot, or even Google’s own Gemini app. Those surfaces need their own crawler-level controls, configured separately.
What to do this week
- Open Search Console → Settings → Search generative AI and note whether your property is set to Include, Exclude, or Inherit. Most sites are silently on Include.
- List your page types against the decision matrix above. For most B2B and editorial sites, the answer is stay in—but flag any consultation-dependent or gated pages for opt-out.
- Add
max-snippet:0(surgical) ornosnippet(nuclear) to just those flagged pages via your SEO plugin, then purge your cache. - Verify with URL Inspection that Google detected the directive, and re-check in a week.
If you want a second set of eyes on where your site is exposed across AI surfaces—and a fixed-price map of what to change—that’s exactly what our AI Visibility Audit covers.