Anyone who owns a Search Console property can pull your pages out of Google's AI answers. Check who that is
Google's switch for keeping a site out of AI Overviews and AI Mode isn't just for the person who owns the domain. An old agency login on a subfolder property can flip it for that section, and you'd only see a notice.
Since August 31, 2026, every site can use the Search generative AI control in Search Console to include or exclude its content from Google's generative AI features. Child properties inherit the setting from their closest configured parent, but any owner of a child property can override it for that section, and the top-level owner only sees a notification. Before debating whether to opt out, list who owns which properties, agree who decides, and measure the traffic first.
The switch has more owners than you think
Since August 31, 2026, every website can tell Google to keep its pages out of the generative AI features in Search, such as AI Overviews and AI Mode. The setting lives in Search Console under Settings, and it has three positions: include your content (the default), exclude it, or follow whatever the parent property decided.
Most of the debate so far has been about whether to opt out. That's a real question, but it's the second one. The first is simpler: who in your organization can flip this switch today, and would anyone notice if they did?
Search Console doesn't think of your website as one thing. It thinks in properties. There's usually a domain property for the whole site, and often a handful of others underneath it: a URL-prefix property for the blog that an agency set up three years ago, one for the help center, one for a regional folder. Each has its own owners, and the list rarely gets cleaned up when people or agencies move on.
Google's help page is clear about what that means for this control. A child property inherits the setting from its closest parent that has one configured, and falls back to the top-level domain property otherwise. But the owners of a child property can override it for that section and everything under it. The owners of the top-level domain property get a notification on the control page when that happens. That's the safeguard: a notice, for whoever happens to open that page.
How the work moves
How a section ends up with its setting
- Child property
For example, a blog folder or help center property.
- Has its own setting?
Then it uses that, whatever the parent says.
- Closest configured parent
Otherwise it follows the nearest parent with a setting.
- Top-level domain
If none is configured, it follows the domain property.
- Notice
Top-level owners see a notification when a child overrides.
Why that matters more than the opt-out debate
Picture a common setup, offered here as an example rather than a real case. The marketing team owns the domain property. A content agency still has owner access to the blog's URL-prefix property from an old engagement. A former contractor has owner access to the help center property because they set up its sitemap.
Any of them could exclude their section from AI answers. Maybe on purpose, after reading an opinion piece about AI scraping. Maybe by accident, clicking through settings they don't recognize. Google says exclusion generally takes effect within a few days. Your help articles would stop appearing as links in AI answers to "how do I reset my device" questions, and content from other sites could fill that space instead.
Nobody would have decided anything. A property owner would simply have used a setting they were allowed to use. The question isn't whether to opt out. It's who in your organization gets to decide.
The question isn't whether to opt out. It's who in your organization gets to decide.
What the control does and doesn't do
Before anyone flips it, it's worth knowing the edges, all from Google's documentation.
Excluding removes your links and content from those features. You get no impressions or traffic from them, and your pages aren't used to ground the AI responses there. It doesn't affect your rankings elsewhere in Search, since Google says the control isn't a ranking signal. It doesn't override your Merchant Center or Google Ads choices. And it doesn't control AI training. That's a separate setting, Google-Extended, in robots.txt.
So the control isn't a privacy switch or a protest button. It's a traffic decision about one set of surfaces. Sometimes that decision is right. A publisher whose business depends on the click may reasonably decide AI answers take more than they give. A store or service business that wants to be named when someone asks Google's AI which vendor to call will usually decide the opposite.
Decision guide
Include or exclude?
| Consideration | Lean toward include | Exclude might make sense |
|---|---|---|
| Store or service business | You want to be named when buyers ask AI who to call. | Revenue depends on readers clicking through. |
| Help center | Customers find answers from your own pages. | Members-only knowledge you don't want summarized. |
| AI training worry | This control doesn't cover training. | Use Google-Extended for that instead. |
| Unclear traffic | Measure first; changes take days to apply. | Measured loss with little visibility gain. |
What to do this week
List the owners. Open each property in Search Console and list everyone with owner access. Remove people who left, agencies you no longer work with and test accounts. This is basic housekeeping that's been overdue at most companies for years. Now it carries a specific consequence.
Decide who decides. Pick one person or role who signs off on this setting for every property, and write it down where the web team will find it. If your site has sections owned by different teams, say whether they're allowed to differ from the main setting. Some should. A members-only knowledge base might want out while the marketing pages stay in.
Measure before you change anything. Google points to its performance reporting for these features in Search Console. Look at how often your pages appear in AI features, and compare that with your normal search traffic for the same pages. If someone wants to exclude a section, they should bring that comparison to the decision. And if someone already did, the notification on the top-level property's control page will say so.
Check the inherit setting on every child property. Open each one and confirm it says it's following its parent. If a child shows its own setting, find out who set it and why before changing it back. There may be a good reason, such as a section you agreed to keep out. There may also be no reason at all. Either way, write the answer down next to the owner list so the next person doesn't have to work it out again.
Tell the people who report on traffic. If the setting changes for any section, the marketing and analytics team should know the date. Otherwise a drop in visits from Google a week later gets blamed on an algorithm update, a redesign or the season, and the team spends a month chasing the wrong cause.
Where this goes next
Google's own help page says it expects to update the list of covered features over time, and its Search Central guidance on controlling what you share was updated again on October 21. Settings like this tend to multiply. If each new one becomes something any property owner can change for their section, the governance question will keep coming back.
The fix doesn't need new tools. Treat Search Console ownership like domain registrar access or the keys to your DNS. Keep a short list of owners, review it quarterly, and add one line to your offboarding checklist when an agency or employee leaves.
If your site has grown into a tangle of properties, subdomains and sections nobody owns, sorting out the structure and access is part of what our web applications team does. Talk to us.
Related work: Sutton Place.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.