The Generative AI Report in Google Search Console: What It Measures and What It Can’t Tell You

Google finally shows site owners where their pages appear in AI Overviews and AI Mode. That first-party view is useful. But the new Generative AI performance report is narrower than its name suggests.

The report measures qualifying link impressions. It doesn’t yet isolate clicks, prompts, leads, or sales. It also can’t separate AI Overviews from AI Mode.

Read too much into one number, and your team can head the wrong way. The real job isn’t finding the report. It’s knowing what the data proves, what it can’t, and which numbers belong beside it.

Reporting note: This article reflects public Google documentation available on August 12, 2026. Google is still rolling out the report gradually. Its metrics, availability, and interface may change.

Key takeaways

• The report counts impressions from AI Overviews and AI Mode. You can split them by page, country, device, and date.
• It doesn’t currently show prompts, clicks, click-through rate, average position, or conversions. It also gives no separate AI Overviews and AI Mode totals.
• The data already sits inside regular Web search totals. Adding the two together counts the same visibility twice.
• An impression means Google showed a qualifying link under its counting rules. It isn’t a visit, recommendation, citation rank, or unique person.
• The most useful review pairs this report with regular Search Console data and analytics. Add page-change notes and a small, consistent prompt sample.

What changed in Google Search Console?

Google announced the dedicated Generative AI performance report for Search on June 3, 2026. The report pulls impressions from AI Overviews and AI Mode into one focused view.

Before that, Search Console folded the same activity into the Web search type. You couldn’t inspect it on its own in the normal Performance report.

As of August 12, 2026, Google’s help page still describes access as a rollout. It reaches a subset of website owners, not everyone. That wording matters.

A missing report doesn’t automatically mean your site has no AI visibility. It doesn’t prove a technical fault, either.

Think of the report as a better first-party baseline. It isn’t the prompt-level attribution report many teams hoped for.

Google gives you a cleaner count of link appearances. You also get enough dimensions to spot page-level patterns. But the report stops well short of the path from generated answer to customer.

What does the report actually measure?

The report currently has one metric: impressions. Google counts the times a user saw a link to your site. The link has to appear in a supported generative AI feature.

AI Overview links count only after the user scrolls or expands them into view. AI Mode follows Google’s standard impression rules.

You can break that impression count down four ways:

• Pages: the final linked URL after redirects. Google usually credits its selected canonical URL.
• Countries: where the search began.
• Devices: desktop, tablet, and mobile.
• Dates: hourly, daily, weekly, or monthly, depending on the selected range.

Keep one accounting rule straight. The regular Search Performance report already includes these impressions under Web. Don’t add the two totals together.

The dedicated report is a filtered view of part of the whole. It isn’t a new pool of visibility sitting beside it.

What does an impression not mean?

An impression is useful, but it’s easy to oversell. It doesn’t prove that Google quoted a passage from your page. Nor does it show that your page held the most prominent supporting link.

An impression also isn’t any of these:

• A click or visit
• A lead, purchase, or other conversion
• A unique person
• A recommendation from Google
• A citation rank or share-of-voice score
• Proof that a page edit caused later growth

Google does count qualifying AI Overview and AI Mode clicks in ordinary Web search data. But the dedicated Generative AI report doesn’t currently isolate those clicks.

A page can record 2,000 generative Search impressions. This report alone can’t tell you whether that produced two visits or two hundred.

The same restraint applies after a content update. Say impressions rise two weeks after a rewrite. Record the timing, but don’t treat it as proof the rewrite caused the increase.

Search demand, rollout changes, competitor pages, indexing, and Google’s systems can all shift at once.

Why can chart totals and page totals disagree?

Search Console can aggregate the same result differently, depending on where you look. Take one generated result that shows two pages from the same site. At the property level, that can count as one site impression.

In the Pages table, each qualifying linked page can receive its own impression. So the page rows may add up to more than the chart total.

Here is a hypothetical example. An AI response shows a plumbing company’s maintenance guide and its pricing page. The property chart records one impression for the site.

The Pages table records one per URL, so its rows add up to two. Neither number is necessarily wrong.

A few other limits can create confusion:

• The table displays up to 1,000 rows.
• Recent data may be preliminary when Google marks it with a dotted line.
• Values shown as a tilde or a dash become zero in an export.
• The report excludes Search Labs experiments.

A mismatch deserves a closer look. But it isn’t automatically a tracking defect.

Why don’t I see the report?

Google lists three common reasons:

• Your property may not have received access yet.
• The site may not have enough impressions in supported features.
• Someone may have excluded the site through the Search generative AI control.

Start in Search Console Settings and check that control before assuming the worst. Google says it allows inclusion by default.

Then confirm Google has indexed the pages you care about. Check that they’re eligible to show a snippet. If those basics are sound, the cause may simply be access or volume.

But don’t treat a missing report as a site-health diagnosis. It isn’t a crawl report, indexing report, or manual-action notice. Search Console already has separate tools for those jobs.

Build a baseline before changing pages

A report this new creates a strong urge to start rewriting. Resist it.

