Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Searchers cannot turn off AI Overviews completely, but they can choose Google’s Web filter for a text-based list of links. Website owners have a separate Search Console control to include or exclude a property from AI Overviews, AI Mode, and generative AI features in Discover. That exclusion does not remove pages from ordinary Google Search or change their ordinary Search ranking.
These are different controls for different outcomes. A Search Console setting governs participation in certain generative features; page directives govern whether Google indexes a page or shows a preview; and robots.txt governs crawling. Choosing the wrong one can leave a page visible when you meant to remove it, or hide useful snippets when you only meant to prevent crawling.
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Can searchers turn off AI Overviews?
No. Google describes AI Overviews as a core Search feature that cannot be turned off. After searching, however, you can select the Web filter to see a text-based results view of links without AI Overviews.
The Web filter is a viewing option, not a permanent preference that disables AI features across Google Search. It also does not change what publishers have allowed their content to be used for. If an AI-generated answer is present, Google advises checking important claims against multiple sources because AI Overviews can make mistakes.
#1 Best Overall
This distinction matters if your goal is simply to see conventional links: use Web after searching. If you own a website and want to control whether its content can be included in certain AI experiences, the Web filter is not the relevant setting; use the property-level Search Console control described below.
How can a website opt out of Google’s AI Search features?
A site owner can use the Search generative AI control in Google Search Console to include or exclude a property from AI Overviews, AI Mode, and generative AI features in Discover. Google Search Console Help says this control rolled out to websites worldwide on August 31, 2026. The setting concerns those named generative features, not Google Search as a whole.
Free tools Windows power users keep installed
One-click scans. No signup required.
Choose the property setting that matches your intent
- Include: permits the property to participate in the covered generative features. Google identifies this as the default when no parent-property override applies.
- Exclude: prevents the site’s links and content from appearing in the covered features and prevents crawled content from being used as input for an AI response or preview.
- Inherit from parent: lets a property use its parent property’s setting rather than applying a separate choice.
Because the setting applies to a property, check that you have selected the property that covers the site or pages you intend to manage. If a property inherits its setting from a parent, its effective choice may not be the same as a separately configured child property. Review the setting that applies to the property rather than assuming that a change to one property automatically governs every other property you manage.
Apply the control in Search Console
- Open Google Search Console and select the property you want to manage.
- Locate the Search generative AI control for that property. Google’s documentation identifies the control, but the exact navigation labels can change; follow the current Search Console interface rather than relying on an older menu path.
- Choose Exclude to opt the property out of the covered generative features, or choose Include or Inherit from parent if those settings better match your preference.
- Allow time for Google’s systems to apply the change. Check again after propagation, particularly if a page still appears in a feature shortly after the setting goes live.
Google says changes generally take a few days. In many cases, exclusion takes effect within 1–2 days after the control goes live, but caching and propagation across Google’s systems can delay some content. That is an expected processing window, not an immediate guarantee for every URL. If a page appears during that period, it does not necessarily mean the setting failed; allow for propagation before drawing that conclusion.
Use Exclude when your objective is specifically to prevent participation in the covered generative features. It is not a general privacy switch, a crawl block, or a command to erase the page from Google. Nor does it change separate choices you have made about Merchant Center or Google Ads.
Does excluding a site from AI features remove it from Google Search?
No. Google says the Search generative AI control affects only whether content can appear in specified generative features; it is not a ranking or inclusion signal for other parts of Search. A page may therefore remain indexed and appear in ordinary search results even when the property is excluded from AI Overviews, AI Mode, and generative AI features in Discover.
Recommended Free Tools
Rank #2
Think of this as a feature-specific participation choice, not a deindexing command. If your goal is to remove an individual page from Google Search, the relevant page-level instruction is noindex, not the AI control. If your goal is to limit how a result preview looks, use a snippet directive instead.
In practical terms, the controls answer different questions: “Can this property appear in these generative features?” is answered by the Search Console setting; “Can this page appear in the Search index?” is answered by an accessible noindex instruction; and “What preview can Google show?” is addressed by snippet directives. Excluding a site from AI features should not be expected to lower or remove its ordinary Search results.
What is the difference between robots.txt, noindex, nosnippet, and max-snippet?
They work at different layers: crawling, indexing, and how a result is presented. The right choice depends on whether you want Google to fetch a page, list it in Search, or display a preview of it.
| Control | What it governs | Effect on indexing and appearance | Effect on ordinary ranking | Where it is set | Timing |
|---|---|---|---|---|---|
robots.txt |
Crawl access | Blocks Googlebot from crawling the page. It does not itself serve as a reliable way to enforce page-level instructions that Google cannot read. | It is a crawl control, not a specified ranking or deindexing instruction. | In the site’s robots.txt file | No specific propagation window is stated here. |
noindex |
Search indexing | When Google can crawl and see the instruction, it removes the page from Google’s Search index. | It removes the page from the index rather than changing its ordinary ranking. | As a page-level instruction | Google must be able to crawl the page to see it; no fixed timing is stated here. |
nosnippet |
Search-result previews | Keeps the URL eligible to appear, but tells Google not to show a text snippet, video preview, or rich-result visual elements for that page. | It controls the preview, not ordinary ranking. | As a page-level instruction | No specific propagation window is stated here. |
max-snippet |
Text snippet length | Limits the maximum length of a text snippet. Google also lists it among reasons a snippet may be shorter than expected. | It limits preview length rather than indexing or ordinary ranking. | As a page-level instruction | No specific propagation window is stated here. |
| Search generative AI control | Specified generative Search features | Includes or excludes a property from covered AI features; it does not deindex pages or change ordinary Search ranking. | Google says it is not a ranking or inclusion signal for other parts of Search. | In Search Console | Generally a few days; often 1–2 days after the control goes live, with possible longer delays. |
The URL outcome is an important difference. A page with noindex is removed from the Search index once Google can see the directive. With nosnippet, the URL remains eligible to appear, but its preview is suppressed. max-snippet sets a ceiling on text-preview length rather than removing the URL. The Search generative AI control governs the specified AI surfaces while leaving ordinary Search eligibility and ranking unaffected.
Why a robots.txt block can undermine a page directive
Google has to crawl a page to see page-level instructions such as noindex or nosnippet. If robots.txt blocks Googlebot from reading that page, Google may know that the URL exists but cannot see the directive on it. A crawl block is therefore not a substitute for noindex when the outcome you want is removal from the Search index, nor is it a dependable way to apply a snippet restriction while hiding the page from crawling.
This is a common implementation pitfall: combining a robots.txt block with a page directive and assuming Google can obey both. The block can prevent Google from fetching the page and discovering the directive. Choose the control based on the desired outcome, and do not use robots.txt as though it reliably enforces noindex or nosnippet.
Choose by the outcome you need
- To keep a page out of Google Search, use
noindexand ensure Google can crawl the page to see it. - To keep a URL eligible while suppressing its preview, use
nosnippet. - To restrict the length of a text preview rather than suppress it entirely, use
max-snippet. - To restrict crawling, use
robots.txt, understanding that a blocked crawler cannot read page-level directives. - To opt a property out of the specified generative Search experiences, use the Search Console control rather than a crawl or indexing directive.
How do I control Google featured snippets?
Publishers cannot request or guarantee a featured snippet. Google’s systems select short extracts from websites when they determine that a concise answer may satisfy a query.
Featured snippets can appear at the top of Search results, in People also ask, or alongside Knowledge Graph information. This is a selection made by Google’s systems, not a placement a publisher can claim by applying for it. Google also applies feature-specific policies. Its documented examples include dangerous, deceptive, harassing, hateful, manipulated-media, medical, sexually explicit, terrorist, violent, and vulgar content, as well as certain public-interest claims that contradict established consensus or lack supporting evidence.
Snippet controls change what Google may show from a page; they do not guarantee a different featured-snippet result. nosnippet suppresses previews while leaving a URL eligible to appear, and max-snippet limits text-preview length. Neither directive is a request for a featured snippet.
If you do not want Google to show a text extract from a page, nosnippet is the direct preview control, with the trade-off that it suppresses the text snippet rather than selectively asking for a different extract. If you want to limit the amount of text shown instead, max-snippet sets a maximum length. These directives affect search-result presentation; they do not make Google select a particular passage or guarantee that a page will appear in a featured-snippet placement.
Is the AI Search control the same as Google-Extended or noindex?
No. Google identifies these as distinct mechanisms. The Search generative AI control governs inclusion in specified generative Search features; noindex is the directive for keeping a page out of Google Search entirely. Google-Extended is a separate mechanism Google identifies for limiting training use.
Do not treat one control as a broader version of another. The AI setting does not replace an indexing directive, and the stated purpose of Google-Extended is not the same as opting out of AI Overviews or AI Mode. Choose the control that matches the particular use you want to address.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchRank #4
For example, if you want a page to remain in ordinary Search but not appear in the covered AI experiences, use the Search Console control. If you want the page removed from Search, use noindex and make sure Google can crawl it. If your concern is training use, Google identifies Google-Extended as the separate mechanism for that purpose. These are not interchangeable settings.
What happens to ads and other Google services when I exclude a property?
The Search generative AI control is limited to the generative features Google specifies. Google says it does not override separate participation choices in Merchant Center or Google Ads. A property owner who wants to manage those services must handle their settings separately rather than assuming the Search Console exclusion changes them.
What should I check before choosing a control?
Start with the outcome, not the name of a directive. Ask whether you want to prevent a page from being crawled, remove it from the Search index, suppress its preview, limit the text shown, or prevent the property from appearing in named generative features. Then select the control that addresses that layer.
- If ordinary Search visibility should remain unchanged but generative feature inclusion should stop, set the property to Exclude in Search Console.
- If the page itself should no longer be indexed, use
noindexand avoid blocking the crawl needed for Google to read it. - If the page may remain in results but should not have a preview, use
nosnippet; if only the preview length needs a limit, usemax-snippet. - If you want to prevent crawling, use
robots.txt, but do not expect a blocked page’s directives to be read.
Also keep timing in mind. The AI exclusion may take a few days to propagate, often 1–2 days after the control goes live, and caching can extend that for some content. By contrast, the other controls work at different layers and should not be assigned the AI control’s propagation estimate. Google does not state a fixed timing window for them in the guidance summarized here.
Frequently Asked Questions
What is AI Mode, and how does it differ from an AI Overview?
Google describes AI Mode as an AI search experience for follow-up questions and deeper exploration. It can divide a question into subtopics and search for them simultaneously; when confidence in an AI response is not high enough, Google may instead provide web links.
Can I ask Google to give my page a featured snippet?
No. Google selects featured snippets programmatically, and publishers cannot request one. A page may be considered by Google’s systems, but there is no publisher application or guaranteed placement.
Does opting out of AI features also stop Google from using a page for training?
The Search generative AI control and Google-Extended address different uses. Google identifies Google-Extended as the separate mechanism for limiting training use; the Search Console control governs inclusion in the specified generative Search features.
Can I stop my website from appearing in Google AI Overviews without removing it from Search?
Yes. Set the property’s Search generative AI control to Exclude in Search Console. Google says this affects the covered generative features, not ordinary Search inclusion or ranking, so pages may remain in regular results.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →How long does it take for an AI-feature exclusion to take effect?
Google says changes generally take a few days. In many cases exclusion propagates within 1–2 days after the control goes live, though caching and propagation across Google’s systems can delay some pages.
What is the difference between noindex and nosnippet?
When Google can crawl and see it, noindex removes a page from Google’s Search index. nosnippet keeps the URL eligible to appear but tells Google not to show a text snippet, video preview, or rich-result visual elements.
Does robots.txt remove a page from Google Search?
robots.txt controls crawling; it is not the page-level instruction for removing a URL from the index. If it blocks Googlebot, Google may be unable to read a page’s noindex or nosnippet instruction. Use noindex for Search exclusion and allow Google to crawl the page to see it.
Can searchers permanently switch off AI Overviews?
No. Google says AI Overviews are a core Search feature and cannot be turned off. After searching, use the Web filter for a text-based view of links without AI Overviews.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →The Bottom Line
Match the control to the outcome: use the Web filter to view links without AI Overviews, Search Console’s Search generative AI control to exclude a property from the covered AI features, noindex to remove a page from Search, and nosnippet or max-snippet to manage previews. robots.txt controls crawling and can prevent Google from seeing page-level directives. Excluding a property from AI features does not remove it from ordinary Search or change its ranking.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
