Search Console. Diagnostics
Average Position Dropped in Search Console, but Clicks Didn’t?
Written by Ram Kr Shukla, SEO and growth consultant
Quick answer
Search Console’s average position is the topmost spot your site held, averaged over every impression, so it’s weighted by impressions. When Google starts showing your page for new, broader searches where it sits on page two or three, thousands of deep impressions drag the average down even though none of your existing rankings moved. If clicks are flat or up, compare a fixed set of your core queries across both periods before you call it a drop. If those queries held their positions, nothing got worse. If they slipped and their clicks fell too, the drop is real.
You open Search Console and the average position line has gone the wrong way. It was 8. Now it’s 19. You’ve paid for SEO for six months, and the one number that looks like a ranking just fell off a cliff.
Then you look at clicks. Flat. Maybe up a little.
It’s one of the most common panic emails a local business owner sends, and most of the time nothing broke. The number moved because of what got added to it. Below I’ll walk through how Google computes the figure, why it falls while a site’s growing, and how to tell a fake drop from a real one in about 20 minutes. Then the reporting mistakes that make a small change look scary. It’s the same check I run in my local SEO work for service businesses. Two of them supply the real numbers below, both anonymised: a US roofing and exteriors contractor and a US lawn care and mosquito control company.
How Search Console Calculates Average Position
Google’s Performance report help defines it as “the average position of the topmost result from your site.” That’s one short sentence with three rules buried in it. Every confusing drop comes from one of them.
Say two of your pages show for one search, at positions 4 and 9: the site-level figure records the 4. Because the chart aggregates by property, the 9 never reaches the chart total.
Google’s explanation of how position is recorded says a result needs an impression before its position gets recorded. So if you’re on page 3 and the searcher never leaves page 1, that search doesn’t touch your average. At all.
Position’s recorded per impression, then averaged. A query you showed for 2,000 times pulls on the number 2,000 times as hard as one you showed for once. Hence the name you’ll see people use: impression-weighted average position.
Two quieter details come back later. Every item in a carousel gets the carousel’s position. And the chart is aggregated by property while the Pages table is aggregated by page, so the page rows never add up to the chart total (Google says so on the same help page). Remember that one. It breaks a lot of reports.
The impression-weighted formula
Multiply each query’s position by its impressions. Add those up. Divide by the total impressions.
That’s how you’d roll up a set of keywords yourself. Don’t expect it to match the site figure exactly, though: the chart includes anonymised queries that never show up as rows. The API side of that problem is in why the Search Console API misses keywords.
Why Average Position Falls When Nothing Got Worse
This is called impression dilution. Average position is a ratio, and when the bottom of it fills up with deep impressions, the result gets worse even if every ranking you had stays exactly where it was. Five things tend to add those deep impressions.
Google is testing your page in broader searches
When a page starts doing well for a specific term, Google often tries it in wider searches: a shorter head term, a national version of a local query, an adjacent service. Those tests usually land somewhere between position 15 and 30. Lots of impressions. Almost no clicks. And every one of them counts toward the average. With local service businesses, a lot of these test impressions come from outside the service area, which has its own diagnosis in why local service pages get impressions from outside their area.
New pages are ranking for long-tail terms
Publish ten new service or blog pages and they won’t enter at position 4. They’ll enter at 40, 60 or 80 for hundreds of long, specific queries, each one adding a few impressions at a deep position. Individually tiny. Together, they can hold the site average down for months. That’s just what a growing site looks like, and the honest SEO timeline lays it out month by month. It’s also where the position 11 to 100 trap lives: a site ranking for thousands of terms on pages two to ten and getting almost nothing from them.
Demand shifted between your queries
If the query you rank best for gets fewer searches this month, it contributes fewer impressions, and your weaker queries take a bigger share of the weighting. Your rankings stayed put while the mix underneath them changed. Roofing and lawn care both swing hard with the weather and the season, so expect some of this every spring and fall.
Your device or country mix changed
Mobile and desktop rank differently, and so do countries. A jump in mobile impressions, or in searchers from outside the US, shifts the blend, so filter by device and by country before you trust the headline number.
Google changed what gets counted
This one runs in both directions. In September 2025 Google stopped supporting the num=100 results parameter that rank-tracking tools used to load 100 results at once. Lots of sites saw impressions fall and average position improve overnight while clicks stayed put (Search Engine Land covered the change). Nobody’s rankings got better that week. Google was simply logging fewer deep impressions, which is the same arithmetic running backwards.
A Worked Example: Same Rankings, Worse Average
Here’s the arithmetic with round numbers, for a made-up roofing site over two 28-day periods. Three queries bring in the work. In the second period, Google starts testing one page in broader searches.
| Query | Impr. before | Pos. before | Impr. after | Pos. after |
|---|---|---|---|---|
| gutter repair | 400 | 3 | 400 | 3 |
| roof leak repair | 300 | 6 | 300 | 6 |
| soffit repair | 300 | 8 | 300 | 8 |
| New broad test queries | 0 | none | 2,000 | 28 |
| Site total | 1,000 | 5.4 | 3,000 | 20.5 |
Before: 400 times 3, plus 300 times 6, plus 300 times 8, comes to 5,400. Divide by 1,000 impressions and you get 5.4.
After: the same 5,400, plus 2,000 times 28, which is 56,000. That’s 61,400 over 3,000 impressions. Average position 20.5.
The chart says the site fell 15 positions. Not one of the three queries the business cares about moved. Clicks went from 65 to 67, because the test queries picked up two stray clicks.
Two more things fall out of the table. Average the four position values straight (3, 6, 8 and 28) and you get 11.25, which matches nothing, so you can’t rebuild Google’s number by averaging rows. Now compare only the three queries that existed in both periods: the set average is 5.4 both times. Honestly, that fixed-set comparison is most of the diagnosis.
What It Looked Like for a Roofing Contractor
Here’s the real version, from a US roofing and exteriors contractor I work with. The owner asked why their soffit repair ranking kept going down. In Search Console, that query’s average position on its service page had slid to 19.7.
Split it by day and you get two kinds of day. On quiet days it got 3 to 10 impressions, at positions 5 to 7 early in the window and 7 to 9 three months later. The spike days came in three bursts (the longest ran 16 days), and on those it got 50 to 150 impressions a day at positions 17 to 25. Zero clicks. That was Google testing the page in broader searches, mostly outside the area the company serves. Spike days carried so many more impressions that they pretty much set the average on their own.
Meanwhile the page was doing better than ever. Quarter on quarter, impressions went from 8,170 to 32,053 and clicks from 29 to 55. The technical side was clean too: indexed, correct canonical, review rich result passing. And an older page that used to compete for the same term had dropped to a single query, so it wasn’t cannibalisation either.
But not everything was dilution, and this is the bit to copy. On the quiet days the page really had slipped 1 to 3 spots. One local-modifier query (the service plus the town) had sat at position 2 with 25 impressions, and it had stopped appearing at all. A real slip, hidden under a fake one. If you only stared at the 19.7, you’d worry about the spike days and miss the query that went missing.
The next 28-day comparison showed the reverse. As the broad fascia repair test impressions faded, the page’s impressions fell from about 12,600 to 7,200, and its average position barely moved (11.6 to 11.9). Site clicks dipped from 211 to 188 the same month. That looked bad until brand and non-brand were split out: about 17 of the 23 lost clicks were people searching the company’s name, down from 41 to 24, and non-brand clicks were roughly flat. That split is covered properly in branded vs non-branded traffic.
How to Diagnose an Average Position Drop
Run these in order. You need Search Console, about 20 minutes, and a spreadsheet for the last step.
Open the Performance report, pick the last 28 days and use Compare against the previous period, or the same period last year if your business is seasonal. Turn on all four metrics. Position down with impressions up and clicks flat or up is the dilution signature. Position down with clicks down needs the rest of these steps.
Use Compare mode, or two exports made in the same sitting. Never work out one period from another. Leave out the most recent two or three days, because fresh data is preliminary and it fills in over the following hours and days.
On the Queries tab in compare mode, sort by current impressions. Queries with impressions now and none or almost none before, sitting at position 15 or deeper, are your dilution. If most of the impression growth is in those rows, you’ve found the cause.
Pick the 10 to 30 queries that actually bring you work: your services, your services plus your area, and the terms that have earned clicks. Compare their positions one by one across both periods, then roll the set up weighted by impressions. If the fixed set held, your rankings held.
Switch to the Pages tab. One or two pages usually account for most of the new impressions. Click into each one, go back to Queries, and repeat the new-query and fixed-set checks for that page alone.
For any query that looks like it dropped, view the chart by day and look for spike days. Note the position on quiet days and on spike days separately. Quiet days at your usual position plus spike days much deeper means Google is testing the page, and the average is lying to you.
Export the query table for both periods and add up impressions in four buckets: positions 1 to 3, 4 to 10, 11 to 20, and 21 and deeper. If the top two buckets held and only the deepest one grew, it’s dilution. If impressions moved out of the top 10 into the lower buckets, the drop is real. Run the same check with the device and country filters if the numbers still don’t make sense.
Step 3 or step 4 explains most drops. Steps 5 to 7 are for mixed answers, like the roofing case, where dilution and a small real slip were sitting inside the same number.
When the Drop Is Real
Dilution is common. It isn’t guaranteed. Treat it as a real ranking loss when you see any of these.
Signs it’s a real drop:
- Your fixed set of money queries lost positions, and the site average isn’t the only thing that moved.
- Clicks fell on those same queries, especially ones that used to sit in the top 5.
- In your position buckets, impressions moved out of 1 to 10 and into 11 to 20.
- The ranking URL for a query changed, or two of your pages now share it. That’s cannibalisation, and here is how to confirm it in Search Console.
- A local-modifier query (service plus town) disappeared, like the one in the roofing case.
- The timing lines up with a confirmed update on the Google Search Status Dashboard.
- URL Inspection shows the page has an indexing or canonical problem.
Google’s own guide to debugging Search traffic drops separates a small drop in position from a large one, and suggests looking at queries, pages, countries and devices one at a time. Do that for your fixed set and you’ll know which kind you’ve got. If it’s real, start with six real causes of a rankings drop. On local sites, the most common one is a change somebody made to the site.
Never Subtract One Date Range From Another
This is the mistake that turns a modest change into a headline. It happened while preparing a monthly report for a US lawn care and mosquito control company, and a recheck caught it.
The report needed first-half and second-half impressions for a rebuilt aeration page. The full month showed 1,115 and the second half 890, so by subtraction the first half was 225. Then a direct pull for the first half returned 609.
Search Console numbers don’t add up the way you’d expect. Page data is counted differently from property data, rare queries get anonymised and left out of query rows, and each date range is calculated on its own. On that site, for the same window, the page rows came to 3,838 against a site total of 3,404.
And the knock-on was big. The draft said the rebuilt pages’ impressions rose 325%. The true figure was 39%. It had the aeration page climbing 25 positions. It climbed 6. Still good news, just smaller. But a client who checks the numbers later will remember the gap.
Freshness bites too. One day’s data went from 0 clicks and 30 impressions in a morning pull to 3 clicks and 215 impressions that evening. Google flags recent data as preliminary in the Performance report, and it does move.
Reporting rules that prevent this:
- Pull every period you report directly, in one sitting, including both halves of any comparison. A Compare export does that in one file, and the content decay finder reads it as it downloads.
- Don’t subtract periods, and don’t add page rows together to get a site total.
- Don’t average position rows by hand. Weight them by impressions, or use the figure Search Console shows for that exact filter.
- Re-pull everything right before the report goes out, and footnote any projected days.
- Search the site before you write that no page ranks for something. The same recheck found a dethatching page that had sat at position 10 the whole time.
What to Report Instead of Average Position
On its own, average position makes a weak headline for a local business. Oddly, it rewards sites that rank for fewer things. Put these in the monthly report instead, or at least next to it.
The cleanest sign that more people found you without already knowing your name. Branded swings, like the 41 to 24 in the roofing case, shouldn’t hide in the total.
Your 10 to 30 money queries, weighted by impressions, same set every month. When rankings move, this moves.
Impressions in positions 1 to 3, 4 to 10, 11 to 20 and 21 and deeper. Growth in the deepest bucket is just new reach. Shrinking top buckets are the ones to worry about.
Where you can track them. They’re what the owner is actually paying for.
If you keep average position in the report, put impressions right beside it, so anyone reading can see when the bottom of the ratio grew. One more thing. The new queries that caused the dilution deserve a second look, because some of them are services you don’t have a page for yet. The service page gap analysis in Search Console turns that list into a build plan.
“An average position drop with flat clicks usually means Google is showing you to more people, not fewer. Your fixed set of queries tells you which.”
Ram Kr Shukla, SEO and Growth Consultant
Average Position FAQ
Why did my average position drop in Search Console?
Usually because your site started showing up for more searches where it ranks deeper, such as broader terms Google is testing your page for, or long-tail queries for new pages. Those impressions get averaged in and pull the number down. If your core queries held their positions and clicks are steady, nothing got worse.
Why did my average position go down but clicks stayed the same?
Your clicks come from the queries where you rank near the top, and those didn’t change. The new impressions sit on page two or three, where almost nobody clicks, so they move the average without moving clicks. That pattern is called impression dilution.
Is Search Console average position weighted by impressions?
In effect, yes. Search Console records the topmost position of your site each time it gets an impression, then averages those. A query with thousands of impressions moves the figure far more than a query with a handful.
Does a lower average position mean my rankings dropped?
Not necessarily. Compare a fixed set of your important queries across both periods. If those held their positions, your rankings held, and the site average fell because new, deeper impressions were added to it.
How do I calculate average position for a group of keywords?
Multiply each keyword’s position by its impressions, add the results together, and divide by the total impressions for the group. A simple average of the position values gives you a number that matches nothing in Search Console.
Can I subtract one date range from another in Search Console?
No. Search Console totals aren’t additive, so a period you work out by subtraction can be badly wrong. In one client report, subtraction gave 225 impressions for half a month and a direct pull for the same days gave 609. Pull every period directly.
When is an average position drop a real problem?
When your fixed set of money queries loses positions, clicks fall on those same queries, impressions move out of the top 10, or an important local query disappears. Check whether the ranking URL changed and whether the timing matches a confirmed Google update.
Why did my average position improve while impressions fell?
It’s usually the same effect in reverse: fewer deep impressions are being counted. When Google stopped supporting the num=100 results parameter in September 2025, many sites saw impressions fall and average position improve, with clicks unchanged.
Not sure whether your drop is real?
I run this check for local service businesses every month: fixed query sets, position buckets, brand split, and the pages Google is testing. Send me the property and I’ll tell you which kind of drop you’ve got.
Local SEO ServicesRoofing SEOMore on reading Search Console for a local business: impressions from outside your service area, finding service pages you should build, and location pages that never get indexed. For keyword rollups through the API, see why the numbers don’t add up.
Tags: Search ConsoleLocal SEOSEO ReportingDiagnostics
Written by Ram Kr Shukla
SEO and growth consultant and Fractional Chief Digital Officer with 20+ years in SEO and growth across 50+ brands. Google Analytics and Google Ads certified. Works in Search Console every day for local service businesses, including roofing, lawn care and dental practices, and for e-commerce and enterprise sites.




