What "average position" in Search Console really means, and why 8 isn't always page one

10 min read·22 October 2026

Search Console average position is the highest spot your site took in Google's results, averaged over every time someone saw it. It isn't your ranking. An average position of 8 can be a page that sat at 3 on busy days and 18 on quiet ones, and never once appeared eighth. So treat 8 as "somewhere around page one, on average", then look underneath it before deciding anything.

This post explains exactly what Google averages, why the chart and the table give different numbers, and how to see the real positions hiding behind a single figure.

Key takeaways

• Search Console average position is the topmost result from your site, averaged over every impression, not over days or searches.
• An average of 8 can be a mix of page-one and page-two appearances, so it isn't proof you're on page one.
• The chart shows your whole site's best result per search; the table shows each page or query, so judge posts from the table.
• Filter to one page and one query, then switch the chart to Daily, to see the real positions behind an average.
• AI Overviews count as one position, and their links are included in the Web search type.

What Search Console's average position actually measures

Google's Performance report help defines it in one line: "The average position of the topmost result from your site." Three words in that sentence do a lot of work.

Topmost. If two of your pages appear for the same search, at 4 and 9, Search Console counts 4. Your second result doesn't drag the number down.

Result. Google counts positions by element on the page, not by blue link. Its guide to impressions, position and clicks says each element "occupies a single position, whether it contains a single link or many". An AI Overview takes one position, and every link inside it gets that same position. A knowledge panel on the right-hand side gets a position number too.

Average. The same guide says the metric "averages the position value for all impressions". It's averaged over appearances, not over days or over searches. A day with 200 impressions counts twenty times as much as a day with 10.

There's one more rule that changes how you read it: "A link must get an impression for its position to be recorded." If your page sits on page 3 for a search and nobody scrolls that far, that search adds nothing to your average. We covered what that does to brand-new posts in how to measure blog performance in Search Console. Here the point is narrower: the average only describes the times you were seen.

Why an average of 8 isn't always page one

Here's a made-up example to show how the arithmetic works. Say one of your posts gets 150 impressions in a month for a single search:

Days

Where it appeared

Impressions

Positions added up

Weekdays, busy

3

100

300

Weekends, quiet

18

50

900

Total

150

1,200

1,200 divided by 150 is 8.0. Search Console reports position 8. The post was never eighth. Two-thirds of the time it was near the top of page one, and a third of the time it was on page two.

The same thing happens when you average across different searches, devices or countries. A post at 2 on mobile and 15 on desktop can average out at something that looks like a respectable page-one spot.

There are also three reasons "position 8" and "page one" don't line up even when the number is accurate:

• Page one isn't ten blue links. Because AI Overviews, carousels and panels each take a position, the eighth element on the page can be well below where people stop scrolling.
• The number can mean different things. Google's own position guide gives examples where a position of 11 could be the top of a desktop knowledge panel, or a row of image results visible without scrolling, and warns "you should not make simple assumptions".
• Results differ by person. The same guide notes that your position for a given search "might be different than the average because of many variables, such as your search history, location, and so on." Searching your own keyword and seeing yourself at 12 doesn't mean the report is wrong.

Chart vs table: why the two numbers don't match

Open Performance and you'll see an average position above the chart and another next to each row of the table. They're calculated differently.

According to Google's Performance report help:

• In the chart, the value is the average position of the topmost result from your entire site.
• In the table, it's the average position for the specific URL, query or other row you're looking at.

On the Pages tab, data is aggregated by page. On the Queries tab, it's aggregated by property, which means by site. So the site-wide figure in the chart is usually better than most of your individual pages. For any search, it takes your best-placed page, and for a small blog that might be the home page on brand searches.

That's why a site average of 6 can sit alongside blog posts that are all in the 20s and 30s. The chart is telling you about your best result per search, not your typical post.

The practical rule: never judge a single post by the number above the chart. Filter to the post first.

How to see the real positions behind an average

To find out whether an 8 is a steady 8 or a mix of 3s and 18s, break it down. All of this happens in Performance > Search results.

1. Filter to one page. Add a Page filter with the post's full URL. Now the chart shows that page only.

2. Then filter to one query. Open the Queries tab and click the search you care about. Google's common tasks guide describes this: clicking a query "filter[s] all report data to the selected query". You're now looking at one page for one search, which is as close to a single ranking as Search Console gets.

3. Switch the chart to Daily. Turn off every metric except Average position and look at the shape of the line. A flat line at 8 means the post really sits around 8. A line that jumps between 3 and 18 means you're averaging two different situations.

