What the dedicated report currently measures
Google's official help page, checked on October 4, 2026, describes a generative AI performance report for Search. Its listed capabilities are AI Overviews and AI Mode. The chart reports impressions, and the listed table dimensions are Pages, Countries, Dates and Devices. The documentation states:
The chart displays total impressions for your property over the selected time period.
Generative AI performance report for Search
That is a useful visibility measure. It does not, by itself, establish a click numerator. The current field list does not document Queries or separate AI Overviews and AI Mode columns either. A page's AI impressions therefore cannot be read as visibility for an individual question in either feature.
Check where each number comes from
Put the report name beside the value before choosing a formula. These two sources answer different measurement questions, even when their numbers describe the same website.
| Dedicated AI report | Overall Web performance report |
|---|---|
| AI impressions: visibility within the included generative AI features | Web impressions: visibility across the selected Web results scope |
| No independent AI-click metric in the current official field list | Clicks across the selected Web scope, rather than an isolated AI subset |
| No AI CTR metric documented in that field list | CTR defined from that report's click and impression counts |
| AI subset already represented in overall data | Overall total already includes the reported AI data |
The general Performance help page defines clicks as “The number of times a user clicked your site from Google Search results.” It defines CTR as “The click count divided by the impression count.” Selecting Web gives a Web result measure; neither definition turns that total into AI-only clicks. Performance report definitions
Treat the table as a source check, rather than a recipe for combining exports. A shared website or page label does not establish that the two metrics count the same population.
Two calculations that mix incompatible totals
Google's launch announcement explicitly says, “This data is included in the overall performance report”. The dedicated view separates visibility for inspection; it does not create an additional pool of impressions outside the overall total. Search Generative AI report announcement
Consider the proposed ratio Web clicks / AI impressions. The numerator can contain clicks from Web results outside the AI subset, while the denominator is limited to AI impressions. The arithmetic may produce a percentage, but that percentage cannot describe the chance of an AI impression becoming an AI click. Labeling it “AI CTR” would conceal the mismatch.
The second tempting calculation is Web impressions + AI impressions. Because the AI data is already included in overall performance, the added amount repeats that subset. Keep the overall total and the dedicated AI figure separately labeled. Do not present their sum as a larger combined reach figure.
What is still missing for AI CTR
Before calculating a rate, require an independently identified AI-click count and an AI-impression count with compatible scope and counting rules. The current official field list supplies the visibility side of this requirement, but does not document the required AI-click numerator. It also supplies no query dimension from which to take a denominator for an individual question.
Do not substitute the number of answers generated by a test question set for Search Console impressions. Those answers are observations from a different collection process. Their count cannot supply the exposure denominator for Google users' clicks. The same reasoning applies to a question set's mention count: it can describe that test, without completing an AI CTR calculation.
For the broader discipline of keeping measures tied to their observation units, see AI visibility card denominators. Use each measure for the question it can actually answer.
Keep a usable record without inventing a rate
A practical measurement note can preserve the available evidence and the unresolved calculation:
- Record the exact report title, metric label and selected scope alongside each exported value.
- Label the dedicated figure as AI impressions. Label the general figure as Web clicks or Web impressions, as appropriate.
- Mark the proposed AI CTR as not calculable from these fields, with the reason: an independently identified AI-click numerator is not documented.
- Retain the official field description used for that decision. Recheck it if Google adds metrics or dimensions before reusing the calculation.
This conclusion depends on the fields officially listed at the check date. A future AI-click field would require a fresh compatibility check, rather than automatic reuse of the Web total. Meanwhile, reported AI impressions remain useful evidence of visibility. When turning measurement findings into content work, From Google Rankings to ChatGPT Answers offers a separate way to organize questions and evidence; its observations do not replace Search Console metrics.
Want to see how AI engines describe your brand today?
Get a free growth audit