Should you block Google AI Overviews from your site?

What did Google just change about its AI and snippet controls?

On October 21, 2026, Google revised its help page on controlling what you share with Google Search. Every AI and snippet control now sits in one guide. Nothing new launched. The update pulls in options that already existed: the site-wide Search generative AI setting in Search Console, plus the page-level robots meta tag, the X-Robots-Tag HTTP header and the data-nosnippet attribute. Google's changelog calls it a refresh of the available choices, not a new feature. Two new sections walk site owners through the generative AI control and the robots-based preview rules. If you've spent the past two years piecing this together from scattered developer docs, forum threads and conflicting blog posts, the single page is a real help. It also signals that Google expects publishers to make these choices on purpose.

Why should a clinic, a law firm or an online store care? These switches decide whether your pages can be quoted and linked inside AI Overviews and AI Mode. Those answers now sit above the classic blue links for a large share of informational searches, and for many queries they're the first thing a prospect reads. If you've put work into content that answers real customer questions, that's exactly the content Google's AI features want to cite. One wrong setting can quietly pull you out of those answers while your rankings look normal in every monthly report. It might be a nosnippet tag left over from a site migration, a developer's well-meant opt-out, or a plugin default nobody checked. You keep your position and lose the visibility.

The headline control is the Search generative AI setting. It's under Settings in Search Console and is now available to every verified property. Turning it off removes a site's content and links from Google's covered AI features, including AI Overviews, AI Mode and generative features in Discover. Google says the choice isn't a ranking or inclusion signal for the rest of Search, so your ordinary listings should stay where they are. The setting applies to a whole property. A narrower property can inherit a parent property's choice unless an owner overrides it, which matters if your agency set up a domain-level property years ago. The setting doesn't touch AI training at all. For training, Google still points publishers to a separate robots.txt token called Google-Extended, and that's where most of the confusion starts.

What does each control do to rankings, snippets and AI citations?

Each control works at a different scale, and each one reaches a different amount of your search presence. The Search Console setting is the only one that removes a site from AI Overviews and AI Mode without touching its regular search snippets. The robots-based rules (nosnippet, max-snippet and data-nosnippet) restrict previews everywhere. That includes the classic text snippet under your blue link, featured snippets and the AI features. Google-Extended governs something else entirely. Think of it as three layers: a property-wide AI switch, page-level and element-level preview rules, and a training opt-out that sits outside Search. Mixing them up is the most common mistake we see, because the names sound alike and the documentation used to live on separate pages. The table below shows what each one changes and what it leaves alone.

The nosnippet rule is set in a robots meta tag or an X-Robots-Tag header. It tells Google not to show any text snippet or video preview for the page. Google's robots documentation says it applies across web search, Images, Discover, AI Overviews and AI Mode. It also stops the page's content from being used as a direct input for those AI answers. That's a steep price. Your listing shrinks to a bare title and URL, which rarely wins the click against competitors who show a helpful two-line description. The max-snippet rule is the adjustable version. Set it to a number of characters and Google caps both the visible snippet and how much of your content can feed AI Overviews and AI Mode. A value of 0 behaves like nosnippet. A value of -1 means no limit at all.

The data-nosnippet attribute is the precise tool. You add it to a span, div or section element, and Google leaves that text out of snippets and AI answers while the rest of the page stays fully eligible. It only works on those three elements, and Google ignores any value you give it, so the bare attribute is enough. It's a good fit for a pricing block that changes weekly, a patient testimonial, or legal boilerplate you'd rather not see quoted out of context. Google-Extended works differently. It's a robots.txt token that controls whether Google can use your content to train Gemini models and ground answers in Gemini Apps and Vertex AI. AI Overviews and AI Mode draw on the regular search index that Googlebot builds, so blocking Google-Extended doesn't remove you from them.

Does blocking Google AI Overviews hurt your SEO?

Officially, no. Google says opting out of its AI features through the Search Console setting isn't a ranking signal, and the robots preview rules don't directly change where a page ranks. But ranking was never the whole game. Visibility is. Picture a competitor cited in the AI Overview at the top of the page while you've opted out. They get the brand exposure and the link, and you sit below the fold. You might hold the same position you held last year, with far less attention on it. Rankings nobody sees don't pay the bills. That's why we'd argue the real cost of blocking shows up in impressions, branded searches and assisted conversions, not in a rank tracker. The tracker keeps reporting good news while the traffic thins.

