Google Adds Property-Override Alert to AI Controls

Google updated its Search Console help documentation for the Generative AI Control page. A new notification now alerts top-level domain property owners when a child property's setting differs from the parent's, Search Engine Roundtable reported on October 6.

This setting lets a site owner allow or block their content from being used in Google Search's generative AI features, such as AI Overviews. It recently expanded to sites worldwide.

Google's documentation states that owners of the top-level domain property will see a notification on the Generative AI Control page when one of their child properties overrides the parent setting. That explanation appears in Search Console help article 16908024.

The trouble is that the more subdomains or subdirectories a site runs, the more this setting gets applied separately by property. That makes it easy to assume the whole domain is blocked while one specific child property quietly differs.

A blog subdomain might be blocked while a shop subdomain stays on the default "allow." This new alert surfaces exactly that kind of mismatch in one place inside Search Console.

The underlying control itself isn't new. The ability to set generative AI exposure site-wide or by folder already existed, and this update is closer to a safeguard that flags when those settings conflict within a property's hierarchy.

Property structures get complicated because Search Console treats a whole domain, each subdomain, and each subdirectory as a separate property. In larger organizations, different teams often manage different properties, so a mismatched setting can go unnoticed for a while.

Google also expanded its generative AI performance report to sites worldwide back on August 31, and this alert sits on that same track. Google is refining two related capabilities inside Search Console at once: showing how much AI draws on a site's content, and letting owners define how much of that content AI can use.

Until now, the blocking control existed but there was no easy way to confirm it was applied correctly everywhere. This alert fills that gap.

There's no word yet on exactly when the notification rolls out to all accounts.

In Korea

Korean sites running a blog, a shop, and a help center on separate subdomains should check this in Search Console. Even if the generative AI exposure setting seemed unified across the whole domain, a child property could still be applying something different.

Source: Search Engine Roundtable, October 6, 2026. Checked October 7, 2026. Read the original