Google Search Console Finally Shows AI Search Data: Rollout Timeline and SEO Impact

Generative AI Search
Google Starts Showing AI Data in Search Console
For nearly two years, SEOs have been staring at a hole in their data. Ever since AI Overviews started reshaping the search results page back in 2024, every practitioner “knew” that generative answers were eating into organic clicks — but nobody had official numbers to prove it, size it, or act on it. That blind spot has finally started closing.

In June 2026, Google rolled out a dedicated Generative AI Performance report inside Search Console. It’s not a complete picture yet, and it isn’t available to everyone, but it’s the first time site owners have gotten any first-party visibility into how their content shows up inside AI Overviews, AI Mode, and AI-powered Discover.

Here’s the full timeline of what’s happened so far, and how SEOs should be thinking about it.

The Timeline

May 18, 2026 — The data clock starts: Google set this as the earliest date the new report can pull data from. There’s no historical backfill before it, so even sites that get early access won’t be able to look back further than this point. If you’re planning to use this data for trend analysis, treat mid-May 2026 as day one.

June 3, 2026 — Official launch: Google introduced two new reporting views inside Search Console: one covering AI Overviews and AI Mode within Search, and a separate one for AI-generated features inside Discover. Alongside the report, Google shipped a new opt-out control that lets site owners exclude their content from generative AI features entirely, without any impact on regular organic rankings.

This wasn’t a voluntary transparency gesture. It was largely a response to regulatory pressure — specifically the UK Competition and Markets Authority’s requirements under the Digital Markets, Competition and Consumers Act 2024, which pushed Google toward giving publishers genuine, auditable visibility and control over how their content is used in AI-generated answers.

June 3–17, 2026 — Limited UK beta: The rollout didn’t go global on day one. Google restricted initial access to a subset of UK-based site owners, framing it as a controlled test to gather feedback before scaling. The opt-out toggle followed shortly after, becoming fully effective on June 17, 2026.

Late June–July 2026 — Slow, uneven expansion: Access continued to trickle out beyond the UK in the following weeks, but inconsistently. Some site owners in other regions began seeing the report appear in their accounts, while many others — including large portions of the US market — still didn’t have it. Google gave no fixed schedule for when a given country or property would get access.

June 23, 2026 — India, the US, and Switzerland start seeing access: Roughly three weeks after launch, SEOs began reporting the report appearing outside the UK for the first time. Multiple practitioners with Indian-based properties confirmed access on non-UK sites, alongside reports from US-based properties and at least one Switzerland-based profile. Google did not announce this expansion formally — it surfaced organically through SEO community reports on X and Mastodon before being picked up more broadly. This matters because it shows Google’s rollout pattern: quiet, incremental, region-by-region, with no public changelog entry marking each expansion.

July 22, 2026 — France goes live: AI Overviews and AI Mode became available in France, and with that, French-language properties started seeing their AI impression data begin from essentially zero, since the underlying AI features themselves hadn’t been active there before.

Ongoing — expanding, but still not global: As of the most recent reports, access spans the UK, India, the US, Switzerland, and France, with more countries likely picking up access on the same quiet, unannounced basis. If your property isn’t showing the report yet, it doesn’t necessarily mean your country is excluded — check back periodically, since Google has been adding regions without formal announcements. A fully global rollout is still unconfirmed on any specific date. Under the UK regulatory deadline that triggered this whole initiative, Google has roughly nine months from the original mandate to implement the complete set of required controls, putting a hard deadline somewhere around March 2027 — though officials have indicated the more important pieces should land sooner than that.

Worth noting: Google isn’t first here: Bing Webmaster Tools already has its own Bing AI performance report (Launched on February 10, 2026), and unlike Google’s staged rollout, it launched available globally from the start — giving Bing’s version broader reach for months while Google was still limited to a UK subset. That’s a useful comparator if you’re managing multi-engine SEO reporting and wondering why your Bing AI data looks more complete than your Google AI data right now.

What the Report Actually Shows

You’ll find it in the sidebar under Performance → Generative AI — it sits as its own sub-item beneath the main Performance report, alongside the regular Search results view, rather than as a separate top-level section.

It’s worth being precise here, because early coverage oversold what’s available. At launch, the Generative AI Performance report includes exactly five dimensions:
Google Search Console Showing AI Search Impressions
Google Search Console Showing AI Search Impressions

Inside the New "Search Generative AI" Control Panel

