Google Search Console Generative AI Report & AI Controls (2026 Guide)

For the first time, GEO measurement moved out of third-party dashboards and into Google's own console. Through August 2026, Google rolled the Generative AI performance report and generative AI controls out broadly in Search Console — letting site owners both see how often their content appears inside AI Overviews and AI Mode, and decide whether Google may use it to ground AI answers at all. If you optimize for AI search, this is now the first surface you should check every week.

"I expect [Google] will evolve over time, search / AI Mode / AI Overviews evolve too, there are edge-cases; the goal is not a written-in-stone absolute truth for position counting (that's impossible), but rather to make something that's useful for site owners in terms of understanding how their site is shown. We'll update the documentation when / if there are significant changes."

The shift is bigger than a new tab. For two years, GEO practitioners measured AI visibility with proxies — scraping ChatGPT answers, buying brand-mention tools, guessing from referral logs. Now Google exposes owned-domain AI impressions natively, and simultaneously hands publishers an opt-out that the UK's CMA forced into being. Below is what changed, what the numbers mean, and how to act on them.

The Generative AI performance report: what it actually shows

The report appears under the "Search results" menu in Search Console once Google has enabled it for your property (rollout accelerated through July–August 2026). It reports how your site is discovered and displayed inside Google's generative surfaces:

Source: Google Search Central — Generative AI performance report documentation; ROI Revolution "August 2026 SEO & GEO News Recap."

The honest limitation: this report measures appearance, not attention. Because Google withholds click and query data, a page can show a large AI impression count while sending almost no referral traffic — the zero-click reality of AI answers. Use the report to confirm eligibility and spot which pages Google thinks are citable, then triangulate real impact with off-site tracking.

What changed on 7 September 2026: AI Mode impressions are folded in

The single biggest reporting change since launch is quiet and easy to miss. According to Google's Search Console documentation as of 7 September 2026, AI Mode impressions are no longer broken out separately — they are combined with AI Overview impressions in one generative AI figure. If you built a dashboard in August that split the two surfaces, that split stopped working.

• ▸ What you lose. Surface-level attribution. You can no longer say "AI Mode drove X% of our generative impressions" from first-party data alone; you need third-party prompt panels to separate them.
• ▸ What you gain. Prompt filtering. AI Mode rows accept a user-prompt filter, letting you inspect which questions triggered your inclusion — currently the only query-shaped signal Google exposes for generative surfaces.
• ▸ Why it is structurally sensible. AI Mode and AI Overviews draw on the same Google Search index rather than a separate AI index, so a single combined counter matches how Google says the systems work.
• ▸ What comes next. The UK Competition and Markets Authority has set Google a March 2027 deadline to ship page-level AI controls and proper click reporting. Today's property-wide toggle is a first iteration, not the end state.

Practical handling: annotate any generative-AI reporting you hand to stakeholders with "AI Overviews + AI Mode combined" from 7 September onward, and keep a manual AI Mode prompt sample so you retain some surface-level context the console no longer provides.

The generative AI controls: opt in, opt out, or inherit

Running in parallel with the report, Google's generative AI controls let you decide whether your site's links and content appear in AI Overviews, AI Mode, and AI Overviews in Discover. Find them at Settings → Crawling & Indexing → Search generative AI. One constraint to know before you plan around them: the control is property-wide, not per page — you cannot exclude one section while leaving the rest eligible. The three options:

• ▸ Include — Google may use your site to ground AI responses and show links to your content.
• ▸ Exclude — Google will not use your pages to ground AI answers or link to them.
• ▸ Inherit — child properties follow a parent property's setting (overridable).

The control's origin is regulatory, not charitable. On 3 June 2026, the UK Competition and Markets Authority imposed a conduct requirement giving publishers "effective tools to prevent their content being used to power AI features in search, such as AI Overviews," obliging Google to attribute publisher content with clear links inside AI-generated results and to let publishers opt out of model fine-tuning separately. Google has nine months to implement, putting the deadline at March 2027 — and the outstanding items are exactly the two gaps publishers complain about most: page-level (rather than property-wide) AI controls and click reporting. The Search Console control available today is the user-facing expression of that requirement, rolling out UK-first and completing worldwide availability on 31 August 2026.

October 2026: the first controlled evidence that impressions and clicks diverge

Through September, the objection to the generative AI report was theoretical: it counts impressions but not clicks. A preregistered randomised field experiment has now turned that objection into a measurement problem. Researchers at the University of Pennsylvania and Northeastern University ("AI in Search Reduces Publisher Referrals Without Improving User Experience," released August 2026; covered by Search Engine Land on 23 September 2026) used a browser extension to randomly assign 1,100 US Google users to one of three conditions for one week: no AI at all, Google as normal, or every search routed into AI Mode.

