Google lets publishers opt out of generative AI answers in Search

Google has announced a Search Console control allowing site owners to decide whether their pages can appear in and ground generative Search experiences. The setting covers AI Overviews, AI Mode and AI summaries in Discover.

The short answer

Google updated its announcement on August 31. Publishers should wait until the control is actually available in their Search Console property before changing strategy.

Visibility versus control

Appearing in an AI answer can expose a brand and generate qualified visits when citations are prominent. A sufficiently complete answer may also satisfy the user without a click. The impact differs for an ecommerce site, an advertising-funded publication and an institutional resource.

The choice should therefore rely on impressions, clicks, conversions and query trends rather than a uniform position for the entire domain.

Do not confuse controls

robots.txt, noindex, snippet directives and this new setting do not necessarily have the same scope. Blocking crawling can remove a page from classic search when the actual goal is only to refuse its use in a generative answer.

Document the exact scope before changing anything and test on a limited section. A mistaken domain-wide rule can lose more traffic than it protects.

Measure before and after

Export a four-to-eight-week baseline for queries, landing pages, click-through rate and conversions. Separate informational, comparison and transactional content. After activation, monitor branded queries and direct signups too.

Results may shift as Google's interface changes. A one-time reading is insufficient; include the decision in quarterly SEO reviews.

An editorial decision, not just a technical one

Copyright, contributor agreements and the business model should inform policy. Free public documentation and subscriber-funded investigative work do not derive the same value from exposure.

The control finally gives publishers a more explicit choice. The best response will probably be neither allow everything nor block everything, but testing by content type and judging value beyond raw click volume.