Measurement, control 9 of 17
M-09 Use Google generative Search impressions accurately
The documented generative Search report provides impressions for covered Google AI surfaces. It is not a recommendation, click or revenue report.
- Priority
- High priority.
- Hard gate
- No
- Change class
- READ_ONLY: Inspect authorised evidence.
- Quality bucket
- Measurement and experiment readiness
Why it matters
Third-party estimates of AI Overviews and AI Mode visibility are modelled guesses, while Search Console reports what Google itself recorded. Relying on estimates first can send a team in the wrong direction. Impressions on their own also say little about business value, so they need to be read alongside conversions and the changes you made.
Evidence to review
- Property-specific report export, field dictionary and limitations.
How to implement
- Confirm actual report availability and the effective inclusion setting.
- Preserve pages, dates, countries, devices and available filters as exposed.
- Keep missing or thresholded data separate from observed zero.
- Do not assume the standard Search Analytics API exposes every new UI field.
How UltimateSEO checks this
Partly automated. The scan records information signals only, so this control never becomes PASS or FAIL on its own.
Evidence needed: the Generative AI Performance report in Search Console and how it feeds decisions.
States used: PASS, FAIL, UNKNOWN, NOT_APPLICABLE or BLOCKED. UNKNOWN is never shown as a pass. How states work.
Sources
Part of The UltimateSEO Framework v4.3, catalogue dated 2026-10-14. Evidence states, control states and the publish gate are explained on the hub.