Google’s Search Generative AI Control (August 31, 2026): Why Michigan Sites Should Leave the Exclude Toggle Alone

On August 31, 2026, Google added one line to its Search Console documentation: “As of August 31, 2026, we’ve rolled out this control to all websites worldwide.” The control in question is the Search generative AI toggle, and it means every Michigan site owner can now remove their entire domain from AI Overviews, AI Mode, and generative AI features in Google Discover with two clicks.

Search Engine Land’s Barry Schwartz reported the rollout the same day, alongside the Generative AI performance report reaching every property. The report is useful. The toggle is a trap for most businesses, and the reason has less to do with AI than with what Google chose not to measure.

What is Google’s Search generative AI control?

It is a property-level setting in Search Console, found under Settings > Search generative AI, with three possible states: Include (the default for all properties), Exclude, and Inherit control from parent. It governs exactly three surfaces — AI Overviews, AI Mode, and generative AI features in Google Discover — and nothing else.

Google’s documentation says a change generally takes effect within 1–2 days, with some content lagging longer because of caching and propagation. There is no per-URL option: you are either in or out, for the whole property.

Why did Google ship a site-wide opt-out at all?

Industry coverage attributes the control to a UK Competition and Markets Authority conduct requirement imposed on Google in June 2026, with a further CMA deadline of March 2027 for Google to offer page-level controls. Google’s own help page does not mention the March 2027 date, so treat that timeline as reported rather than confirmed by Google.

That origin matters. A control built to satisfy a regulator gets built to the minimum specification that satisfies the regulator — property-level, binary, and shipped without the measurement that would let you use it well.

What does “Exclude” actually stop, and what does it leave running?

Exclude prevents two things: your site being linked inside those three AI surfaces, and your crawled content being used to ground the responses generated there. Google states plainly that excluded sites receive no traffic and no impressions from those features.

Four things it does not touch, per Google’s documentation:

• Your regular rankings. Google says the control “isn’t used as a ranking or inclusion signal affecting other parts of Search.”
• Merchant Center and Google Ads. The control explicitly does not override participation in those programs.
• Model training. Google directs you to the Google-Extended user agent in robots.txt for that. The toggle and the crawler control are separate levers with separate effects.
• General language understanding. Your content may still help Google’s systems understand queries and page language.

Here is the mechanism that decides whether this hurts you: excluding your site does not suppress the AI answer. It suppresses you. Google still writes the response and still fills the citation slots — from whoever is left. A Livonia industrial supplier that excludes its catalog does not stop AI Mode from answering “what thread sealant is rated for hydraulic fittings.” It hands that citation to a competitor’s spec page. Apply the rule anywhere and you can predict the result: exclusion only wins when the AI answer would have fully satisfied the user and no rival is waiting to take your slot.

How does the inherit setting spread an exclusion you never intended?

By default, a property inherits its control from its closest parent property that has stopped inheriting; if no parent was manually configured, it inherits from the top-level domain property. One person changing one setting can therefore silently move properties they do not manage.

Picture a Troy manufacturer. Marketing owns the domain property example.com. An agency owns the URL-prefix property https://example.com/resources/ and never touched the toggle. A manager reads a scare piece about AI Overviews and flips the domain property to Exclude. The entire resource library — the application notes Tier 2 buyers find at the start of an evaluation — leaves AI Mode within about two days, and nobody at the agency is notified.

The boundaries are also stricter than people expect. Per Google’s examples, https://www.example.com/ is not a parent of https://example.com/. Protocol and www variants are separate lineages, so a Sterling Heights site that set Exclude on one URL-prefix property and assumed the whole site followed has configured about half of it.

Should Michigan businesses set the control to Exclude?

For the overwhelming majority, no — and the strongest argument against it is Google’s own instructions. The help page tells you to use the Generative AI performance report “to get an idea of how changing your control may impact traffic to your site.” That report contains impressions, pages, countries, devices, and dates. It contains no clicks, no queries, and no CTR, and it is not exposed through the Search Console API — the searchanalytics.query method still accepts only web, image, video, news, googleNews, and discover.

Google is recommending you forecast a traffic change using a report that does not report traffic. You can learn a page drew 40,000 AI impressions in August and still not know whether that produced four sessions or four hundred. Shipping a decision tool without the decision data is not a neutral omission; it makes Include the only defensible default.

