Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

Google Search Console’s average position is mathematically defined, but it is not a fixed rank for a keyword or a stable measure of SEO progress on its own. It averages the topmost position of your property’s result across impressions, and the number can change with the queries, pages, devices, countries, and result layouts represented in the report.

That explains why Search Console might report position 5 while a manual search appears to show position 8. Google itself cautions that “The position value is a complex metric that can be misleading if you don’t understand the subtleties.” The practical fix is not to discard the metric: compare equivalent slices of data and read position alongside clicks, impressions, and click-through rate.

What does average position in Search Console measure?

In the Performance report, position is the topmost position occupied by a link to your property or page when it receives an impression. Search Console averages those positions across the relevant impressions and queries. It is a summary of observed appearances—not a stored, universal rank for one keyword on one unchanging search results page. Google’s explanation is in Search Console Help: “What are impressions, position, and clicks?”.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

For example, a property may appear at different positions across multiple queries and search appearances during the selected period. Its average position compresses those observations into one number. A single query can also show more than one page from the same property; the property-level figure uses the topmost result.

Why can the average be misleading?

A position is not always a conventional blue-link rank

Search results include different formats and layouts. Depending on the result, a position can refer to a knowledge panel location, the first result on a later page, or a row in image results. Several links inside a compound result element can share its position. Thus, the same numerical position does not necessarily describe the same visual location across searches.

Property and page views count appearances differently

At the property level, Search Console reports the topmost position for the property. At the page level, each URL is counted separately. If multiple URLs from the same property appear, the two views can produce different average positions. Choose the view that matches the question: a property-wide view is not interchangeable with a particular landing page’s view. See Google’s documentation on Performance report data.

The average includes only appearances that generated impressions

Position is recorded when an impression occurs. As the mix of queries and appearances that receive impressions changes, the average can move even if you are trying to assess one page or target query. This is a consequence of what the metric summarizes; it does not by itself establish that a particular page gained or lost rank.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A manual search is not the same observation

A live Google search may differ from the report average because results can vary with factors such as location and search history. One search from your browser is therefore not a direct validation or refutation of a period-wide Search Console average.

Visible query rows may not include every query

Google omits anonymized query text from tables for privacy, while anonymized queries can still be included in chart totals unless the report is filtered by query. Search Console also applies daily row limits. The visible query rows may therefore fail to add up to the chart’s totals. Google explains these behaviors in its October 19, 2022 article on Performance report filtering and limits.

How to analyze average position more reliably

  1. Choose the unit first. Decide whether you are assessing the whole property, a specific page, or a particular query. Keep that unit consistent across comparisons.
  2. Open the relevant report rows. In Search Console, go to Performance and inspect the Queries and Pages tabs. Filter to the query or URL tied to your business question instead of using a sitewide average as the main KPI.
  3. Compare equivalent periods and contexts. Use the report’s date comparison, and keep country, device, search type, and relevant search appearance consistent. A period with a different geographic or device mix may not be a like-for-like comparison. Google’s guidance on using the Performance report is in Search Console Help.
  4. Read position alongside outcomes and exposure. Review clicks, impressions, and CTR with position. CTR is clicks divided by impressions. For queries with many impressions but few clicks, examine the result’s title and snippet as well as its position; Google recommends this kind of review in its Performance report guidance.
  5. Interpret movement over time. Use position as a trend clue and investigate sudden changes, rather than treating one average as a complete measure of success. When reporting an average, identify the page or property, query scope, period, country, device, and search type behind it.

Can you recompute an average from exported rows?

Be careful when combining row-level averages. A plain average of averages gives each row equal weight, even when the rows represent different numbers of impressions. If the underlying rows describe compatible observations and impressions are the appropriate weights, an impression-weighted recomputation is more consistent with the metric’s definition.

That calculation still may not reproduce Search Console’s exact total. Grouping dimensions must align, and privacy filtering or row limits can leave query data incomplete. Treat a recomputed figure as an analysis of the available rows, not as proof that the report total is wrong. Google describes the metric’s averaging and query-data limitations in its position and impressions documentation and its article on filtering and data limits.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Which Search Console view should you report?

Reporting question Use this view Keep comparable
How is the site performing overall? Property-level Performance data Date range, country, device, search type, and query scope
How is a landing page performing? Filter the Pages view to that URL The same URL, period, and context dimensions
How is a target query performing? Filter the Queries view to that query The query, page scope, period, and context dimensions
Are search appearances producing visits? Position together with impressions, clicks, and CTR The same segment and period when comparing outcomes

These views answer different questions. A property average can be useful for a broad trend, but it should not be presented as though it were the rank of one page for one keyword. Likewise, Search Console’s impressions, clicks, and average position describe its recorded search performance; a separate rank observation does not replace those first-party report measures.

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.