The control lives under Settings → Search generative AI inside Search Console. Once you open it, you get three options:

  • Inherit control from [your domain] — this is the default state for every property. It simply follows whatever setting is applied at the parent domain level, and the panel shows you the current effective control (Include or Exclude) so you’re never guessing what’s actually in force.

  • Include my site’s links and content in Search generative AI features — this is the setting most sites will stay on. Google’s own description frames it as maximizing visibility: your pages can appear as cited links, help ground AI-generated answers, and still receive impressions and traffic through these features.

  • Exclude my site’s links and content from Search generative AI features — the opt-out. Choosing this prevents your site from being surfaced or linked to within AI features and stops it from being used to ground AI answers. The tradeoff is stated plainly: you won’t receive any impressions or traffic from generative AI features at all if you turn this on.

Generative AI Search Setting in Google Search Console
Generative AI Search Settings in Google Search Console
A few implementation details matter more than they might look at first glance:

  • It’s a property-wide switch, not a page-level one. Changing this control applies to every page under that property — there’s no way to include some URLs and exclude others from within this panel.

  • Inheritance flows downward to child properties. If you manage a domain with multiple subdomains or subdirectories verified as separate properties, they inherit the parent’s setting by default — but each child property’s owner can override it independently. That’s useful for larger sites where, say, a blog subdomain wants different AI visibility than a checkout or account subdomain.

  • It’s framed as a visibility decision, not a ranking one. Nothing in the interface ties this setting to organic rankings, and Google has been explicit elsewhere that this control has no bearing on how you rank in standard search results or Discover.

Practically, this means the setting works less like robots.txt (all-or-nothing, technical, easy to misconfigure) and more like a business decision made in an accessible UI — which is likely intentional, given regulators wanted this to be a genuinely usable option for ordinary publishers, not just developers.

Why This Matters for SEO Strategy

1. You finally get a partial answer to the “is AI eating my traffic” question. Impressions-only data isn’t the full picture, but it’s the first verifiable signal. If a page is racking up AI impressions while its organic clicks in the standard Performance report are flat or falling, that’s a real, attributable pattern worth investigating — not a hunch.

2. Page-level visibility opens the door to a new kind of content audit. Because the report tells you exactly which URLs are being pulled into AI features, you can start correlating content structure, format, and freshness with AI citation likelihood. Pages that get cited frequently are worth studying as internal case studies for what AI systems seem to favor.

3. The opt-out toggle is a genuinely new lever, not a repackaged old one. It’s easy to confuse this with existing controls, but it behaves differently from both of them:

  • Google-Extended blocks your content from being used to train AI models — it does nothing to stop AI Overviews from citing you.
  • nosnippet blocks AI features from using your content, but it also strips your snippet from regular organic results.
  • The new Search Console toggle is the first control that blocks AI-feature inclusion specifically, while leaving your organic snippet and rankings untouched.
That makes it a much cleaner decision for publishers who are ambivalent about AI visibility but don’t want to sacrifice normal search performance to get out of it.

4. Regional rollout gaps mean your data may be premature — don’t overreact. If your site operates across multiple markets, don’t assume flat or missing AI impression numbers mean your content isn’t being surfaced. It may simply mean your market hasn’t been switched on yet, or that the underlying AI feature itself hasn’t launched there (as was the case in France until July).

5. Treat this as the opening move, not the finished tool. Given Google’s own admission that clicks, queries, and API access are still missing, any AI-search strategy built purely on this report today will be incomplete. The realistic move is to start tracking the dimensions you do have now, so you’re building a clean historical baseline by the time richer data (especially clicks and queries) eventually ships.

What to Do Right Now

  • Check your Search Console property regularly for a new “Generative AI” section under Performance — there’s no notification when access is granted, and Google has been expanding country access quietly (the UK, India, the US, Switzerland, and France are confirmed so far).

  • If you get access, start logging impressions weekly, even in a simple spreadsheet, so you have your own historical record independent of Google’s UI.

  • Cross-reference AI impression spikes against your regular Performance report to look for correlated dips or plateaus in organic clicks.

  • Decide deliberately whether opting out makes sense for your content strategy — head to the “Search generative AI” control panel in Search Console, confirm what’s currently inherited or set, and remember it’s a property-wide (not page-level) decision with no ranking downside either way.

  • Don’t restructure your entire content strategy around this data yet. Treat it as an early signal to monitor, not a KPI to optimize against, until click and query data arrive.

Why Is Google Really Launching This?

Google’s own framing is “transparency” and “publisher control.” That’s true as far as it goes, but it’s also the version of the story Google would tell regardless of the real motivation. It’s worth pulling apart the different theories floating around the SEO and publishing world, because they aren’t mutually exclusive — this move likely serves several of them at once.

