What Does Average Position Mean in Google Search Console? A Guide for New Websites

Open Search Console, click into a query, and the number sitting next to it can look alarming: position 62. Position 88. Sometimes worse. For anyone used to reading numbers as scores, where higher is better, this one runs backwards, and that alone causes more false alarm than almost any other metric in SEO.

Average position is a relative ranking: position 1 is the top result, position 2 is next, and so on, so a lower number is always the stronger one. Google's own definition is more specific than that, though, and the specifics are exactly where the confusion starts. This article works through what the number actually measures, why it can get numerically worse while a site is genuinely improving, and what a growing website should watch instead of refreshing one query's position every morning.

What "Position" Actually Means in Search Console

Google's own Search Console documentation defines position as the topmost position occupied by a link to your site in search results, averaged across every time your property appeared for that query. Two details in that definition matter more than they first appear. First, it's the topmost position: if your site shows up twice on the same results page (which happens, for instance, when a search triggers extra listings from your domain), only the highest of those positions counts, not the average of both. Second, it's genuinely an average, not a single measurement, which is the part that causes most of the confusion this article exists to clear up.

How Google Calculates Your Average Position

Picture one page ranking for one query over the course of a week. It shows up at position 8 once, position 15 once, and position 22 once. Search Console doesn't report each of those separately. It reports the average: (8 + 15 + 22) ÷ 3 = 15. That's the figure that appears next to that query in the Performance report.

Zoom out to the query level, and Search Console is averaging across every instance a page appeared for that query, across whatever date range and filters are currently applied. Zoom out further to a whole page or the entire property, and it's averaging across every query the site appeared for at all, low-competition long-tail phrases and brutally competitive head terms treated identically in the math. That last part is the one most people miss, and it's the reason a sitewide average can move in a direction that has nothing to do with whether the site is actually doing better.

Lower Numbers Are Better: Reading the Scale Correctly

It's worth stating plainly, because the phrasing genuinely trips people up: a lower average position is the stronger one. Position 1 outranks position 10. Position 10 outranks position 50. Position 50 outranks position 90. "High position" is ambiguous enough that it's worth avoiding altogether, since it could mean a high (strong) ranking or a high (weak) numerical value, and those are opposites.

Average Position vs. Impressions vs. Clicks vs. CTR

None of the four core Performance report metrics tell the whole story alone. Read together, they tell you which stage of visibility a page is actually in.

This table covers the classic Performance report, built around traditional blue-link results. Since June 2026, Search Console has also included a separate Generative AI performance report, covering how a site appears inside Google's AI Overviews and AI Mode specifically, using impressions rather than the position metric described here. It's a different surface with its own metrics, not another way of reading average position. If you're trying to work out why your business isn't showing up in ChatGPT or Google's AI Overviews, that report is the more relevant one to check.

Why You Can Get Impressions but Almost No Clicks

This is one of the most common patterns a growing site sees, and it's rarely a sign of a broken title. At position 90, a result is typically sitting several pages deep, if Google's results are even paginated that far by the time a searcher gives up. Search behavior drops off sharply after the first page and drops off again after the first few results on it, so a page can be shown thousands of times and still earn close to zero clicks, purely because of where it's sitting, with nothing about the title or content necessarily wrong at all.

That doesn't mean the title never matters. A weak or mismatched title can absolutely suppress clicks even at a reasonable position. It means the two explanations, poor position and poor title, produce a similar zero-click pattern in the data, and the position is worth ruling out first before rewriting anything, since a title rewrite won't fix a page that almost nobody is scrolling far enough to see.

A Real Example From a New Website

Social Stellor's own website went live around July 30, 2026. In the weeks since, Search Console has shown Google actively discovering pages, generating impressions, and matching relevant queries to the right pages on the site, useful, real signals of progress even before they translate into clicks. Two examples from our own account illustrate what that early stage can look like in practice.

What's genuinely useful about these two rows isn't the position number on its own. It's what the whole picture shows together: Google has correctly matched each query to the page actually written about that topic, both pages are already being shown over a thousand and a few hundred times respectively, and neither has earned a click yet because a position in the 90s puts them far past where most searchers ever look. That's a page waiting on stronger rankings before clicks become likely, not a page with a content or indexing problem.

