Google AI search control clarity
On October 21, Google updated its Search Central documentation to consolidate something that has confused site owners for two years: exactly which controls govern whether your content shows up in Google’s AI search features and how those controls differ from the ones for traditional indexing and AI training.
The short version: these are separate switches, they do separate things and flipping one does not do the job of another. If your GEO strategy assumes otherwise, it’s built on a misunderstanding.
The four controls, and what each one actually does
| Control Name | Primary Mechanism | Where to Manage |
| 1. Indexing Controls | noindex meta tags, robots.txt |
Server-side (robots.txt) / On-page HTML header |
| 2. Presentation Controls | data-nosnippet, robots meta tags |
On-page HTML header / Element attributes |
| 3. Search Generative AI Control | Search Console UI toggle | Google Search Console (Settings > Search generative AI) |
| 4. Google-Extended | robots.txt user-agent directive |
Server-side (robots.txt) |
1. Indexing controls: noindex, robots.txt
These are the classics. noindex governs whether a page can appear in Google Search at all; robots.txt governs whether Google can crawl the page in the first place. Neither says anything specific about AI features.
2. Presentation controls: robots meta tags, X-Robots-Tag, data-nosnippet
These govern how your content is presented in search results, whether a snippet can be shown, and whether specific sections of a page can be excluded from snippets using data-nosnippet.
3. Google’s Search generative AI control: Search Console
This is the AI-specific switch, and the one the updated documentation clarifies. You’ll find it under Settings, then Search generative AI, in Search Console. It rolled out worldwide by August 31, and it lets site owners manage whether their content appears in AI Overviews, AI Mode, and specified generative AI features in Google Discover. Inclusion is the default, even if you’ve never touched this setting, your content is in.
4. Google-Extended: AI training
Training is a separate mechanism. The Search Console control above does not govern whether Google can use your content to train its AI models. That’s Google-Extended’s job, and conflating the two is the most common mistake in this area.
What opting out of generative AI search actually does
Google documents the consequences of excluding a site from its generative AI search features plainly:
- Your content and links will not appear in the affected AI features.
- You will not receive impressions or traffic from those features.
- The exclusion does not act as a ranking signal anywhere else in Google Search, opting out of AI Overviews does not hurt (or help) your traditional organic rankings.
- It isn’t instant: Google says a change generally takes a few days to take effect: most content is excluded within 1–2 days of the change going live, and some can take longer because of caching.
That last point about rankings matters. For a while, a reasonable fear kept publishers from touching these settings: if I opt out of the AI features, will Google hold it against me in regular search? Google’s answer, now in writing, is no.
So should you opt out?
That depends on your business model, and anyone who gives you a blanket answer hasn’t thought it through.
A publisher monetizing reach and referral traffic may want its content cited in AI answers. Those citations are visibility, and increasingly, traffic. A publisher whose value sits in proprietary content may weigh the commercial and intellectual-property side differently. Neither answer is wrong; what’s wrong is not knowing the setting exists, or having it set by accident.
There’s also a governance question hiding in this: who in your organization decides whether your content appears in AI search experiences? For most businesses, nobody has ever explicitly decided. The default decided for them.
What we’d do first
Before changing anything, audit:
- Document the current configuration of the Search generative AI control on every Search Console property you own or manage, including properties that inherit the setting from a parent property, where the inherited value is the one that actually applies.
- Establish a baseline: AI-related impressions, clicks and conversions, so a change, if you make one, is measurable instead of vibes. Search Console’s Generative AI performance report is the tool Google provides for the impressions side of that baseline.
- Assess reliance on Google Search per property. The right answer for a content publisher and a local services business are rarely the same.
- Keep the controls straight. The Search generative AI control, noindex, robots.txt and Google-Extended are four tools for four jobs. Audit them separately.
What we’re watching
- Whether Google adds more granular controls, either by content type or by individual feature.
- Whether Search Console reporting gets better at isolating the traffic effects of inclusion decisions.
- Whether other AI platforms introduce comparable controls.
- Whether shifts in AI visibility start mapping to measurable business outcomes.
Google has now put the map of switches in one place. The work is deciding, property by property, which position each switch should be in, and being able to show your numbers before and after.
Jtree works on exactly this: SEO and GEO strategy grounded in what’s actually driving traffic. If you’re not sure how your properties are configured, that’s the first thing to fix.