What To Check Before Changing Google’s AI Search Control

Before changing participation in Google AI Overviews or AI Mode, open the exact Search Console property, inspect its effective Include, Exclude or Inherit status, identify the configured parent, confirm the intended URL scope, and record the current setting and time. That sequence matters because a domain property and a URL-prefix property can govern different parts of a site.

This guidance is for site owners, developers and SEOs responsible for Search Console settings. The most important exception is that the Search generative AI control is not a substitute for noindex, robots.txt, Google-Extended, Google Ads or Merchant Center settings. It controls eligibility for specified generative AI features, not every way Google can crawl, index or use a page.

What the Search generative AI control changes

Google says the Search generative AI control became available for all websites worldwide on August 31, 2026. In Search Console, open Settings > Search generative AI. The setting applies to AI Overviews, AI Mode and generative AI features in Google Discover; Google notes that the feature list can change over time. See Search Console Help: Search generative AI control.

The available choices are:

Include: allow the property to participate in the specified generative AI features, subject to Google’s systems and feature eligibility. Inclusion does not promise an appearance, impression, click, citation or business result.
Exclude: prevent the site’s links and content from appearing in the specified features and prevent crawled content from being eligible as input for generating an AI response or preview in those features.
Inherit: use the setting from the applicable parent property.

Google describes this control as separate from ordinary Search ranking and inclusion. Excluding a property does not, according to the documentation, deindex its pages, change ordinary rankings or block Googlebot. It also does not control AI training. Those distinctions should shape both the decision and the verification plan.

1. Select the property that should govern the change

Start with the property selector in Search Console, not a bookmarked settings page. Confirm whether you selected:

A domain property, which represents the verified domain across protocols, subdomains and paths included by that property.
A URL-prefix property, which covers URLs beginning with the specified protocol, host and path prefix, such as https://example.com/resources/.

Then write down the intended scope in plain language: “the entire domain,” “the main HTTPS site,” “the resources section,” or another precise boundary. If the intended change is only for a section, changing a domain-level property may affect more URLs than intended.

Before editing, record:

the property name and property type;
the displayed Search generative AI status;
the date and time, including time zone;
the business reason for the change; and
any related configuration change that is deliberately being made at the same time.

2. Trace inheritance before choosing a setting

A property with a parent normally inherits the closest parent setting that has been manually configured to stop inheriting. If no parent has done that, the child can inherit from the top-level domain property. A child property owner can manually override the parent for that property and its subpages.

Do not assume that the status displayed on a child property tells you the domain’s policy. “Inherit” means the effective behavior comes from elsewhere in the property hierarchy. Identify the parent and inspect its setting before changing anything.

Hypothetical example: the domain and `/resources/`

Hypothetical example: A business has a domain property for example.com set to Include. It also has a URL-prefix property for https://example.com/resources/, which currently shows Inherit.

The owner has two materially different choices:

Change the domain property: change the policy for the domain-level scope. The resources property may then inherit the new effective setting unless it has its own manual override.
Override the resources property: select the URL-prefix property, change it from Inherit to the intended setting, and leave the domain-level policy and unrelated sections unchanged.

The second option is appropriate when the decision genuinely applies only to the resources section. The first is appropriate when the business has made a domain-wide policy decision. This is a governance choice, not a ranking tactic.

3. Keep neighboring controls separate

Several controls can appear related because they all affect how Google handles content. They do not serve the same purpose.

Control	Primary purpose	Scope or access condition	Expected Search effect
Search generative AI control	Include or exclude content from specified Google generative AI features	Configured in Search Console at the property level, with inheritance and child-property overrides	Changes eligibility for those generative AI features; it is not documented as a general indexing or ranking control
`noindex`	Tell Google not to index a page	Applied at page level, such as with a meta robots tag or HTTP header; Googlebot must be able to access the rule	Can prevent the page from appearing in Google Search after Google processes the directive
`robots.txt`	Control crawler access to URL paths	Applied by user agent and URL path in the robots.txt file	Controls crawling behavior; it is not the Search generative AI participation setting
Google-Extended	Control certain uses related to future Gemini model training and grounding	Configured separately from the Search generative AI control	Does not serve as an opt-out from AI Overviews or AI Mode and is not a general Search-indexing control