Source: University of Pennsylvania + Northeastern University, "AI in Search Reduces Publisher Referrals Without Improving User Experience" (preprint, August 2026); reported by Search Engine Land, 23 September 2026. Caveats from the authors: AI Mode represented only 0.6% of baseline searches, the sample skewed younger and more educated, and Google changed its page code mid-study so only about half of AI Overviews were successfully hidden — meaning the +8.8 pp uplift is likely an underestimate.

"If traffic falls while rankings and impressions hold steady, it is easy to assume something has gone wrong with the SEO. In reality, the search results page is simply answering more of the question itself."

The operational consequence is blunt: stop treating rising generative AI impressions as evidence that visibility is converting into demand. Report them next to clicks and sessions, never instead of them. Where impressions hold and clicks fall, the result page changed — not your rankings.

The AI-share metric: the one number the report lets you build

Google confirms that ordinary web impressions already include appearances in AI Overviews and AI Mode — the generative AI view isolates a subset, it is not an additional channel. That detail is also the report's most useful property: because the AI numbers sit inside the web numbers, you can divide one by the other for each page.

One more mechanical constraint to plan around: as of October 2026 the Search Console API still exposes only web, image, video, news and Discover search types — there is no AI Overviews or AI Mode type. No tool can pull this report automatically, so a monthly manual export is the only way to own your history. Export the Search view (not Discover) and store the file; the report's own retention is not your baseline.

Why impressions are not the whole story: the 2.9% finding

Even with Google's report live, it only counts your own domain. And the own-domain slice of AI visibility is surprisingly small. A 2026 large-scale baseline (Pratyush Kumar; capston.ai analysis) examined 102,025 prompt responses and 149,912 citations across 102 brands on ChatGPT, Gemini, Perplexity, Claude, and Grok (March–May 2026). Two findings reframe the work:

The consequence is uncomfortable for anyone selling on-site optimization alone: engines mostly cite pages about you that you do not own. Search Console shows your 2.9%; the other ~97% lives on review sites, roundups, and third-party coverage. A complete GEO measurement program pairs the native report with off-domain brand-mention tracking (see our guide on tracking your brand in AI answers). One more wrinkle from the same study: sentiment flipped in 45.5% of runs versus 6.8% for mere mention status — how you are framed is roughly 6.7× noisier than whether you appear at all.

Cloudflare's September 2026 AI-bot defaults

Crawler access is the gatekeeper beneath all of this. From September 15, 2026, Cloudflare applies new default posture for AI bot traffic, split into three categories:

• ▸ Search bots — allowed by default. These are the crawlers that help your content appear in AI answers (e.g., Google-Extended, OAI-SearchBot). Keep them allowed.
• ▸ Training bots — blocked by default on pages that display ads.
• ▸ Agent bots — blocked by default on pages that display ads.

The GEO takeaway: the bots that drive AI citations stay on by default, so most sites need no change — but if you run Cloudflare and have been blocking bots wholesale, now is the time to confirm search crawlers are explicitly allowed. In response to the announcement, Google's John Mueller reiterated that Google does not use llms.txt or llms-author.txt files — another signal that crawler access and structured content, not self-described summaries, govern AI eligibility.

How to read your AI report: a 5-step weekly playbook

1. 1.
   Confirm the report is enabled

   Open Search Console → "Search results" → look for the generative AI dropdown. If absent, it is coming; check again weekly. Verify the AI opt-out control is set to "Include" unless you have a brand-safety reason not to.

2. 2.
   Rank pages by AI impressions

   Your top AI-visible URLs are the pages Google's models already trust. Protect them: keep dateModified fresh, verify Schema.org, and ensure Google-Extended can crawl them.

3. 3.
   Cross-check against referral traffic

   High AI impressions with low referrals is normal under zero-click. Do not panic — but do treat the impression count as a visibility score, not a traffic number.

4. 4.
   Audit off-domain citations

   Since ~97% of your brand's AI citations sit off your domain, track review sites, roundups, and "best-of" listicles that mention you (ranked listicles carry 21% of all citations). Influence them with accurate, citable data.

5. 5.
   Watch sentiment, not just mentions

   Framing flips in 45.5% of runs. One negative-looking AI answer is noise, not a crisis — but a pattern of mis-framing is a real GEO problem worth correcting at the source.

Common mistakes with the new controls

• ▸ Treating AI impressions as clicks — The report has no click or query data yet; pair it with referral logs and brand-mention tools.
• ▸ Opting out by default — Excluding your site removes you from AI answers and is not an organic ranking signal; only opt out for genuine risk reasons.
• ▸ Ignoring off-domain footprint — 97% of brand citations live elsewhere; on-site optimization alone misses most of your AI visibility.
• ▸ Blocking search bots at the edge — A Cloudflare or security rule that blocks AI search crawlers silently opts you out of every AI citation, regardless of Search Console settings.

Frequently asked questions