Search Generative AI Control: Do Not Switch It Off Blind

Google's Search generative AI control is a Search Console setting that decides whether your site can appear in AI Overviews, AI Mode and generative AI features in Google Discover. Google rolled it out to all websites worldwide on August 31, 2026, and the default on every property is Include. Set it to Exclude and your links and content are prevented from appearing in those features, and Google states you will not receive any traffic or impressions from them.

Every founder I have shown this setting to reaches for Exclude inside about four seconds. Do not. It is the most expensive click in Search Console right now, and the report Google points you at before you decide cannot answer the only question that matters.

What the control actually does

You find it under Settings, then Search generative AI. It takes three values: Include, which is the default for every property, Exclude, and Inherit control from parent.

Three things it is not, because these get run together in almost every thread I read:

• It is not a training opt out. Google says the control does not affect AI training. Google-Extended is the crawler that governs training and grounding in Google's other systems.
• It is not a ranking signal. Google states the control is not used as a ranking or inclusion signal affecting other parts of Search.
• It is not a way out of Google. To keep your content out of Google Search completely, that is still noindex.

One more thing it is not: well documented. Google's AI features guide for site owners, last updated in December 2025, still tells you the controls are robots.txt for Googlebot plus nosnippet, data-nosnippet, max-snippet and noindex. It does not mention this setting at all. The help centre shipped a switch the developer documentation has not caught up with.

The mistake: treating this as the block AI button

The mistake is reading Exclude as a privacy control. It is a distribution control. It does not protect your content from being learned from, and it does not stop Google crawling you. It decides exactly one thing: whether Google may put your name and your link inside the answer somebody is already reading.

I have watched an AI answer send me a paying client. A founder found imisofts because an assistant named us in a reply, then booked a call. That is the exact surface this switch turns off. Paying that price to protect content Google will keep crawling anyway is a bad trade.

The setting travels down your properties by default

Here is the part almost nobody is discussing, and the part that will cause the first real accident.

The control inherits. A property follows the value of its closest parent property that has stopped inheriting, and when no parent has been configured, it follows the top level domain property. Change the parent and the change applies to the children automatically.

So if your domain property is example.com and you also verified blog.example.com and a URL prefix property for the shop, one person setting Exclude on the domain property sets it on all of them. There is no second confirmation on each child. You can override any child by opening that property and configuring it manually, but you have to know to look.

Google says a change generally takes a few days, with content excluded within 1 to 2 days of the control going live and some content taking longer because of caching and propagation. The accident is quiet, and it is quick.

The report Google tells you to read counts impressions only

Google's page on the control tells you to use the Generative AI performance report to, in its words, get an idea of how changing your control may impact traffic to your site.

Then read what that report contains. Impressions. The dimensions are pages, countries, dates and devices. There is no query dimension and there is no click column.

So the instrument Google hands you to price the decision measures the one number that is not revenue. You can prove you were shown. You cannot prove you were clicked, and you will never see which question you answered. Anyone selling you an AI Overviews ranking report built on Search Console data is selling you impressions with a confident voice over the top.

A few more limits before you build a dashboard on it. The Search report covers AI Overviews and AI Mode, Discover has its own separate report, Search Labs experiments are excluded, and the data comes from the Web search type with the same 1,000 row limit as the rest of the performance report.

Four moves to make in Search Console this week

The part that should worry agencies

If you run an agency, that inheritance default is a support ticket with a two day fuse. A client's developer sets Exclude at the domain level to keep our content out of AI, and every property you report on goes dark in the generative features while the classic performance report barely moves, because the control is not a ranking signal. Impressions fall in a place most agencies are not looking yet, and nobody connects it to a setting somebody flipped on a Tuesday.

I have built this kind of infrastructure for 500+ businesses and the pattern never changes. The damage is not the toggle. It is the six weeks before anyone notices the toggle.

The bottom line

Include is the default because being included is almost always the right answer. If you sell something, an answer that names you and links you is distribution you did not have to buy.

There are real reasons to exclude. If your writing is your paid product, or a contract forbids it, exclude and take the hit knowingly. What you should not do is flip it because AI feels like something to defend against, on a property that quietly carries three others with it, using a report that will never show you what it cost.

Check the setting. Export the report. Then get back to the work that gets you named in the answer. If you want a second pair of eyes on your setup, book a 30 minute call at cal.com/zeeshanwaheed/30min or email [email protected].