What does average position mean in Search Console?
Average position summarizes the topmost position of a result from your property or page across recorded impressions. A lower number means a higher position. It is an average of observations, not a fixed rank for your whole website.
The scope matters: a property-level report and a report filtered to a specific page need not describe the same set of results. Google also counts positions differently for some result formats. Its position methodology explains those details.
Looking for a target? See what counts as a good average position for concrete verdicts and which pages to work on first. This guide explains how the number is calculated and why it can move.
Your average can get worse while you reach more people
Suppose a site has one established group of searches. In the next period, it keeps those positions and also starts appearing for a new group.
| Group | Previous period | Current period |
|---|---|---|
| Established searches | 1,000 impressions at position 3 | 1,000 impressions at position 3 |
| New searches | No impressions | 1,000 impressions at position 30 |
The earlier average is 3. The new average is 16.5:
(1,000 × 3 + 1,000 × 30) ÷ 2,000 = 16.5
Nothing in the established group lost a position. The aggregate changed because the site gained impressions at lower positions. That could be useful new reach, irrelevant exposure, or a mixture of both. The average alone cannot decide which.
The reverse is possible too. If those lower-position impressions disappear, the average improves to 3, even though the site is being seen less often. This is why reading a ranking badge in isolation can send you in the wrong direction.
This example assumes complete, non-overlapping groups with the same report scope. Do not average arbitrary exported rows and expect to reproduce the property total.
Compare a stable group before interpreting the average
Pick a page that matters to you, then choose a specific query or a small group of similar queries. Keep the search type, country, device, and date windows consistent. Now the comparison is closer to “Did this page become less visible for this search?”
Read clicks and impressions alongside position. If the position number gets larger while clicks and impressions also fall for the same group, you have a clearer reason to investigate a loss of visibility. If impressions expand and clicks grow, first inspect the new queries before treating the overall average as a setback.
Google recommends looking at click and impression trends alongside position. You can use the regex builder to keep a defined set of query variants together, then use the same filter in both periods.
Save the scope with your observation: page, query group, device, country, and dates. That makes it possible to repeat the check. A screenshot of an unexplained average gives the next person much less to work with.
Common questions about average position
Why does my own Google search show a different rank?
Your search is one observation; the report combines many. Results can vary with location, device, time, and search context. Google discusses this mismatch in its position documentation.
Does position 11 always mean page two?
No. Different result layouts complicate that interpretation. Treat position as a relative reporting measure, rather than an exact pixel location or a guarantee about which results page a person saw.
What should I do when position barely changes but clicks fall?
Check the impression count and query mix first. A similar average can conceal different movements inside the report. Work through the clicks-down, impressions-up example if exposure increased; use the CTR calculator to put numbers on the change.