What "Average Position" in Search Console Really Means

Average position is one of the most watched metrics in Google Search Console, and one of the most misunderstood. Founders open the Performance report, see a site-wide average position of 62 and conclude that their pages usually rank on the seventh page of Google. Or they see the average improve from 40 to 30 and celebrate, without noticing that clicks went down over the same period. Neither reading is quite right. The meaning of average position in Search Console depends heavily on how the number is calculated and which queries feed into it.

Once you understand the calculation, the metric becomes much more useful. At the level of a single query or page, it is a reasonable guide to where you stand. At the level of a whole site, it is mostly a summary of which searches Google is showing you for, and it can move in the opposite direction to your actual performance. This guide explains how the number is built, why site-wide averages mislead, when movements in either direction can be misleading, and how a small SaaS team should actually use it.

How average position is calculated

Every time your site appears in a Google search result and that result is counted as an impression, Search Console records the position of the topmost result from your site in that search. If one of your pages appears in third place, the position for that impression is three. If two of your pages appear, in third and seventh place, Search Console records three, because it uses the highest-ranking result from your site.

Average position is then the average of those recorded positions across all impressions in the period you have selected. That has three important consequences.

First, it is weighted by impressions. A query that generates a thousand impressions influences the average ten times as much as a query that generates a hundred. Your average is dominated by whatever searches you appear for most often, not by the searches you care about most.

Second, it includes every query you appear for. That covers your core commercial terms, but it also covers long-tail searches where you rank on page five, loosely related queries Google is testing you for and occasional odd matches you would never have targeted. All of them count.

Third, because only the topmost result from your site is counted per search, adding a second ranking page for the same query does not change the position for that query unless the new page ranks higher than the existing one.

Why site-wide averages mislead

A simple example shows the problem. Imagine a site that ranks in position three for a query with 100 impressions and in position 80 for a query with 1,000 impressions. The weighted average lands well above 70, because the low-ranking query has ten times as many impressions. Yet the site is doing well for the first query, which might be the one that brings in signups. The site-wide average describes neither query accurately.

Real sites have thousands of queries, and the same effect happens at scale. Newer sites often show high site-wide averages, somewhere in the range of 50 to 70, because Google tests them for many queries deep in the results while it works out what they are about. This is normal and not a sign of failure. A new SaaS blog with a few dozen posts can easily appear for hundreds of loosely related searches on pages four through nine, and those impressions will dominate the average even if a handful of posts are already ranking on page one.

The practical lesson is that the site-wide average position is closer to a description of the shape of your visibility, heavily influenced by the long tail of queries where you barely appear.

When average position improves but clicks do not

Because the average depends on which queries you appear for, it can improve for reasons that are not good news.

The most common case is losing visibility for low-ranking queries. If your site stops appearing for a large group of searches where it ranked in position 70 or 80, those impressions disappear from the calculation. The remaining impressions, from queries where you rank higher, now make up a bigger share, so the average moves up. On a chart, it looks like progress. In reality, you are appearing in fewer searches, and total impressions have fallen.

Another case is a shift toward branded queries. If more of your impressions come from people searching for your company name, where you naturally rank first, the average improves even if your visibility for non-branded commercial terms has not changed at all. This often happens after a launch, a press mention or a busy month of outbound, when more people search for you by name.

In both cases, the fix is the same: always look at clicks and impressions alongside position. An improving average with falling impressions is a warning sign, not a win.

When average position worsens but things are fine

The reverse also happens. Average position can get worse when your site starts appearing for many new queries at low positions. This is common as a site grows. Publishing new content, earning links or building topical authority often leads Google to test your pages for a wider range of searches, initially deep in the results. Those new impressions pull the average down.

From a growth perspective, this is often a healthy sign. More impressions at low positions can mean Google is beginning to associate your site with more topics. Some of those queries will move up over time, especially if you strengthen the pages involved. If clicks and total impressions are rising while average position worsens, you are probably expanding your footprint rather than losing ground.

How to use average position well

Look at query level

Filter the Performance report to specific queries. The average position for a single, relevant query is much more meaningful than a site-wide figure, because it reflects where you stand for that search rather than a mix of everything. For a SaaS company, start with your core commercial terms, such as category and use-case searches, and the comparison or alternative queries that bring in evaluators.

Look at page level

Check average position for your most important pages, such as the homepage, key landing pages and top blog posts. Then look at the queries each page ranks for. You will often find that a page ranks well for a few relevant queries and poorly for many marginal ones, which tells you where its real strength lies.

Filter by country and device

Positions can vary by location and device. A page might rank well on desktop in the United States and less well on mobile in another market. If your customers are concentrated in particular countries, filter to those countries so the numbers reflect the audience you actually serve.

Use longer date ranges

Daily positions fluctuate for reasons that have nothing to do with your work: personalization, result testing, new competitors and small algorithm adjustments. Comparing one day to the next mostly measures noise. Compare 28-day or three-month periods instead, and compare like with like, such as one quarter against the previous quarter.

Pair it with clicks and impressions

The most useful view combines all three metrics. Rising impressions and clicks, with stable or improving positions for your target queries, is a healthy pattern. Falling impressions with improving average position suggests lost visibility. Rising impressions with worsening position suggests expansion into new topics. Reading position on its own will lead you astray far more often than reading it in context.

A practical example (illustrative)

A new SaaS blog shows a site-wide average position of 62.5, with several thousand impressions over the past three months. Looking at that number alone, the team might decide the content strategy is not working.

Filtering by query tells a different story. A small group of long-tail queries ranks between positions 8 and 15. These are specific, relevant searches, such as how to calculate a particular metric for a particular kind of business. Many other queries rank between 50 and 90, and most of them are broad or only loosely related to the product.

The right response is to strengthen the pages ranking in positions 8 to 15, since those are close to page one and a modest improvement could bring meaningful clicks. That might mean expanding the content, improving titles, adding internal links from related posts or answering follow-up questions more directly. The team should also build new content around queries that are already generating impressions, since those show what Google is willing to associate with the site. Worrying about the site-wide average would only distract from that work.

How to report it to your team

If you share SEO numbers with a founder, a board or a wider team, avoid putting site-wide average position on the summary slide. It invites exactly the misreadings described above, and you will spend the meeting explaining why a worse number is good news. Instead, report clicks and impressions for the whole site, then show position for a short, fixed list of target queries that matter to the business. Keep that list stable from month to month so changes are comparable.

When position for a target query moves, add a sentence of context: whether the page was updated, whether a competitor published something new or whether the change is within normal fluctuation. That small habit turns position from a confusing number into a useful signal, and it helps everyone focus on the pages and queries where effort will actually pay off.

Common mistakes

The most common mistake is treating the site-wide average as a ranking, as if the whole site sits in one position. Another is comparing daily numbers and reacting to normal fluctuation. Teams also go wrong when they ignore impressions and clicks and read position in isolation, which is how improvements caused by lost visibility end up being celebrated. A related mistake is setting goals around site-wide average position, which encourages the wrong decisions. Goals tied to clicks, conversions from organic traffic or positions for specific target queries are far more useful.

The takeaway

Average position is an impression-weighted average of your topmost result across every search you appear in, so the site-wide figure often says more about the range of queries you show up for than about how well you rank. Use it at the query and page level, filtered to the countries and devices that matter, over periods of at least a few weeks and always alongside clicks and impressions. Read that way, it becomes a useful guide to where your next improvements should go.