Opt out of AI Overviews: the Search generative AI control
How to opt out of AI Overviews and AI Mode with the Search Console Search generative AI control, what Exclude costs, how inheritance works and what it leaves alone.
By Crawlito · 9 min read
In short
- Search Console has a site-level switch under Settings > Search generative AI that can exclude a property's links and content from AI Overviews, AI Mode and generative AI features in Google Discover.
- Google's help page says the control had reached all websites worldwide as of 31 August 2026, with Include as the default and Inherit control from parent as the default for any property that has a parent.
- Google says Exclude is not a ranking or inclusion signal for the rest of Search, but an excluded site gets no traffic or impressions from those features.
- The control does not affect AI training, which Google points to Google-Extended for, and it does not override Merchant Center or Google Ads choices.
- Google says exclusion generally takes a few days, with content excluded within one to two days after the control goes live and some taking longer because of caching and propagation.
On this page
- What the Search generative AI control is
- The three options: Include, Exclude, Inherit
- How parent and child properties inherit the setting
- How long a change takes
- Search generative AI control vs nosnippet, max-snippet, data-nosnippet and noindex
- What the control does not touch
- What opting out costs, and how to decide
- How to check the setting on your site
- Frequently asked questions
- Next step
Yes, you can now opt out of AI Overviews without leaving Google Search. Search Console has a setting under Settings > Search generative AI that excludes a property's links and content from AI Overviews, AI Mode and generative AI features in Google Discover. Google says the choice is not used as a ranking or inclusion signal for the rest of Search, so your ordinary results stay as they are. What you give up is every impression and click those AI features would have sent you.
This changes advice that was correct until recently, including in some of our own older posts: before this control, the only documented levers were page-level snippet rules that also cut your normal snippets. The facts below come from Google's Search generative AI control help page, read on 15 November 2026.
What the Search generative AI control is
The control is a per-property setting in Search Console. Google's help page says that as of 31 August 2026 it had been rolled out to all websites worldwide. It covers three features:
- AI Overviews, the summaries on a normal results page.
- AI Mode, the conversational search experience.
- Generative AI features in Google Discover. The help page lists these but does not define them further.
Google adds that it expects to update this list over time, so check the help page again before relying on it. It does not list any other Google product. The Gemini app, for example, is not mentioned, so do not assume the switch reaches it. How AI Overviews and AI Mode differ for users is covered in AI Mode vs AI Overviews; for this setting they are treated as one group.
Note that Google's developer page on AI features and your website did not mention this control when we read it. It still describes robots.txt for Googlebot and the snippet rules. The Search Console help page is the source for everything in this post about the switch itself.
The three options: Include, Exclude, Inherit
The help page labels the choices this way:
| Option | Label in the help page | What happens | Default for |
|---|---|---|---|
| Include | "Include my site's links and content in Search generative AI features" | Your content can appear in these features, including as links and as grounding for AI responses | Properties with no parent |
| Exclude | "Exclude my site's links and content from Search generative AI features" | Your links and content are not shown in these features, and content crawled from your site is not eligible as input for their responses or previews | Nobody: you choose it |
| Inherit | "Inherit control from parent" | The property follows its parent's choice | Any property that has a parent |
Google spells out what Exclude means in practice:
- You will not receive any traffic or impressions from these features.
- Other sites' content still appears there, and it may look similar to yours.
- It is not used as a ranking or inclusion signal affecting other parts of Search, though your content may still be used to power Google Search as a whole.
- It does not override your participation choices in services such as Merchant Center and Google Ads.
That third point is what makes the control different from everything that came before it. For the full list of what Google says Exclude does and does not touch, see the section on limits below.
How parent and child properties inherit the setting
Search Console properties nest. A parent can be a top-level domain property, a subdomain property or a URL-prefix property. The help page's inheritance rule is: by default a property inherits from its closest parent that has changed its control to stop inheriting, and if none has, from the top-level domain property.
A worked example with three properties:
example.com Domain property Exclude (set manually)
shop.example.com Subdomain property Inherit control from parent
https://example.com/research/ URL-prefix property Include (set manually)With these settings:
- Everything under
example.comis excluded, because the domain property was set to Exclude. shop.example.comfollows its parent, so it is excluded too.- URLs starting with
https://example.com/research/are included, because that property stopped inheriting and chose Include.
Two practical consequences follow.
You can use URL-prefix properties to act on a section. Search Console's property documentation says a URL-prefix property can include a path, and any URL that begins with that prefix belongs to it. The control has no per-page option, so a URL-prefix property is the narrowest scope it offers. For single pages, the page-level rules below are still the tool.
Somebody else may override you. Owners of a child property can choose to inherit or set their own value, and that value applies to the property and its subpages. Google says owners of the top-level domain property see a notification on the Search generative AI control page when a child property overrides the parent setting; owners of an intermediate parent, such as a subdomain property, are not mentioned. On a site where agencies or product teams have their own properties, check every child property, not only the top one.
How long a change takes
Google's help page gives two numbers. It says it generally takes a few days for a site's content to be excluded from these features. It also says content is excluded within one to two days after the control goes live, and that some content can take longer because of caching and propagation across Google's systems.
So plan in days, not hours, and record the date you change the setting. Switching back to Include is not given a separate timeline on the help page, so do not assume it is instant.
Search generative AI control vs nosnippet, max-snippet, data-nosnippet and noindex
Before this control existed, every documented way to limit AI Overviews also changed ordinary results. Those rules still work and still have that cost. Here is how they compare with the new switch:
| Control | Scope | Normal Google results | AI Overviews and AI Mode | Discover |
|---|---|---|---|---|
| Search generative AI: Exclude | Search Console property | Not a ranking or inclusion signal | Links and content excluded | Generative AI features excluded |
nosnippet | Page or file | No text snippet | Content not used as a direct input | Rule applies to Discover results |
max-snippet:[n] | Page or file | Snippet capped | Caps how much content is used as direct input | Rule applies to Discover |
data-nosnippet | Part of a page (span, div, section) | Marked text not in snippets | Listed by Google as a control for what AI features show | Not stated |
noindex | Page or file | Page not shown | Not eligible | Not shown |
Google-Extended Disallow | robots.txt | No effect on inclusion or ranking | Not the control for these features | Not stated |
The Discover column for nosnippet and max-snippet comes from Google's robots meta tag documentation, which lists Discover among the result types those rules apply to. The semantics of each page-level rule, including which elements data-nosnippet works on and how to send the rules as an X-Robots-Tag header, are in noindex, nosnippet and X-Robots-Tag.
A simple way to choose:
- Want a whole site or section out of Google's AI answers but still in normal results? Use the Search Console control.
- Want one page or one block of text kept out? Use
nosnippetordata-nosnippet, and accept the snippet cost on that page. - Want the page out of Google entirely? Use
noindex, which the help page itself recommends for that goal. For the wider removal workflow across assistants, see how to remove a page from AI search.
What the control does not touch
The help page draws several boundaries. Read them before you decide, because they are where people expect more than the switch delivers.
- AI training. Google says the control does not affect AI training, and points to Google-Extended for limiting training of the models behind these features. Google's common crawlers page describes Google-Extended in terms of Gemini Apps, the Vertex AI API for Gemini and grounding, and says it does not affect inclusion in Google Search. Google-Extended explained covers that token.
- Merchant Center and Google Ads. Exclude does not override your choices in those services.
- The rest of Search. It is not a removal tool. Google may still use your content in Search generally, and
noindexis the documented way to leave Search. - Googlebot crawling. The help page does not say the setting changes crawling, so keep your robots.txt and firewall rules for Googlebot as they are. Blocking Googlebot to get out of AI features would also stop Google crawling your pages for normal Search.
- Other AI assistants. ChatGPT, Claude, Perplexity and Copilot are not Google products, so this setting has no bearing on them. Their crawlers follow their own robots.txt tokens.
What opting out costs, and how to decide
Exclude has one documented cost: no traffic and no impressions from AI Overviews, AI Mode and Discover's generative AI features. How much that is for your site depends on how much of your Google traffic those features already send, which is a question for your own data rather than a general estimate.
Google suggests using the Generative AI performance report in Search Console to see how your content performs in these features and to judge what a change might do. Our guide to the Generative AI performance report explains what it shows. A reasonable sequence:
- Look at that report for the property, and note which pages and queries get impressions from AI features.
- Decide the scope: the whole domain, a subdomain, or a section you can isolate with a URL-prefix property.
- Write down the date and the property you changed, and who owns any child properties.
- Make the change, allow a few days, then compare the report with the period before.
Reasons sites choose Exclude include licensed or paid content they do not want summarised, and pages where a summary tends to answer the query without a visit. Reasons to keep Include: AI features can still send clicks, and excluding does not stop competitors' similar content from appearing. Neither choice guarantees anything about traffic. Eligibility for these features still follows the usual rules in the technical requirements for AI Overviews, and being eligible never guarantees being shown.
How to check the setting on your site
The setting lives in Search Console, not in your HTML or HTTP headers, so a curl of your page cannot show it. Check it there:
- Open each property you own and go to Settings > Search generative AI. Note whether it says Include, Exclude or Inherit.
- List every child property: subdomains and URL-prefix properties. Any one of them may have stopped inheriting.
- Make sure you can sign in to each property you need to change. The help page says a child property's control is set from that property, but it does not say which Search Console permission level can change it, so ask an existing owner for access if you cannot change it.
- Separately, check your pages for leftover
nosnippetormax-snippetrules. A page-level rule still limits AI features and normal snippets even if the property is set to Include.
Frequently asked questions
Can I opt out of AI Overviews and stay in normal Google results?
Yes. Set the property to Exclude under Settings > Search generative AI in Search Console. Google says this is not used as a ranking or inclusion signal for other parts of Search.
Does the control remove my site from AI Mode as well?
Yes. It covers AI Overviews, AI Mode and generative AI features in Google Discover together, and the help page offers no way to pick only one of them.
Can I exclude a single page with the Search generative AI control?
Not directly: it works per property. A URL-prefix property can isolate a section, and for a single page nosnippet or data-nosnippet remain the documented options.
Does excluding my site stop Google training AI on my content?
No. Google says the control does not affect AI training and points to Google-Extended for that.
How quickly does Exclude take effect?
Google says exclusion generally takes a few days, with content excluded within one to two days after the control goes live and some taking longer because of caching and propagation.
Next step
The Search Console switch only matters for pages Google can crawl and index in the first place, and leftover snippet rules can make the decision for you without anyone noticing. Before you decide how to set the control, run the free check on an important page. It covers one page, needs no account, and shows whether the main AI crawlers can fetch it.
Filed under Strategy and audits. Topics: google, ai-overviews, search-console, ai-search