Could a Search Console setting be hiding my site from AI Overviews?

Google treats inclusion in its generative AI features as the default. Its Search Console help documentation (as verified in August 2026) says inclusion "is the default control for all properties." You don't have to opt in, and the page on whether you need to opt in to AI Overviews covers that side.

The risk runs the other way. The control lets a property owner opt out of three surfaces:

• AI Overviews
• AI Mode
• Generative AI features in Google Discover

Google says it expects to update that list over time.

Three properties make this control easy to miss:

1. It is invisible from outside. No crawl, header or robots.txt file reveals it. Only someone with Search Console access can see it.
2. It inherits. For child properties the default is "Inherit control from parent." An opt-out set on a parent applies to everything under it.
3. There is no robots.txt alternative. Google has no robots.txt token for AI Overviews or AI Mode. Googlebot rules and this Search Console control are the levers, so this setting carries a lot of weight.

The result: a property can be excluded from AI Overviews, AI Mode and Discover AI features without anyone on your team remembering a decision. The next move is to check every property, not just the one you use daily.

The inherited setting is the main trap. Picture a hypothetical company with a domain-level property and several URL-prefix properties for a blog, a help centre and a regional site. Someone opts the parent out during a content-licensing discussion. Every child set to inherit follows it, including the blog your marketing team is trying to get cited.

Other conditions that raise the odds:

• Many properties, many owners. Agencies, past employees and legal teams may all have had access.
• Restructured accounts. New child properties default to inheriting, so a property created last month takes the parent's setting automatically.
• Partial rollout. Google's documentation says the control is rolling out to a subset of website owners. If you can't see it yet, someone else on a parent property might.

One edge case to keep straight: the opt-out removes display in these AI surfaces, but Google states it can still use content "to power Google Search as a whole, like helping our systems better understand the language of users' queries." The page on what Google can still do with your content after opting out goes deeper.

Here is what Google documents, and what it does not.

Google's AI features documentation sets the floor: a page must be indexed and eligible to show in Search with a snippet, and "there are no additional technical requirements." So the control can only remove you. Leaving it on buys eligibility, not citations.

Keep Google-Extended separate in your head. Google's common crawlers page says it governs training and grounding for Gemini Apps and Vertex and "does not impact a site's inclusion in Google Search." Blocking it won't remove you from AI Overviews, and allowing it won't add you. If ranking side effects worry you, read whether opting out hurts rankings.

Work through every property you can find, not just your main one.

1. List every property. Include domain properties, URL-prefix properties and any subfolder properties. Ask whoever manages the account whether properties exist under other users.
2. Open the AI features control on each one. Note whether it says included, opted out, or inherit from parent. If you don't see the control, the rollout may not have reached that property yet.
3. Trace inheritance upward. For every child set to inherit, find the parent and record its value. That parent value is what the child actually uses.
4. Fix deliberately. If an opt-out was a real decision (for example, a licensing policy), leave it and document why. If not, switch the parent back or override the child.
5. Check on-page controls too. noindex, nosnippet, max-snippet:0 and data-nosnippet also keep content out of AI answers. Google documents these in its robots meta tag specifications. Templates often inherit them by accident.

For a step-by-step walkthrough across large accounts, use the playbook on auditing inherited AI controls. The free Search Console AI control check is a faster first pass. Google's AI features control guide explains each setting in detail.

A correct setting removes one block. It doesn't put you in AI Overviews. Next, confirm the other gates.

• Index status. Use URL Inspection to confirm key pages are indexed. No crawl from outside can tell you this.
• Generative AI impressions. Search Console's generative AI report shows impressions for AI Overviews and AI Mode, with no clicks, CTR or position. The generative AI report playbook covers how to read it. A confirmed Google-side bug depressed impressions from around 12 to 13 August 2026, so treat trends across that window with caution.
• Facts on the page. State specific facts (prices, numbers, one-line definitions) in fetchable HTML. That gives the engine a sentence it can quote.

What you can't control: whether an AI Overview triggers for a query, and which sources Google picks. What you can control: making sure no setting of yours is saying no.