Google Search Console’s average position is mathematically defined, but it is not a fixed rank for a keyword or a reliable standalone measure of SEO progress. It averages the topmost position of your property or page across impressions, and the result can shift with the queries, pages, and search-result formats represented in the report.
What average position measures
Google defines position as the topmost position occupied by a link to your property or page, averaged across queries where it appeared. Position is recorded when the result receives an impression. At the property level, if several pages from your site appear for one query, Search Console uses the topmost result; in a page-level view, each URL is counted separately. Google describes position as “a complex metric that can be misleading if you don’t understand the subtleties” in its Search Console Help explanation of impressions, position, and clicks.
As an Amazon Associate I earn from qualifying purchases.
That makes average position a summary of observed appearances, not a stored rank for one keyword on one unchanging results page. A value such as 5 does not mean your page will always appear as the fifth conventional blue link whenever someone searches.
Why one average can tell the wrong story
Search-result layouts do not share one visual ranking scale
A position can refer to different kinds of result placements: a knowledge panel, the first result on a later results page, or a row in image results. In some compound search elements, multiple links can share the container’s position. The number is therefore not directly comparable across every result format as though it described the same visual location.
#1 Best Overall
Property and page views count appearances differently
Property aggregation reports the topmost position for the site, while page aggregation treats URLs separately. If multiple pages from your property appear for a query, the two views can produce different averages. Choose the reporting unit that matches the question: the whole property for a site-level view, or a particular URL when evaluating a landing page.
The mix of impressions can change the average
Because position is recorded when an impression occurs, the queries and appearances included in a period affect its average. A sitewide average can move as the mix of impressions changes, even when your practical question is about one target query or page. This follows from Google’s definition; it does not establish that any particular site has experienced such a change.
Rank #2
A manual search is not a like-for-like check
A live search may differ from the report average because factors such as search history and location affect what you see. Google’s help page captures the familiar discrepancy: “The Performance report says my page position is 5, but when I do a search it’s in position 8!” One search is a different observation, not a direct validation or refutation of the reported average.
Free tools Windows power users keep installed
One-click scans. No signup required.
Visible query rows may not explain chart totals
Search Console omits anonymized query text from query tables for privacy, while anonymized queries can remain in chart totals unless the report is filtered by query. Google Search Central also documents daily row limits in its October 19, 2022 article on Search Console performance data filtering and limits. As a result, adding up visible query rows may not reproduce the chart’s total.
How to make a useful comparison
- Choose the unit first. Decide whether you are assessing the property, a specific page, or a query. Keep that unit consistent; a property-level average and a page-level average answer different questions.
- Open the relevant report views. In Search Console, go to Performance and inspect the Queries and Pages views. Filter to the query or page that matches the business question instead of making a sitewide average the headline KPI. Google’s Performance report guidance explains the available report dimensions and filters.
- Compare equivalent periods and contexts. Use the report’s date comparison and keep country, device, search type, and any relevant search appearance consistent. Google’s Performance report guidance describes date and country comparisons and recommends considering country and device when interpreting performance.
- Read position beside outcomes and exposure. Compare average position with impressions, clicks, and CTR. CTR is clicks divided by impressions. Google recommends inspecting queries with high impressions and low CTR, including the page title and snippet, rather than assuming position alone explains performance.
- Use the trend as a clue, not a complete objective. Google recommends monitoring changes over time, especially sudden changes, alongside absolute position. When reporting an average, state the segment and period it represents so readers know what is being compared.
When combining exported rows
Do not calculate an overall average by taking a plain average of row-level averages when the rows have different numbers of impressions. If the underlying rows represent compatible observations and impressions are appropriate weights, an impression-weighted recomputation is more consistent with averaging across impressions. Keep grouping dimensions aligned, and treat this as an analytical approximation: query filtering and data limits mean an export may not reproduce Search Console’s exact report total.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Which view should you report?
| Decision | Choose this view | Keep consistent |
|---|---|---|
| Is the whole site’s search performance changing? | Property-level Performance report | Date range, country, device, search type, and any relevant appearance |
| Is a landing page changing? | Pages view filtered to that URL | The same URL and report context across periods |
| Is one search term changing? | Queries view filtered to that query, with the relevant page context considered | Query scope, date range, country, device, and search type |
| Is visibility translating into visits? | Position together with impressions, clicks, and CTR | The same segment and comparison period for each metric |
Google’s documentation does not establish a universal numerical error rate for average position. The issue is not that the metric is mathematically incorrect; it is that a single average can conceal differences in unit, query mix, context, and result layout. For a meaningful SEO comparison, define the slice first and interpret position alongside the traffic measures it does not replace.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
