Auditing the Search Console AI Features Control Across Every Property

Google's generative AI control in Search Console decides whether a property's pages can appear in AI Overviews, AI Mode and generative AI features in Google Discover. Google says it expects to update that list over time.

Three facts make it easy to get wrong:

• It is opt-out. Inclusion is the default control for all properties. You don't need to do anything to be eligible, as the opt-in question explains. Something has to change for you to be excluded.
• It inherits. For child properties, the default is "Inherit control from parent". An opt-out on a parent flows down to every child left on the default.
• It is invisible from outside. No page crawl, robots.txt parser or public API reads it. A third-party tool can't see it, and neither can your SEO agency unless it has account access.

There is also no robots.txt token that targets AI Overviews or AI Mode on their own. Googlebot rules cover all of Google Search, so this Search Console control is the lever for those surfaces. When we last checked Google's help documentation (August 2026), it described the control as rolling out to a subset of website owners. Some properties may not show it yet. Record that as a finding too.

What this means: a site can pass every technical check and still be excluded from Google's AI surfaces by one setting nobody remembers changing. For background on the control itself, read our guide to Google's AI features control in Search Console.

Inheritance only makes sense once you know which property sits above which. Multi-property accounts grow messy. Agencies add properties, regional teams verify subfolders, and old properties linger after migrations.

Say you run a hypothetical retailer with a broad property for the whole domain, plus narrower properties for the blog, a country folder and a help-centre subdomain. Each narrower property may be a child that inherits from the broad one. Confirm the relationship inside Search Console rather than assuming it from the URL.

Build a simple inventory with one row per property:

The gap between the displayed value and the effective value is the whole point of the audit. A child showing "Inherit control from parent" looks harmless. Its real state depends entirely on the parent.

Work from the top of the hierarchy down. You need owner-level access to see and change the control.

1. Export your property list. Pull every property in the account, including ones you think are retired. List any properties owned under other Google accounts that cover your domains.
2. Mark parents and children. Fill the Parent column in your inventory. Start with the broadest property.
3. Open the AI features control on each top-level property. Record whether it is included (the default) or opted out. Take a dated screenshot.
4. Open the control on each child. Record whether it inherits or carries its own explicit value. Screenshot it.
5. Resolve the effective value. For every child set to inherit, copy the parent's value into the Effective column. If the parent itself inherits, keep walking up.
6. Compare effective against intended. Flag every row where they differ. Those are your findings.
7. Note properties without the control. If a property shows no control because of the staged rollout, write that down and recheck later.
8. Check the other gates on flagged and unflagged sections alike. A page must be indexed and eligible to show with a snippet to appear as a supporting link in AI Overviews or AI Mode. Look for noindex, nosnippet, max-snippet:0 and data-nosnippet using our snippet controls audit, and confirm robots.txt lets Googlebot in.
9. Fix with intent, then record the change. Change a value only after confirming the intended policy with whoever owns it. Log who changed what and when.

Don't confuse this control with Google-Extended. That robots.txt token governs training and grounding for Gemini Apps and Vertex, not AI Overviews or AI Mode. The Google-Extended definition covers the difference.

Use this as the per-property pass. Every box should be ticked, or the exception written down with a reason.

• Property is in the inventory with its exact name and scope
• Parent property identified, or confirmed as top-level
• Current owners listed, and former staff or agencies removed if appropriate
• AI features control value recorded with a dated screenshot
• Control availability noted (present, or not yet rolled out)
• Effective value resolved through every inheritance level
• Effective value matches the documented intended policy
• Any explicit opt-out has a named owner and a written reason
• No unintended noindex on sections meant to appear in AI answers
• No unintended nosnippet, max-snippet:0 or data-nosnippet on that content
• robots.txt allows Googlebot on the sections you want eligible
• Generative AI performance report checked for impressions on included sections
• Change log updated with date, person and reason

The performance report is a sanity check, not proof. It shows impressions only, with no clicks, CTR or position. A confirmed Google-side bug depressed impressions from roughly 12 to 13 August 2026, so don't read a trend across that window. See how to view AI Overview impressions in Search Console.

A clean result

• Every property has a recorded, dated value.
• Every effective value matches the intended policy.
• Any opt-out is deliberate, documented and owned by a named person.
• Sections meant to appear in AI answers are indexed and snippet-eligible.

A result that needs action

• Silent inherited exclusion. A child shows "Inherit control from parent" and the parent is opted out. The child is excluded, and nobody chose that for it.
• Orphaned opt-out. A property is opted out and nobody knows who did it or why.
• Conflicting intent. A team wants its section in AI Overviews while a parent opt-out keeps it out.
• Hidden second layer. The control is fine, but a template-level nosnippet or data-nosnippet suppresses the content anyway.

A clean audit removes a block. It doesn't guarantee inclusion. Google states that indexing and serving isn't guaranteed, and there are no special optimizations needed beyond normal Search eligibility. You control the gates. You don't control what the model picks.

Run the full audit once a quarter. Also run it whenever one of these happens:

• A new property is added or verified.
• A site migration, domain change or subdomain launch.
• An agency, contractor or employee with owner access leaves.
• Google changes the surfaces the control covers. Google says it expects to update that list.
• The control first appears on a property that previously didn't have it.
• Impressions in the generative AI report drop sharply for one section and not others.

Keep the screenshots. They are the only evidence of the setting's state at a point in time, because nothing outside your account records it.

This audit covers Google only. To see whether other AI platforms name you for real buyer questions, the free checker on this site gives a quick snapshot.