Google's AI Search control leaves ordinary Search eligible, but property scope matters

Google's October 21, 2026 update to its content-control documentation lists the Search generative AI control as site-wide. It lets publishers manage inclusion in AI Overviews and AI Mode without using an indexing-removal rule. There is an important qualification: the detailed Search Console help allows child properties to override their parent.

This is a documentation update, not evidence of an October launch. Google's change log describes the addition of existing controls to the page. For a publisher, the useful distinction is between choosing where content appears and withdrawing it from Search altogether.

Check the property behind the setting

The Search Console instructions say the control reached websites worldwide by August 31, 2026. It sits under Settings, then Search generative AI. Its scope includes AI Overviews, AI Mode and generative AI features in Discover.

Exclusion removes a site's links and content from those features, including use as input to ground their responses. Google says the setting does not determine ranking or inclusion elsewhere in Search. Ordinary search eligibility therefore remains subject to the usual rules; keeping it does not guarantee that every page will be indexed or rank.

The overview's site-wide label should not be read as an absolute ban on narrower configurations. Child properties inherit a parent's choice by default, but their owners can set a different choice for that property and its subpages. This is a Search Console property control, not a new per-page robots directive. Check the actual property and any overrides before assuming one change covers every section.

Choose the control that matches the problem

A page that must disappear from Google Search needs a different decision. The overview describes deleting content, protecting it with a password or using noindex. Password protection also restricts access to the content itself; search exclusion alone does not make a public page private. ClickSyrup's URL-removal guide separates those purposes.

For presentation choices, Google's robots documentation covers page-level settings, the X-Robots-Tag response header and the data-nosnippet attribute for selected text. The overview also describes blocking image and video crawling with robots.txt. These mechanisms have different scopes, so they are not interchangeable switches.

Separate opt-outs remain for properties such as Google Shopping, Google Hotels and vacation rentals. The Search AI setting also does not control AI training, according to its help page. A decision about visible AI results should therefore not be recorded internally as a decision about every Google use of the content.

Record the decision before measuring the result

Google says excluded sites will not receive impressions or traffic from the covered generative features. That is a consequence of removal, not a forecast of the change in total visits or revenue. Neither the documentation update nor its change log establishes that opting out increases ordinary search traffic.

Before changing the control, write down the property, the current setting, any inherited choice and the business reason for changing it. Afterward, confirm the saved configuration and allow for propagation rather than treating an immediate search as a definitive test. If several people manage related properties, assign responsibility for checking overrides.

The decision also belongs beside the wider question of AI Search links and publisher traffic. A publisher can choose exclusion, inclusion or a narrower property configuration. The useful result is a deliberate choice whose scope is understood, followed by measurement without assuming causation.