Google has updated its Search generative AI control page in Search Console to display a notification to top-level domain owners whenever a child property manually overrides the parent’s setting. The update, reported by Search Engine Roundtable on October 6, 2026, adds a visibility layer to a feature that became globally available as of August 31, 2026, according to Google’s own support documentation.
What changed in the Search generative AI control page?
Google’s updated help document now states that owners of the top-level domain property (the root domain of a site, such as example.com) will see a notification on the Search generative AI control page when one of their child properties overrides the parent setting.
The three available control options, as documented by Google, are:
- Include, the site’s links and content can appear in Search generative AI features (the default for all properties).
- Exclude, the site’s content is prevented from appearing in those features; the property will receive no impressions or traffic from them.
- Inherit control from parent, the property follows the setting of its closest parent that has a manually configured control. This is the default when a parent property exists.
How does the parent-child inheritance work?
Google’s documentation explains that a property inherits its generative AI control from its closest parent that has stopped inheriting. If no parent in the chain has manually configured a setting, the property defaults to the top-level domain’s control.
For example: the child property https://example.com/business/cats inherits from domain property example.com by default, unless an owner of a closer parent (https://example.com/business/ or https://example.com/) has manually set a different control. Many properties, Google notes, can function as both a parent and a child of other properties simultaneously.
Once an owner changes a control setting, Google’s documentation states it generally takes a few days for the change to propagate, with most content excluded within 1-2 days, though some content may take longer due to caching across Google systems.
Two important scope limits are documented by Google. First, this control does not affect AI training; to limit training of the models used in Search generative AI features, webmasters should use Google-Extended (a separate robots.txt directive). Second, the control is not used as a ranking or inclusion signal for other parts of Search, and it does not override a publisher’s separate choices about services such as Merchant Center and Google Ads.
What this means for AI-search visibility
Think of it this way: if you manage a large site and your marketing team controls a subdirectory like /blog/ or /products/, they can set a different AI inclusion rule for that section. The new notification surfaces that on the top-level domain’s control page.
In Hingewise’s view, this update matters most to organizations that manage multi-section sites across different teams. Without such a notice, a top-level domain owner who had opted the whole site into generative AI features could miss a subdirectory that a team member had excluded, or vice versa. The notification now surfaces that kind of configuration drift directly on the Search generative AI control page.
The broader point: generative AI control operates at a property level, not a page level. If your site has multiple URL-prefix properties or subdomain properties verified in Search Console, each can carry its own setting. An “include” decision at the domain level does not guarantee every section of your site is included if someone further down the property tree has configured an override.
The feature being globally available as of August 31, 2026 also means that any property owner who has not yet reviewed their setting is implicitly on the default, “Include” for root properties, “Inherit from parent” for child properties. That default may or may not match the intent of each team managing a specific section.
The practical question going forward is whether Google extends this notification pattern to other levels of the property hierarchy, or whether it adds more granular logging so owners can see exactly which child changed what and when. Neither source indicates such changes are planned.
Quick checks before adjusting your generative AI control settings
- Verify which Search Console properties exist under your top-level domain and who owns each one.
- Log in to the top-level domain property and check whether any child override notification is currently displayed.
- Review the setting on each verified child property, “Inherit from parent,” “Include,” or “Exclude”, to confirm it matches your intent.
- Confirm that any decision to exclude applies to the right scope: this control removes content from Search generative AI features but does not remove it from standard Search results (use
noindexfor that) and does not block AI training (use Google-Extended for that). - If multiple teams manage different sections of the site, agree on a policy before one team’s override conflicts with another’s intent.
- Note that changes may take 1-2 days to take full effect, so plan around any time-sensitive content decisions.
The expansion of this notification is a small but concrete step toward making the generative AI control hierarchy more auditable. How organizations with complex site structures respond, particularly those balancing participation in AI features against content protection concerns, will be worth watching as the feature matures.
Sources: Search Engine Roundtable, Oct 6, 2026; Google Search Console Help, Search generative AI control
Lam Nguyen · Hingewise
This article was drafted with AI assistance from the sources cited above and checked against them before publishing. The "What this means for AI-search visibility" section is Hingewise's editorial analysis, built on the frameworks and positions we use in our GEO work. How we work: Editorial policy.