Quick answer
Search Console AI position is a feature-level measurement: it records where the AI feature sat among results, not where your citation ranked inside the generated answer. It cannot be averaged with standard Search position, and totals across surfaces can double count the same appearance. Report it as its own labelled row and judge it against leads and revenue.
- Feature-level placement, not citation rank inside the answer
- Never blended into standard average position
- Surface totals can double count a single search
The dedicated generative AI performance report gave teams their first official view of AI exposure, and it arrived with a column that causes more misreporting than any other: position. The word carries decades of SEO meaning, and almost none of that meaning transfers.
This page is deliberately narrow. Our general guide to the AI report covers what the report measures overall. Here we only deal with position mechanics and the reporting decisions that follow from them.
What position means here
Position in this context is recorded at the feature level. It describes where the AI feature appeared among the things on the results page. It does not describe:
- Which link inside the generated answer was yours.
- How high your citation sat within the answer text.
- How prominent or how long the reference to you was.
- Whether a reader ever saw your name at all.
That distinction is the whole article. A page can be cited in an AI answer that sits high on the results page and still be the last of eight sources listed. Position would look strong. Prominence would not be measured.
AI Overviews and AI Mode behave differently
The two surfaces are not symmetrical, so a single position rule cannot apply to both.
| Surface | What position reflects | Reporting note |
|---|---|---|
| AI Overviews | Placement of the AI Overview block among other result types on the page | Comparable across dates for the same surface; not comparable to blue-link position |
| AI Mode | The generated response is the surface itself, so there is no ranking of the feature against other page blocks | Do not read a low or absent value as a ranking loss |
The dedicated report does not split AI Overviews from AI Mode. That means you cannot attribute a movement to one surface. State that limitation in the report itself rather than choosing an explanation.
Aggregation boundaries
Search Console aggregates differently depending on what you group by, and the AI report inherits that behaviour. Three boundaries matter in practice:
- Page grouping. Figures grouped by page answer a different question from figures grouped by property. Pick one per row and label it.
- Date grouping. Position averages over a range are not the average of the daily averages you might compute yourself. Use the tool's own range rather than recomputing.
- Country and device grouping. Filtering changes the denominator. A Canada-filtered position is not the worldwide position with the other countries removed from a total.
The double-counting warning
This is the failure mode that damages credibility fastest. A single search can produce exposure in more than one place, and adding surface totals together can count the same appearance twice. Two rules prevent it:
- Never present a single combined visibility number across Search and AI surfaces.
- Never sum across overlapping date ranges or overlapping filters to build a bigger figure.
If a stakeholder wants one number, give them a business number: qualified leads. Visibility stays as separate labelled rows.
A monthly reporting workflow
- Freeze the range. Complete settled days only, identical across every source you pull.
- Pull AI exposure by page. Impressions and position, with country and device recorded as filters, not merged.
- Pull standard Search performance for the same pages. Keep it in its own columns.
- Add analytics and CRM outcomes. Sessions, conversions, qualified leads, and revenue where a closed deal traces to the entry page.
- Label every number by source. Search Console, analytics, or CRM. Mixed-source totals are how reports lose trust.
- Write one sentence of interpretation per page. If you cannot write it without speculating, the honest note is that the data does not support a conclusion yet.
Language that survives an executive review
Wording does the work here. Useful phrasing, and the phrasing to avoid:
| Say this | Not this |
|---|---|
| The AI feature containing our page appeared in this average on-page placement | We rank third in AI answers |
| Exposure rose while qualified leads stayed flat | AI traffic is growing |
| The report does not separate AI Overviews from AI Mode, so the cause is unattributed | The change came from AI Mode |
Where the evidence comes from
The metric rules described here follow Google's own documentation for the generative AI performance report and its worldwide availability. Search Engine Journal reported a discussion by Google's John Mueller on September 13, 2026; we treat that as commentary on existing behaviour, not as a separate product announcement, and nothing above depends on it.
We have no fresh Search Console figures to publish alongside this, and we are not presenting older numbers as current. Search volume, difficulty, CPC, backlink and AI citation-frequency data for this topic are unavailable, so none appear.
If you would rather this ran as a standing monthly report than a spreadsheet argument, our reporting service builds it with the outcome columns attached. The citation signals behind the exposure are handled by our AEO services and GEO services.
Want your AI reporting to survive scrutiny?
Book a free 30-minute consultation. We will review how your AI exposure is currently reported and show you which pages earn citations that convert.
Book My Free Consultation