Which Google AI Search Control Should Your WordPress Site Use?

Choose the Google Search control that matches your intended scope: use Search Console’s Search generative AI control for site-wide inclusion in the listed generative AI features, page- or text-level controls to adjust a particular preview, and noindex only when you want content kept out of Google Search more broadly. For WordPress site operators, excluding a site from generative AI features is not the same as removing its pages from ordinary Search.

What did Google clarify in October?

Google’s October 21, 2026, update-log entry says it updated its Control what you share with Google Search documentation to include existing options—including robots meta, data-nosnippet, X-Robots-Tag, and the Search generative AI control—along with minor clarifications to keep the page current. The Google Search Central documentation update log describes a documentation update, not a newly launched control or a change to Search behavior.

Match the control to the outcome

Your goal	Control to consider	Scope to keep in mind
Exclude the site from Google’s listed generative AI features	Search generative AI control in Search Console	Site-wide. Google says this control manages inclusion in Search generative AI features, including AI Overviews and AI Mode. Its Search Console Help page also lists generative AI features in Google Discover.
Adjust a page or particular text preview	Robots meta, `data-nosnippet`, or `X-Robots-Tag`	Page- or text-level controls for adjusting how content is presented in Search. The right implementation depends on the site and the content you want to affect.
Keep content out of Google Search more broadly	`noindex`	Broader than a preview adjustment: Google says `noindex` tells it not to index the content or show it in Search results.

Google says the Search generative AI control is managed in Search Console. Properties without an inherited setting default to inclusion. Excluding a site from these generative AI features is not a ranking or inclusion signal affecting other parts of Search; it does not, by itself, remove pages from ordinary Search. Google identifies noindex as the option for keeping content out of Google Search more broadly. See Search Console Help: Search generative AI control and Google Search Central’s Control what you share with Google Search for these scope distinctions.

Example: limit a policy-page preview, not Search eligibility

Hypothetical: A WordPress store wants a policy page to remain eligible for ordinary Google Search but wants to limit a particular passage’s use in a Search preview. That is a page- or text-level preview question, not a request to remove the page from Search. The store could assess a control such as data-nosnippet for the text it wants to exclude from snippets. Implementation depends on how its WordPress theme, plugins, and page output are configured. Applying noindex instead would be broader: it tells Google not to index the page or show it in Search results. Neither choice guarantees a particular display.

Google’s AI features and your website guide says pages must be indexed and eligible to appear with a snippet to be eligible as supporting links in AI Overviews or AI Mode. Meeting those requirements does not guarantee crawling, indexing, or serving. Choose a preview control for the presentation scope you intend; do not treat it as a way to guarantee or prevent a specific AI result.

Check the site-wide setting in Search Console

Open Search Console and select the property you intend to manage. Confirm that it represents the correct site and scope before changing a setting.
Open the Search generative AI control for that property. Inspect whether it is set to include or exclude the site from the listed features.
Check whether the setting is inherited from a parent property. According to Search Console Help, a property without its own or an inherited setting defaults to inclusion.
Record the property, displayed setting, and inheritance status so you can distinguish the site-wide decision from any page-level implementation.

This is the check for the site-wide control. URL Inspection does not verify that Search Console setting.

Check a page-level control in URL Inspection

For a page- or text-level preview control, inspect the page in Search Console’s URL Inspection tool and examine the HTML Googlebot received when it crawled the page. Look for the intended directive in that crawled HTML. If it is missing or differs from your intended output, check the WordPress configuration that generates the page—such as the relevant theme, plugin, or server response—and inspect again after the correction is available to Googlebot. Google’s AI features and your website guide describes URL Inspection as a way to check Googlebot-received HTML; it does not make the tool a check for the site-wide generative AI setting.

Google says recrawling and processing changes can take from several days to several months. The crawled HTML can help confirm what Googlebot received, but it does not guarantee a particular Search preview or AI feature display.

Monitor the result without overreading the report

Search Console’s Generative AI performance report covers impressions for AI Overviews and AI Mode and provides available date and page dimensions for reviewing reported activity. Google says the report may be absent because the site has insufficient impressions or because it is excluded. A missing report does not tell you which explanation applies, and an impression change after changing a setting does not, by itself, show that the setting caused the change. Treat the report as a way to review reported impressions, not as proof that a control produced a particular outcome.

Verification checklist

State the intended scope: site-wide generative AI feature inclusion, a page or text preview, or exclusion from Google Search more broadly.
For a site-wide decision, select the intended Search Console property and inspect its Search generative AI setting and any parent-property inheritance.
For a page-level decision, use URL Inspection to check the HTML Googlebot received for the intended control. Do not use it to verify the site-wide setting.
Allow for recrawling and processing, which Google says can take several days to several months.
Review the generative AI performance report if available, but do not treat its absence or an impression change as proof of cause.

WordPress implementation depends on how the particular site produces its HTML and headers; Google’s documentation does not establish one plugin setting that controls these options across all WordPress sites. If you want help mapping the intended scope to your site’s configuration, Splinternet Marketing’s AI search optimization service can help implement and verify relevant controls and monitor available reporting. Brian Bateman’s managed service draws on 30 years of experience and is $421 per month per business, month to month, cancel at any time.

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.