Change ten pages before recording the starting point, and you’ll have a pile of activity. But you’ll have no clean way to judge what followed.

Use 90 days when the property has enough history. If it doesn’t, use the longest stable window available. State that range in every update.

Save the chart and table data too. That way you keep a record even if Google changes the interface later. A useful baseline covers seven steps:

1. Record total generative Search impressions for the period.
2. Export the page, country, device, and date tables.
3. Calculate how much of the total sits with the top five pages.
4. Group visible pages by purpose, such as service, guide, category, product, or location.
5. Mark major publishing, migration, and page-update dates.
6. Compare the same pages in the regular Web search report.
7. Review organic landing-page engagement and conversions in your analytics platform.

That last comparison is directional. The dedicated report and your analytics platform don’t share a clean user-level join. Nothing in them proves an AI impression became a form submission.

You’re looking for patterns that deserve a test. Don’t manufacture certainty the data can’t support.

A hypothetical 90-day example

The following numbers are hypothetical. A B2B service company records 38,000 generative Search impressions over 90 days. Here is how they break down:

• One comparison guide receives 12,400, about 33 percent of the total.
• All service pages combined receive fewer than 2,000.
• Mobile accounts for 71 percent.
• 84 percent of impressions come from the United States.

The sensible reading is modest. The guide is the company’s clearest current visibility asset in Google’s generative Search features. The team should check three things:

• Why the guide works
• Whether its facts are current
• Whether an interested reader can reach a relevant service page without hunting

Stronger internal links may help the page do more useful work after a visit. So may a clearer next step.

The team can’t claim the guide produced 12,400 visits. It can’t say Google recommended the company 12,400 times. Nor can it say those impressions caused sales.

Copying the guide’s format across fifty thin pages wouldn’t be sensible either. One strong pattern is a reason to inspect, not a license to mass-produce.

Now picture a local HVAC company whose emergency-repair guide holds most of its impressions. Search Console still provides no prompt data in this report. So the next move has three parts:

• Compare regular query data.
• Read the page on a phone.
• Collect the questions real callers ask.

Don’t invent a list of AI prompts from an impression total. That only makes the report look more precise than it is.

What should you do with strong and weak pages?

Start with the pages already appearing. Check these details on each one:

• Dates and named sources
• Original examples
• Internal links
• The path to a relevant product or service

Make the central answer easy to find in visible text. Does the page contain an old figure, an unsupported claim, or a dead end? Fix that before adding more content.

For pages with little or no visibility, go back to ordinary search basics:

• Confirm crawling and indexing.
• Check whether the page is eligible for a snippet.
• Look at internal links, duplication, and page experience.
• Ask whether the topic is useful enough to deserve a page at all.

Google’s published guidance says AI Overviews and AI Mode need no special markup. Eligibility needs no special file, either.

Google Search doesn’t use llms.txt as a ranking or visibility signal. That statement covers Google Search, not every other AI service.

The work is still the same:

• Clear pages
• Accurate structured data where it fits
• Useful media
• Sound technical access
• Original information

Those practices support eligibility and help Google Search process a page. They don’t guarantee an AI Overview, an AI Mode appearance, a ranking, or a lead.

A monthly review can take 30 minutes

You don’t need a giant dashboard. A short monthly check is enough for most teams. That’s especially true while access and reporting are still changing.

Split the 30 minutes like this:

• Five minutes: compare the latest month with the prior month. Add the same period last year when useful.
• Ten minutes: inspect the pages with the largest absolute changes.
• Five minutes: check country and device shifts.
• Five minutes: review annotations for site and content changes.
• Five minutes: write one action, one open question, and one item that needs more data.

Every update should answer five short questions:

• What changed?
• Which pages moved?
• What might explain it?
• What can we verify?
• What will we watch next?

If the report can’t support an answer, say so. A blank cell is better than a confident guess.

How does this change GEO measurement?

Sampled prompt tracking still has a role. But it shouldn’t carry the whole GEO measurement plan for Google’s generative Search features. Seeing how people find and use your site takes several sources:

• Search Console now supplies first-party impression history.
• A controlled prompt sample can add question and competitor context.
• Analytics shows what visitors do after they reach the site.

None replaces the others. The same separation helps when teams measure social and video content in Search Console.

Platform properties show how supported off-site accounts perform in Google Search. The Generative AI report covers qualifying links from your website inside supported AI features. The two answer related questions, but they aren’t interchangeable.

Our view is simple. Treat the Generative AI report as a better flashlight, not a scoreboard. It can point to pages and shifts worth examining.

A sound measurement plan still needs a few basics:

• Clear definitions and consistent dates
• Normal search data and analytics
• Someone willing to write down what the numbers don’t show

Maybe the report is collecting data and your team still can’t explain which pages matter. Or maybe nobody knows what should happen next.

Ardoz Digital can review the page patterns against wider search and analytics data. Then we identify practical next steps.

That work can produce a clearer plan. It cannot promise placement in AI Overviews or AI Mode.

Ardoz Digital is not affiliated with or endorsed by Google. We name Google Search Console and related products only to identify them.