If I opt out of Google's AI features, can Google still use my content?

Google treats showing your page in an AI answer and using your content in its systems as two separate questions. The Search Console control for generative AI features answers the first one only.

As of October 2026, that control covers three surfaces: AI Overviews, AI Mode, and generative AI features in Google Discover. Google says it expects to update that list over time. When you opt out, your pages stop appearing as supporting links on those surfaces.

Google is explicit about what the opt-out leaves in place. Your content can still be used "to power Google Search as a whole, like helping our systems better understand the language of users' queries." In other words, Googlebot still crawls you, your pages stay in the index, and Google still learns from them inside Search.

The opt-out is also not a training control. Training and grounding for Gemini Apps and Vertex AI run through Google-Extended, a robots.txt token. So the honest answer is: opting out reduces where Google displays you, not where Google uses you. If you want to limit a specific use, you need the control built for that use.

Google runs several AI paths, and each has its own switch. This table maps them as of October 2026.

Two points from Google's documentation shape this map. First, Google says Google-Extended "does not impact a site's inclusion in Google Search nor is it used as a ranking signal." Second, there is no robots.txt token for AI Overviews or AI Mode. Google says AI is built into Search, which is why Googlebot's robots.txt rules are the crawl control there. The full comparison is in Google-Extended vs Googlebot.

The control works as an opt-out, not an opt-in. Google says inclusion "is the default control for all properties." You do nothing to be eligible.

Eligibility itself still depends on ordinary Search rules. Google's AI features documentation says a page must be indexed and eligible to show with a snippet to appear as a supporting link, with no additional technical requirements. It also says indexing and serving are not guaranteed.

Here is what the opt-out does not do, per Google:

• It is not used as a ranking or inclusion signal for other parts of Search. The detail is in whether opting out hurts your rankings.
• It does not stop training. Google-Extended is that lever.
• It does not stop Google using your content to understand queries and run Search.

One caveat on scope: Google's help documentation said the control was rolling out to a subset of website owners. Many properties may not see the toggle yet. The step-by-step setup is in our guide to Google's AI features control in Search Console.

Inherited settings

For child properties, the default is "Inherit control from parent." A parent property set to opt out can silently remove every child from AI Overviews, AI Mode and Discover generative AI. Nothing on the page tells you, and no crawler can see it from outside. Run an audit of inherited AI controls across your properties if you manage more than one.

Blocking Google-Extended expecting to leave AI Overviews

This is a common mistake. Google-Extended governs Gemini Apps and Vertex AI. It does not remove you from AI Overviews or AI Mode, because those run on Googlebot's crawl.

On-page snippet controls

nosnippet, max-snippet:0 and data-nosnippet limit what Google shows, and AI features depend on snippet eligibility. They also affect classic search snippets, so they are blunter than the Search Console control. Check templates for accidental use, for example a data-nosnippet added to hide a cookie banner that wraps real content.

Discover

Discover's generative AI features sit under the same Search Console control. See whether your content can appear in Discover AI summaries.

Decide which use you want to stop, then set only that control.

1. Want to stay in Search and AI answers, but stay out of Gemini training? Disallow Google-Extended in robots.txt and leave Googlebot allowed. The same pattern across vendors is in block AI training but keep AI search.
2. Want to stay in Search but out of AI Overviews and AI Mode? Use the Search Console control if you have it. Accept that Google still uses your content inside Search.
3. Want to stay visible everywhere? Check that no parent property has opted you out, that Googlebot is allowed, and that no noindex or nosnippet sits on pages you care about.
4. Record what you set and when. Google says the list of covered surfaces will change, so recheck after announcements.

What you control is eligibility. What you cannot control is whether Google picks your page for a given answer.

Does blocking Google-Extended stop Google from training on my content? Google-Extended tells Google not to use your content for training and grounding in Gemini Apps and Vertex AI. Google says it does not affect your inclusion in Google Search or act as a ranking signal. It is a robots.txt token, so it only applies to content Google crawls after you add the rule. It does not change how Search itself uses your pages, and it does not remove you from AI Overviews or AI Mode.

Is there a robots.txt rule that removes me from AI Overviews only? No. As of October 2026, Google has no robots.txt token for AI Overviews or AI Mode. Google says robots.txt directives for Googlebot are the crawl control, because AI is built into Search. Blocking Googlebot removes you from Search as a whole. For AI surfaces alone, the options are the Search Console control, where available, or on-page snippet controls, which also affect classic snippets.

Will opting out of AI features lower my normal rankings? Google says the AI features control is not used as a ranking or inclusion signal for other parts of Search. That is Google's stated position, and nobody outside Google can verify it directly. What does change is that your pages stop appearing as supporting links in AI Overviews, AI Mode and Discover's generative AI features. Classic results are governed by the usual Search systems.

Why can't I see the AI features control in Search Console? Google's help documentation said the control was rolling out to a subset of website owners, so many properties may not have the toggle yet. Inclusion is the default either way. If you manage several properties, also check the parent: child properties inherit its setting by default, so a property can be opted out even when its own screen shows no change.

Does the Gemini API's Google Search grounding follow the same controls? It is a separate path. Developers who call the Gemini API can turn on Grounding with Google Search, which is billed separately and distinct from AI Overviews, AI Mode and the Gemini app. Do not assume the Search Console AI features control covers it. Treat each Google AI path as its own surface when you decide what to allow.