Theory 1: It’s a PR move to counter the “Google is stealing our traffic” narrative. There’s a strong case here. The pressure on Google hasn’t been quiet. Pew Research data has shown that when an AI Overview appears at the top of a results page, only a small fraction of users click any of the underlying source links — a stark drop compared to results pages without one. Giving site owners a dashboard that shows “look, you’re still getting impressions” is a low-cost way to reframe the conversation from “you’re disappearing” to “you’re just being measured differently now.” Whether impressions without clicks actually reassure anyone is a separate question — but as an optics move, it’s efficient.

Theory 2: It’s a retention play against third-party AI-visibility tools. This one holds up well too. An entire category of tools has sprung up in the last year specifically to track brand and content mentions inside AI Overviews, ChatGPT, and other generative answers, because no first-party option existed. Every time a marketer opens one of those tools instead of Search Console, that’s a habit forming outside Google’s ecosystem — and habits are sticky. Shipping even a limited native version inside Search Console is a plausible defensive move to keep that workflow, and the accompanying keyword/traffic data around it, inside Google’s own product.

Theory 3: It’s about keeping SEO “reportable” as an industry, because Google needs SEOs to keep believing the game is winnable. This is a subtler angle but worth taking seriously. SEO as a discipline depends on the idea that effort produces measurable, attributable results. If a large and growing share of visibility becomes literally unmeasurable, the incentive for businesses to invest in content, technical SEO, and links weakens — and that investment is part of what keeps the web (and Google’s index) rich with content worth serving. A reportable AI layer, even a thin one, keeps SEO as a discipline feeling viable rather than obsolete.

Theory 4: It’s cover against allegations that AI Overviews are siphoning clicks by design. This is probably closer to the center of it than Google would say outright. The traffic numbers being cited by publishers this year are severe — some large news properties have reported organic traffic declines of 25% to over 80% year over year, and multiple major publishers have openly discussed blocking Google’s crawlers entirely rather than continuing to accept the current trade-off. Against that backdrop, a report that shows impressions (activity) without clicks (impact) is, cynically, a way to demonstrate “engagement” without having to surface the metric — click-through rate — that would actually confirm or deny the harm publishers are alleging. That omission is unlikely to be accidental at this stage of the product.

Theory 5: It’s a hedge against a wave of publishers blocking Google outright. This is arguably the most urgent driver of all. Through 2026, a growing list of major publishers and platforms — including outlets like the Associated Press, The Atlantic, and Condé Nast, alongside infrastructure providers like Cloudflare defaulting new customers to block AI scrapers — have moved toward restricting AI crawler access by default. Some publishers have gone further and openly discussed cutting off Google Search crawling entirely, not just AI training access, if the traffic trade-off doesn’t improve. If a critical mass of content providers actually pulled their content, Google’s AI features would have a lot less to summarize. Giving publishers a reporting layer and a clean opt-out is a way to keep them inside the tent — negotiating through settings rather than through robots.txt files and lawsuits.

A few additional angles worth considering:

  • Regulatory self-defense, not just UK compliance. The report technically satisfies a UK mandate, but Google almost certainly built it knowing regulators in the EU, and potentially the US, are watching the same issues. Shipping a version of this now — even a limited one — gives Google a working answer ready if similar demands land elsewhere, rather than building one from scratch under a future deadline.

  • Data control as a negotiating chip. By defining exactly which metrics exist (impressions, pages, countries, devices) and which don’t (clicks, queries, API access), Google controls the terms of the transparency conversation. Publishers can’t demand click data Google hasn’t offered — they can only ask for it, which keeps the pace of disclosure entirely in Google’s hands.

  • Building the infrastructure for a future publisher-payment model. Google has already tested payment programs tied to how content is used in AI features. A page-level, country-level, time-stamped impressions report is exactly the kind of data infrastructure you’d need before rolling out anything resembling AI-citation-based compensation. This report may be as much a foundation for that future system as it is a transparency tool for today.

  • Slowing the shift toward answer engines and AI browsers. Every publisher that blocks Google outright, or leans harder into licensing deals with OpenAI, Amazon, or others, is content Google’s own AI features can no longer draw on either. Keeping publishers engaged with Google specifically — rather than pivoting fully to other AI partners — protects the quality of Google’s own generative answers, not just its search index.
The honest answer is probably “most of the above, in different proportions.” Google rarely ships a single-purpose feature when it can ship one that serves compliance, PR, retention, and product strategy simultaneously — and this report checks all four boxes.

The Bottom Line

This is the most significant transparency shift Search Console has seen in years, but it’s still a first version — built quickly, under regulatory pressure, with major gaps by design. For SEOs, the right posture right now is to start watching, start logging, and stay ready to act once Google fills in the missing pieces: clicks, queries, and full global access.