4. Check the Dates tab. It lists each day's impressions and position. Days with high impressions and good positions are your "page one" days. Days with few impressions and poor positions are the page-two days pulling the average down.

5. Compare devices. Use the Compare option for Mobile vs Desktop. It's common for a post to rank noticeably differently on each.

If you're working with a blog that gets very few impressions, the daily line will be noisy whatever you do. Switch to Weekly, which Google says smooths out "daily fluctuations (like those caused by weekends or holidays)", and look for a trend over a couple of months instead.

How AI Overviews and AI Mode affect the number

AI features are counted in the same report. Google's AI features documentation says pages that appear in AI Overviews and AI Mode are reported in the Performance report "within the 'Web' search type", so they're already in your average position.

The rules for how they're counted are in Google's position guide. An AI Overview "occupies a single position in search results, and all links in the AI Overview are assigned that same position." In AI Mode, position "follows the same methodology as a Google Search results page", and a follow-up question counts as a new search.

That has two practical effects. A post that's linked from an AI Overview near the top of the page can show a strong position even if its ordinary blue link is further down, because Search Console takes your topmost result. And because the Overview counts as one position, the blue links below it are numbered from the next position down.

If you want to see AI features on their own, Search Console's generative AI performance report shows impressions in AI Overviews and AI Mode by page, country, device and date. It doesn't show positions, so use it alongside the main report rather than instead of it.

What counts as a good average position

There's no single good number, because it depends on what you're looking at. A rough guide for one post and one search:

Average position (one page, one query)

What it usually means

What to do

1–3

You're at or near the top

Work on the title and description if clicks are low

4–10

Page one, but below the top results

Improve the post; this is where a refresh pays off

11–20

Close to page one, often a mix of page one and page two

Check the daily line, then strengthen the post

21+

Google connects you with the search, but weakly

A new or rewritten post may do better than a tweak

The 4–20 band is what people call striking distance. We've written a full guide to striking distance keywords in Search Console, including which ones to work on first.

Google's own advice on position is less about thresholds and more about movement. Its position guide recommends that you "monitor change in position over time, particularly sudden position changes, as well as absolute position." A post moving from 15 to 9 over two months is telling you more than a post sitting at 7.

Mistakes to avoid when reading average position

Reading the site average as your blog's ranking. It mixes every page, including your home page on brand searches. Filter to the blog or to a single post.

Comparing a new post with an old one. A new post may only be seen for a handful of small searches, which can give it a flattering average. Wait until it has enough impressions to judge.

Reacting to a single day. One bad day on a quiet search can move a small site's average a long way.

Assuming lower is always better for the business. Position 2 for a search nobody makes is worth less than position 9 for one your customers type every day. Look at impressions alongside position.

Forgetting that an AI Overview has a position. If one appears above the results and links to you, you're credited with its position. If it appears and doesn't link to you, everything below it has moved down a place.

Putting it to work

Once you can see what an average is made of, it becomes useful. A post that's genuinely around 8 for a valuable search is a candidate for a refresh. One that bounces between 3 and 18 might need a clearer answer to the exact search. Our guide to refreshing old blog posts with Search Console data covers what to change once you've picked a post.

If you'd rather not do the filtering by hand, Blog AI reads your data through its Google Search Console integration. Its search opportunities list flags searches at an average position of 4–20 with at least 100 impressions in 28 days, with the page that ranks for each.

Your next step: pick the post with the most impressions on your blog, filter Performance to that page and its top query, and switch the chart to Daily. Whatever the line looks like, you'll know more than the single number told you.

Frequently asked questions

What does average position mean in Google Search Console?

It's the position of your site's highest result for a search, averaged across every time that result was seen. Position 1 is the top of the page. Each page element, such as an AI Overview or a carousel, takes one position. Searches where nobody saw your result add nothing to the average.

What is a good average position in Google Search Console?

For one page and one search, 1 to 3 is near the top, 4 to 10 is on page one but below the leaders, and 11 to 20 is close to page one. Google recommends watching how position changes over time rather than fixating on one number, so a post moving from 15 to 9 is a good sign.

Why is my average position different from what I see when I search?

Google personalises results by location, device, search history and more, and the report averages every impression across all of those situations. Your own search is one example among many. Use Search Console's filters for one page and one query, then the Daily view, to understand the range.

Why does the average position in the chart differ from the table?

The chart shows the topmost result from your whole site for each search, so it uses your best-placed page. The table shows the position for each row, such as a single URL or query. That's why a site average can look much better than any individual blog post.

Drafted with AI assistance, edited, and source-checked by hand. Published and measured with Blog AI.