The blunt tools carry an extra penalty. nosnippet and a tight max-snippet also strip or shrink your regular description, so you lose clicks on the classic results too, which is the very traffic you were trying to protect. A listing with no snippet looks incomplete, and searchers skip it. We've covered elsewhere why meta descriptions still shape clicks even though they don't move rankings. nosnippet throws that lever away entirely and overrides whatever description you carefully wrote. There's a subtler cost for anyone investing in GEO, too. Buyers increasingly build their shortlist from AI answers before they ever click. If you're absent, you're never in the running. Your brand doesn't appear, your expertise isn't quoted, and the assistant recommends someone else.

The counterargument deserves a fair hearing. Many publishers worry that AI Overviews answer the question right on the results page, so a citation earns a mention but no visit. For some query types, like quick definitions, simple conversions or a single fact, that's true, and the click was never coming anyway. The questions businesses actually care about are different. Which treatment suits a specific case? How does a legal process work in your state? Which product fits a particular need? A short AI summary of those tends to raise more questions than it answers, and the cited source is the natural next click. Google keeps tweaking the interface, and our piece on what happens to clicks when the AI Overview label disappears looks at how that plays out.

When does restricting previews actually make sense?

Restricting previews makes sense in a few narrow cases where the content itself, not the click, is the product. A paywalled publisher, a paid research firm or a membership site sells the full text, so it has a real reason to cap what Google can quote. An AI summary that gives away the conclusion undercuts the subscription. Even then, max-snippet or data-nosnippet on the key sections usually beats a blanket nosnippet, because a short teaser still sells the click. Pages with sensitive information are another fair case. Think of internal documents that slipped into the index, or details you're legally required to show only in full context. For most of these, though, noindex or proper login protection is the real fix. A snippet rule still leaves the page findable.

Regulated industries sit in a grey zone. A clinic or a financial adviser may worry that an AI answer will paraphrase their advice badly or drop a disclaimer. That concern is reasonable, but blocking the whole site is rarely the answer. A targeted approach works better. Wrap dosage tables, rate quotes or time-sensitive offers in data-nosnippet so they're never lifted out of context, and leave your explanatory content open so it can be cited. Then write that open content so it survives being summarized: put the key caveat in the same sentence as the claim, not three paragraphs later. Clear, specific, self-contained content tends to be quoted accurately. That protects you better than silence does, and it keeps your practice in the conversation when patients ask an assistant for help.

Then there's Google-Extended, which many site owners block on principle. That's a legitimate decision about AI training, and it's yours to make. Just be clear about what it buys you. Google says it won't remove you from AI Overviews or AI Mode, and it isn't a ranking signal for Search. One industry analysis did find that sites blocking Google-Extended were retrieved less often by AI Overviews, though its own authors called the link surprising rather than proof of cause. Our take: blocking Google-Extended is a position on training, not a way to control search visibility. Don't expect it to keep your content out of AI answers, and don't assume it has no side effects either. If training genuinely bothers you, block it. If you have no strong objection, there's little to gain from doing so.

Which controls should a business leave open?

For most businesses trying to grow organically, the right default is simple. Leave the Search generative AI setting on, use no nosnippet tags, set max-snippet to -1 or leave it out, and save data-nosnippet for specific passages you really don't want quoted. That setup keeps you eligible for classic snippets, featured snippets, AI Overviews and AI Mode at the same time. Each one is a chance to be seen by a prospect who's actively researching the problem you solve. Restricting should be the exception, backed by a business reason, not a precaution applied out of habit. Ask two questions. What specific harm would a citation cause? What would you lose by being invisible in AI answers? If you can't answer the first, keep the door open. Staying open is the default whose benefits keep adding up.

Before you change anything, audit what's already there, because the most damaging settings are usually accidental. Check the Search generative AI setting in Search Console for every property you own, including any old domain-level property a narrower one might inherit from. Crawl your site for robots meta tags and X-Robots-Tag headers that contain nosnippet or a low max-snippet value. Staging configurations and SEO plugins are frequent culprits. Search your templates for data-nosnippet and make sure it only wraps what it should. Review robots.txt for a Google-Extended rule and decide whether it reflects a real policy. Finally, check where you're actually being cited. Our GEO score checker shows how ready your pages are for AI answers, and our guide to how AI Mode weighs competing sources explains what earns the citation.

Leaving the controls open is only half the job. The other half is publishing content worth citing. AI Overviews and AI Mode draw from pages that rank and answer questions directly, so steady, well-structured publishing on the topics your customers search is what turns eligibility into citations. Organic growth rewards that work over time, and unlike paid ads it doesn't stop the day the budget runs out. If you're weighing that trade-off against PPC, our breakdown of whether SEO is cheaper than Google Ads in 2026 runs the twelve-month numbers. Artiql is built to keep that publishing engine running for you in every language you sell in, with pricing tailored to your business after a short call. Want a second pair of eyes on your settings? Book a demo and we'll go through them with you.

Frequently asked questions