Who lands on each side? A publisher whose revenue is display impressions on article pages, and who can show AI summaries fully substitute for the article, has a real case. A Warren Tier 2 supplier does not: in a nine-month B2B cycle, the AI answer is where the early spec question gets asked, and being cited there is often the only moment you enter the consideration set. A Grand Rapids HVAC company still loses more than it saves, because “furnace not igniting” ends in a phone call, not a summary.

The asymmetry seals it. Excluding takes 1–2 days. Re-including means re-earning a grounding slot Google spent your absence filling with someone else’s page.

How should a three-person marketing team handle this week?

1. Audit the current state. Open Settings > Search generative AI on every property you own and record whether it reads Include, Exclude, or Inherit.
2. Map the property tree. List the domain property, both www and non-www URL-prefix properties, every subdomain, and every path property. Mark which are manually configured and which inherit. Getting this inventory straight is unglamorous, and it is the first thing we pull when a Michigan client hands us a Search Console account at ROSH Media.
3. Prune the owner list. Only property owners can change this setting. Remove departed employees and former agencies from the domain property today.
4. Export the Generative AI report by hand, monthly. With no API access, a manual CSV on the first of each month is the only baseline you will have going into Q4.
5. Cross-reference with GA4. Line the top AI-impression pages up against GA4 landing-page sessions for the same dates. Heavy impressions with flat sessions is a content problem; heavy impressions with rising sessions means the surface is working.
6. Fix the pages carrying the impressions. Put the direct answer in the first 40 words, keep spec and fitment tables in real HTML rather than images, and stop burying compatibility data in PDFs.
7. Separate the training question. If your objection is model training rather than answer surfaces, Google-Extended in robots.txt is the lever. The Search Console toggle will not do it.
8. Diary a March 2027 review. If page-level controls arrive on the reported CMA timeline, excluding a single pricing or login page becomes a sensible conversation. Excluding an entire domain mostly does not.

What dates should Michigan marketers put on the calendar?

• September 1–30, 2026: Google begins automatically upgrading Search campaigns that use campaign-level broad match or standalone automatically created assets to AI Max, rolling gradually through the month.
• September 11, 2026: One full month of Generative AI performance data exists for every property, since the report finished rolling out on August 11.
• October–December 2026: Retail peak. Any exclusion set now is an exclusion set through your highest-intent quarter.
• February 2027: Reported start of the Dynamic Search Ads auto-upgrade to AI Max, extended from earlier guidance.
• March 2027: The reported CMA deadline for page-level generative AI controls. Not confirmed in Google’s documentation.

Frequently asked questions

Does excluding my site from AI Overviews hurt my regular Google rankings?

Google says no. Its documentation states the control “isn’t used as a ranking or inclusion signal affecting other parts of Search.” Your blue links should be unaffected. What you lose is every impression and click from AI Overviews, AI Mode, and generative AI features in Discover — which for many Michigan sites is now a meaningful share of first contact with a buyer.

Does this toggle stop Google from training AI models on my content?

No. Google’s help page is explicit that the control “doesn’t affect AI training” and points to the Google-Extended user agent in robots.txt for that purpose. These are two independent decisions. You can allow grounding while blocking training, or the reverse, and most businesses should think about them separately rather than as one AI switch.

Can I exclude a single page instead of my whole site?

Not through this control today. It operates at property level only. You can approximate page-level scoping by verifying a narrower URL-prefix property — for example https://example.com/pricing/ — and configuring that property to stop inheriting. Reported CMA timelines put genuine per-URL controls in March 2027, but Google has not published that date itself.

Why doesn’t the Generative AI performance report show clicks?

Google has not published a reason, and has said only that more metrics may come without committing to a timeline. Practically, it means the report shows visibility but not value. Pair it with GA4 landing-page data and call tracking — the approach we use when auditing AI search visibility for Ann Arbor and metro Detroit clients at ROSH Media — rather than treating impressions as outcomes.

Google gave every website a switch on August 31, 2026 without the meter that would tell you whether to throw it. Audit the property tree, lock down who can change the setting, export the impression data monthly, and leave the toggle on Include until March 2027.