Google's AI Features Control in Search Console: How the Opt Out Works

Google's Search Console has a setting for generative AI features. When Google's documentation was last verified in August 2026, it covered three surfaces: AI Overviews, AI Mode, and generative AI features in Google Discover. Google says it expects to update that list over time.

The key fact is the direction. Inclusion is the default control for all properties. You don't have to switch anything on to be eligible. The control exists so a site owner can switch it off. If you've been wondering whether you need to opt in to appear in AI Overviews, the answer is no.

Eligibility is a separate question from this setting. Google's AI features documentation says a page must be indexed and eligible to show in Search with a snippet to appear as a supporting link in AI Overviews or AI Mode. It adds that there are no additional technical requirements, and that indexing and serving isn't guaranteed. So the control can remove you, but leaving it on only keeps you in the running. It does not put you in an answer.

Google also states the setting isn't used as a ranking or inclusion signal for other parts of Search. Opting out of AI features does not, by Google's account, hurt your regular rankings.

Most access problems leave a trace you can check from outside. A robots.txt rule is a public file. A noindex tag sits in the page's HTML. A firewall block shows up as a 403 when a crawler requests the page.

This control leaves no trace. It lives inside Search Console. It is not in your HTML, your headers or your robots.txt. As of October 2026, Google offers no API for it. A crawler, an SEO audit tool or an agency without account access cannot read it.

That has two consequences:

• A clean technical audit can miss it. Your pages can pass every crawlable check and still be excluded from AI Overviews and AI Mode.
• Someone else may have set it. A former employee, an agency or a colleague managing a sister property could have opted out, and nothing on the site would show it.

The practical move is simple. Treat the setting as unknown until someone with access has looked at it. Our question page on whether a Search Console setting could be hiding your site from AI Overviews walks through the symptoms.

Search Console lets you register more than one property for the same site. For child properties, Google's default for this control is "Inherit control from parent."

That default is convenient and risky in equal measure. One change at the parent level flows down to every child that still inherits. Nobody has to touch the child property for it to change.

A hypothetical example

Say you run a software company with a parent property for the whole domain and child properties for the blog, the docs and a regional subfolder. Someone opts out at the parent level to keep a test section out of AI answers. Every child set to inherit is now opted out too. The blog team sees no change on their pages and no warning in their reports. Their content simply stops being eligible for AI Overviews and AI Mode.

What to record

For each property, note two things: whether it inherits, and what the effective setting is. A child can override its parent, so a mixed setup is possible. Write it down in one place so the next person doesn't have to rediscover it. For multi-property setups, the playbook on auditing inherited AI controls across GSC properties gives a step-by-step audit sheet.

Google has several controls that touch AI features. They do different jobs, and confusing them is the most common error. As of October 2026, there is no robots.txt user-agent token that blocks AI Overviews or AI Mode on its own. Google's position is that AI is built into Search, so robots.txt rules for Googlebot are the crawl-level control.

Google's crawler documentation says Google-Extended does not affect a site's inclusion in Google Search and is not a ranking signal. Blocking it will not remove you from AI Overviews. Leaving it open will not put you in them.

If your goal is to keep one section of a page out of AI answers while staying in Search, the snippet controls are the finer tool. The guide on keeping specific content out of AI answers covers when to use each one.

Be clear about which side of the line each factor sits on.

In your control

• The Search Console AI features setting on every property you own.
• Whether child properties inherit or override.
• Googlebot access in robots.txt.
• noindex and snippet directives on your pages.
• Whether your important facts are stated plainly on pages Google can index.

Not in your control

• Whether Google triggers an AI Overview for a given query. Many queries don't get one.
• Which indexed, eligible pages Google chooses to cite.
• How Google uses your content elsewhere in Search. Google says opting out of display doesn't stop content being used to power Search as a whole, such as helping its systems understand the language of users' queries. More on that in whether Google can still use your content after you opt out.
• How the AI answer describes you, once it does cite you.

The setting is a gate. Fixing a closed gate removes a block. It doesn't create demand or earn a citation.

Do these in order. Each step rules out a cause before you spend time on the next.

1. List every property. Pull the full list of Search Console properties tied to your domains, including subdomains and subfolders. Note which are parents and which are children.
2. Open the AI features setting on each one. Record whether it is included, opted out, or inheriting. If you can't find the setting, the control may not have reached your property yet. Google was rolling it out to a subset of owners when its documentation was last verified in August 2026.
3. Resolve inheritance. For every child set to inherit, write down the parent's effective setting. That is the child's real setting.
4. Ask who changed it. If anything is opted out, find out who did it and why. Sometimes it's deliberate. Keep deliberate opt-outs and document the reason.
5. Check crawl and index eligibility. Confirm robots.txt lets Googlebot in, key pages carry no stray noindex, and snippet directives aren't set to nosnippet or max-snippet:0 by accident. Use URL Inspection to confirm key pages are indexed.
6. Read the generative AI report. The generative AI report in Search Console shows impressions for AI Overviews and AI Mode. As of October 2026 it shows impressions only, with no clicks or position. Google confirmed a bug that depressed impressions from about 12 to 13 August 2026, so don't read a trend across that window.
7. Recheck after changes. Re-run this list whenever properties are added, owners change, or an agency hands over access.

If you'd rather work through a guided version, the free Search Console AI control check follows the same steps. Once the gate is confirmed open, the free checker on this site shows whether AI engines name you for up to three buyer questions.

These come up repeatedly when teams look at Google's AI controls.

• Assuming you need to opt in. Inclusion is the default. Teams that hunt for an opt-in switch sometimes toggle the wrong setting.
• Checking only the main property. An opt-out on a parent can silently cover every inheriting child. Check them all.
• Treating Google-Extended as the AI Overviews switch. It governs Gemini Apps and Vertex AI training and grounding. It doesn't touch AI Overviews or AI Mode.
• Looking for a robots.txt token for AI Overviews. None exists as of October 2026. Blocking Googlebot removes you from all of Search, not just AI features.
• Trusting an external audit on this point. No crawler can read the setting. An audit that says "all clear" has not checked it.
• Reading a missing toggle as an opt-out. If the control hasn't rolled out to your property, the default still applies.
• Expecting the setting to earn citations. Being included keeps you eligible. Google still decides which pages to cite, and says there are no special optimizations required to appear.
• Using the opt-out to fix a single page. If one block of text shouldn't appear in AI answers, data-nosnippet or snippet limits are narrower and keep the rest of the site eligible.