What a New Website Should Actually Monitor

Sitewide average position is a reasonable number to glance at occasionally, but it's a poor primary KPI for a growing site, for the exact reason covered in the next section. These are more useful signals to actually track, in roughly the order they tend to show up.

Reading Average Position Over Time, Without Overreacting

One of the more counterintuitive things about a sitewide average is that it can get numerically worse while a site is doing something entirely healthy: expanding into more search visibility than it had before.

Illustrative example, not a real case: imagine a site ranking at position 8 for one established query, generating 100 impressions a week for it. Its average position is 8. The site then starts appearing for 20 new, harder queries it's never shown up for before, averaging position 70 across them, adding another 400 impressions a week. The original query hasn't moved at all, and total visibility just roughly quintupled, both genuinely good outcomes, and yet the sitewide average position is now much closer to 70 than to 8, because it's a blended average weighted toward wherever most of the impressions are coming from.

That's precisely why a query-level or page-level trend line, watched over weeks rather than single days, is a far more honest read than one blended sitewide number. Filtering the Performance report to a specific query, page, country or device removes the blending and shows what's actually moving.

When Should You Actually Take Action?

What position data should actually prompt you to do something depends entirely on the pattern, not the raw number. None of the following are universal diagnoses, they're starting points for the right next question.

Common Misinterpretations

• "Position 90 means Google hasn't indexed my page." Not necessarily. A page can be fully indexed and eligible to rank, and still sit at position 90 for a specific, competitive query. Indexing and ranking are separate questions.
• "Zero clicks means my title is bad." Sometimes true, but at very low positions, the position itself is usually the bigger factor. Rule out position before rewriting titles.
• "My sitewide average got worse, so SEO is failing." Often the opposite: it can simply mean the site is now visible for more, harder queries than before, which pulls the blended average down even as real coverage grows.
• "Every new site goes through the exact same fixed process at the same speed." There's no confirmed, uniform system new domains are put through. Starting conditions, competition and content quality all vary, and so does the timeline.

A Practical Search Console Review Checklist

1. Check the Queries tab filtered to your date range, not just the sitewide summary number.
2. Look at position trend over weeks, not the movement between yesterday and today.
3. Cross-reference position against impressions and clicks for the same query, not any one metric alone.
4. Filter by page to see whether a specific page's position is moving, separate from the sitewide blend.
5. Note when new queries first appear; that's an earlier and more useful signal than the position they start at.
6. Save a few important queries to watch specifically, rather than reacting to the single blended average.

Frequently Asked Questions

What is a good average position in Google Search Console?

There's no single number Google defines as "good," since what counts as strong depends heavily on how competitive the specific query is. As a practical reference rather than an official benchmark, positions 1 to 3 are commonly treated as strong visibility, and anything under 10 as page-one visibility for that query. A newer site competing on a difficult term may be doing well simply by moving from position 90 toward position 50.

Is a lower average position always better?

Numerically, yes, a lower position always means a stronger ranking spot. What it doesn't automatically mean is more traffic or business value, since a page at position 8 for a rarely-searched term can produce less than a page at position 15 for a high-demand one. Position is one input, not the whole answer.

Why did my average position get worse while impressions increased?

This usually means the site started appearing for more, and often harder, queries than before. Since the sitewide average blends every query's position together, adding a wave of new, lower-ranking queries can pull the overall number down even while total visibility and query coverage are genuinely expanding.

Why do I have impressions but no clicks?

The most common reason is simply position: results shown far down the rankings, especially past the first page, receive very few clicks regardless of how good the title is. A weak title can also suppress clicks at any position, but it's worth checking where the page actually ranks before assuming the title is the problem.

Should I track sitewide average position or individual queries?

Individual queries and pages, primarily. The sitewide number is a blended average across everything the site ranks for, which can move for reasons that have nothing to do with any one page's real performance. Filtering to specific queries or pages gives a far more honest read of what's actually improving.

How often should I check Search Console position?

Weekly is usually enough to catch a real trend without reacting to normal day-to-day noise. Position data is naturally volatile at a daily level, and checking too often tends to produce anxiety about movement that reverses itself within days, rather than useful information.