Google’s Search Central guidance on noindex explains the page-indexing directive and the requirement that Google can crawl the page to see it. The overview of Google crawlers and fetchers and list of common Google crawlers provide the relevant context for crawler-specific behavior. Use the control that matches the problem you are trying to solve.

4. Apply and document only the intended change

Select the exact domain or URL-prefix property.
Open Settings > Search generative AI.
Review whether the displayed state is Include, Exclude or Inherit.
If it is Inherit, identify the parent supplying the effective policy.
Change only the property whose URL scope matches the decision.
Save the setting and capture the resulting displayed status.
Record the timestamp, property, previous state, new state and reason in the site’s change log.

Avoid making unrelated changes to noindex, robots.txt, canonical tags, templates or tracking at the same time if you want a clean before-and-after comparison. Multiple changes make later reporting harder to interpret.

Google says that after a control change goes live, content will be excluded within 1–2 days, while caching and propagation across Google systems can make some content take longer. Treat that as an expected window, not a universal completion deadline for every URL or system.

5. Verify the setting without overreading the data

After the propagation window, use this sequence:

Reopen the control page. Confirm the selected property still shows the intended state.
Check the hierarchy. For a child property, confirm whether it is still inheriting or has a manual override. Check the parent if the effective state is unexpected.
Allow for reporting delay. Do not use same-day movement as confirmation that the change worked.
Open the generative AI performance report if it is available. The report covers AI Overviews and AI Mode impressions in Search. Discover data is handled separately.
Use stable comparisons. Keep the date range, country, device and page grouping consistent. Compare canonical URLs rather than assuming duplicate URL variants represent separate page performance.
Check whether recent chart data is preliminary. Google says the newest data can change over the next few hours.

The Search Console Help: Generative AI performance report explains the report’s dimensions, canonical URL assignment and preliminary data. It also says the report may be unavailable when a property has not received enough generative AI impressions or while access is still rolling out. A missing report alone is not proof that the property is excluded.

For additional comparisons, remember that Search Console can aggregate data differently at the property and page levels. The Search Console Performance report documentation describes why chart and table totals may differ. Keep the comparison boundaries consistent before treating a change as meaningful.

Verification example: ordinary Search impressions continue

Hypothetical example: An owner changes the https://example.com/resources/ URL-prefix property from Inherit to Exclude. Two days later, the owner still sees ordinary Google Search impressions for pages in that section.

That result is compatible with the documented scope. The Search generative AI control governs eligibility for specified generative AI features; it does not state that excluded content disappears from ordinary Google Search. The owner should recheck the child-property status and hierarchy, then use the generative AI report if available. Continued ordinary Search impressions are not evidence that the control failed.

Conversely, a decline in generative AI impressions after the change should not be treated as conclusive proof based on a same-day chart movement. Reporting lag, preliminary data, date selection, canonicalization, country, device, query demand and other Search conditions can affect what the report shows. Google does not document a separate report that provides an exact per-URL timestamp for when eligibility ended.

Change checklist

Correct Search Console property selected.
Domain property or URL-prefix scope confirmed.
Current Include, Exclude or Inherit status recorded.
Closest configured parent identified.
Decision made between domain-wide policy and child-property override.
Search generative AI control kept separate from noindex, robots.txt and Google-Extended.
Timestamp, previous state, new state and reason added to the change log.
Documented 1–2-day exclusion expectation allowed to pass before interpreting results.
Control page and property hierarchy rechecked.
Performance data compared with consistent dates, country, device, page grouping and canonical URLs.
Preliminary data and report availability limitations considered.

The defensible question is not simply “Did AI traffic change?” It is “Did the intended Search Console property receive the intended policy, and am I comparing the right data for that scope?”

Have you found an inheritance or URL-prefix scope issue while managing Search Console settings? Share the configuration pattern—not confidential site data—so other site owners can learn from it.

Sources

Editorial note: AI assists with research, drafting and automated checks. Sources are linked so you can verify the guidance. Platform requirements can change; confirm the details that apply to your setup.