Average position is a Google Search Console metric showing where your site typically appeared in search results. For each impression, Search Console records the topmost position any of your pages held, then averages those positions across all impressions. It is useful for tracking a single query or page over time, and easy to misread when it averages together many queries with very different rankings.
How it is calculated
Position counts down the page, with 1 as the topmost result. Google's help documentation explains that features such as a carousel or an AI Overview occupy a single position, and that links inside them share that position. If your site shows up more than once on a page, only the highest position counts for that impression.
The figure you see in a report is an average of those values, weighted by impressions. Position is only recorded when your result was shown, so queries where you did not appear do not pull the average down.
Why the average can mislead
Average position across a whole site or a large group of queries mixes very different situations. A page ranking first for its own brand and fortieth for a hundred long-tail queries can show an average that describes neither.
It can also move for reasons unrelated to rankings. If a page starts appearing for many new, distant queries, the average position gets worse even though nothing was lost. That is often a sign of growing visibility rather than decline.
How to use it well
Filter before you read it. Average position is most reliable for a single query, or a small group of closely related queries, on a single page and in a single country.
- Filter to one query or a regex group of near-identical queries
- Filter to one page when diagnosing cannibalization
- Filter by country and device, since rankings differ
- Read it alongside impressions and clicks, not alone
- Compare equal date ranges
Search Console versus rank trackers
Rank-tracking tools check a keyword from a fixed location and device, usually once a day. Search Console reflects real searches from real users across locations and devices. The two will rarely agree exactly, and neither is wrong; they measure different things.
Example
A worse average that is good news
A hypothetical HR platform publishes a set of new guides. The following month, its site-wide average position drops from 18 to 24, and the marketing lead worries.
Filtering by page shows the existing pages held steady. The new guides have started collecting impressions for hundreds of queries at positions 30 to 60, pulling the average down. Impressions and clicks are both up. The lower average reflects new visibility, not lost rankings.
Common mistakes
Reporting site-wide average position
An average across thousands of queries hides the movements that matter and can move in the opposite direction to performance.
Comparing it directly to a rank tracker
The two use different methods. Differences are expected and do not mean either tool is broken.
Questions
Because it is an average across many impressions where your position varied, for example between 3 and 6 depending on the searcher's location, device or the features shown.
Google's documentation says an AI Overview occupies one position, and all links within it are assigned that same position. Check the current help page, as Google updates these definitions.
