Average Position, Google Search Console

The average ranking position across all your queries, where sustained drift signals a ranking algo update or content decay. How to read it, why it matters, and how to act on it.

Metrics type: Key Metrics • Category: Search Performance

Average ranking position across all queries. Sustained position drift = ranking algo update or content decay.

At a glance

Average Position is the impression-weighted mean of where your results appeared in Google search across every query, over the trailing 30 days versus the prior period. Lower is better: position 1 is the top organic result, position 11 is the top of page 2. It is the headline read on your overall ranking strength. A sustained rise in the number (your results sliding down) signals a ranking algorithm update or gradual content decay, often before clicks visibly fall. The card is a gauge showing the average position with an arrow against the prior period.

What it tracks	The average position of your property’s results across all queries, weighted by impressions. Google records the position of your highest result for each query on each search; the property figure is the impression-weighted mean of those. A move from 8.5 to 9.5 means your average appearance slipped roughly one place down the page.
Data source	Google Search Console Search Analytics (Performance report), the property-level Average position metric, read via the Search Analytics API.
Why it matters	Position is the input to almost everything else in organic search: clicks, CTR, and revenue all hinge on where you appear. Watching the property average gives an early, aggregate read on ranking health; a steady climb in the number is the fingerprint of a core update or content that has aged behind competitors.
Time window	30D vsP (trailing 30 days compared against the prior 30 days).
Alert trigger	>15 (page 2 territory), sentiment key gsc_avg_position. An average position above 15 means the bulk of your impression-weighted appearances sit on or beyond page 2, where clicks are scarce.
Roles	owner, marketing

Calculation

Calculated automatically from your Google Search Console data. We read the property-level Average position metric over the trailing 30 days and compare it against the prior 30 days. The figure is an impression-weighted mean: queries you appear for more often pull the average more strongly. See the At a glance summary above and the worked example below.

Worked example

A UK pet-supplies retailer, Search Console verified on pawsandclawsdirect.co.uk. The dashboard shows the property’s 30-day Search Performance gauge.

Period	Average position	Clicks	Impressions
Prior 30 days (to 22 May 26)	8.6	52,300	2,100,000
Latest 30 days (to 21 Jun 26)	11.2	44,900	2,180,000

Three numbered observations:

1. A 2.6-place average slide is a material erosion, not noise. The average position rose from 8.6 to 11.2, meaning the impression-weighted average appearance crossed from the bottom of page 1 to the top of page 2. Clicks fell 14% on roughly flat impressions, exactly what you expect when appearances slide past the page-1 cliff: you still appear, but far fewer searchers scroll to you. Because impressions held, this is a ranking story, not a visibility-loss story.
2. Distinguishing an algorithm update from content decay. (a) Check the timing: a sharp step on a single date that matches Google’s confirmed update history points to a core or spam update; a slow week-on-week climb points to content decay or rising competition. (b) Split position by page type and intent, see Ranking by Page Type and Ranking by Intent, an update usually hits one content type hardest. (c) Read Ranking Volatility: high volatility across many queries on one date is the update signature. (d) Confirm pages are still indexed, an average-position rise plus an indexed-pages drop means the slide is partly de-indexing, not re-ranking.
3. The response and the recovery. Investigation showed the slide concentrated on category pages whose buying-guide content had not been updated in 14 months; two competitors had published fresher, deeper guides. The retailer refreshed the ten worst-hit category pages with current product ranges, comparison tables, and updated copy, then requested re-indexing. Over the following 30 days average position improved to 9.4 and clicks recovered to 49,600. Position is slow to move and slow to recover; treat it as a trend to manage, not a number to fix overnight.

Rule of thumb. Read average position with impressions: rising position number on flat impressions = ranking erosion (act on content and relevance); rising position number with falling impressions = you are both ranking worse and appearing less, a broader visibility problem worth escalating.

Sibling cards merchants should reference together

Card	Why pair it with Average Position
Average CTR	The other half of the ranking story. Position drives CTR; read them together to separate rank from snippet.
Position Trend	The time series behind this gauge. Distinguishes a step change (update) from a gradual drift (decay).
Position Distribution	The spread behind the average. Two sites can share an average position with very different distributions.
Ranking-Drop Alert	The per-query alarm. The average can hide a sharp drop on a few money queries; this catches them.
Ranking Volatility	The instability gauge. High volatility on one date is the classic algorithm-update signature.
Declining Queries	The queries dragging the average down, your refresh shortlist.
Ranking by Page Type	Which content types rank best and worst, to target a refresh.
Index-Coverage-Drop Alert	The de-indexing check, to confirm a position slide is re-ranking and not pages leaving the index.

Reconciling against the source

Where to look in Google Search Console:

Performance → Search results. Switch on the “Average position” metric and set your date range. The figure at the top of the chart, with the default “Web” search type, is the property-level number this gauge mirrors. Use the “Compare” date mode to see the prior-period delta the gauge shows.

Performance → Queries / Pages tabs. Sort by position to see the best and worst, but remember the property average is impression-weighted, not a simple mean of the rows.

Other GSC views that look related but are not this number:

• Per-query position: a single query’s position can be far better or worse than the property average. Do not read one query as representative of the whole.
• Search type filter: Image, Video, and News search have their own position figures. Confirm “Web” when reconciling.
• Insights: Google’s curated highlights, not a precise position you can match to a decimal.

Why our number may legitimately differ from the GSC UI:

Reason	Direction of divergence
Reporting delay. Performance data is typically 2 to 3 days behind. A 30-day window ending today ends on Google’s latest complete day, so it may not match a UI window you set to literally today.	Marginal, lag of 2 to 3 days
Average-of-averages. Average position is impression-weighted across every search. Comparing two 30-day windows reads differently if the impression mix shifted, even when no single ranking moved.	Variable
Device and search-type blend. A query ranking #2 on desktop and #14 on mobile shows a blended figure. A change in your desktop-to-mobile impression mix moves the average without any ranking changing.	Variable
Anonymised queries. Google withholds rare queries; their impressions still count in the property average but are absent from the query breakdown, so a row-summed average will not equal the headline.	Use the headline, not a row average
1,000-row cap. The Performance export caps at 1,000 rows, so rebuilding the average from an export omits the long tail and diverges from the property figure.	Variable

Cross-connector reconciliation:

Card	Expected relationship	What divergences mean
google_search_console.average-ctr	As average position worsens, CTR usually falls (deeper appearances earn fewer clicks).	A position slide with steady CTR suggests the loss is concentrated in already-deep queries that were not earning clicks anyway.
google_analytics.organic-vs-paid-traffic	GA4 organic sessions fall as average position worsens past the page-1 cliff.	Stable organic sessions despite a worse average position means the erosion is in low-traffic queries.
google_search_console.organic-to-revenue-divergence	A position slide on commercial queries flows through to organic revenue.	Use it to size the financial cost of the ranking erosion.

This card is not the source of truth for your live SERP rank; Google Search Console is, and even GSC reports an averaged, delayed figure rather than a real-time rank. This gauge mirrors that figure, compares it to the prior period, and surfaces sustained drift early so a slow erosion does not hide until it shows up as lost revenue.

Known limitations / merchant FAQs

My average position got worse but I think my rankings are fine. Why? Average position is impression-weighted across every query, device, and location, not a live rank check. It can worsen for reasons that have nothing to do with your core terms: Google started showing you for a batch of new, deep-position queries (more impressions at poor positions drag the average down), or your mobile-to-desktop impression mix shifted toward a surface where you rank lower. Always read the average alongside impressions and split by query before concluding your rankings fell.

Is a lower number better or worse? Lower is better. Position 1 is the top organic result; the number counts down the page. A move from 6 to 4 is an improvement; a move from 6 to 9 is a decline. The alert fires when the number rises above 15, meaning most of your impression-weighted appearances have fallen onto page 2 or beyond.

A core update hit and my average position jumped. Will it recover on its own? Sometimes partially, as Google continues to evaluate, but core-update losses usually require genuine content-quality improvement to recover. Identify the worst-hit content type, refresh it to be deeper and more current than the competitors who overtook you, and request re-indexing. Position is slow to move; expect weeks, not days, for recovery.

Why is my average position around 20 when my key pages rank on page 1? Because the average includes the long tail. You may rank #3 for your money terms but #25 to #40 for thousands of incidental queries that generate lots of impressions and few clicks. Those drag the blended average deep. This is normal; judge ranking health by the position of your commercial queries, not the property average alone, and use Position Distribution to see the spread.

Does average position account for SERP features like ads and AI overviews? Google’s reported position is the rank among organic results, so a result at “position 1” can still sit well below the fold if ads, a featured snippet, or an AI overview occupy the top of the page. That is why a strong average position can coexist with a weak CTR. Read both cards together, and audit the actual SERP for your top queries to see what sits above your organic result.

How long should I wait before reacting to a move? Distinguish a step from drift. A sharp one-date jump that matches a known update warrants prompt content investigation. A slow, steady climb of a fraction of a place per week is content decay; address it on your normal refresh cycle. A single noisy day, especially on low-impression queries, is rarely worth reacting to; use Position Trend to confirm the move is sustained.

Can I change the page-2 alert threshold? Yes, alert thresholds are configurable per profile in the Alert Rules tab. A niche where you naturally rank deep may warrant a higher threshold; a brand that lives and dies on page-1 visibility may want a tighter one. The default of >15 is set to flag when the bulk of your weighted appearances have crossed onto page 2.

---

Tracked live in Vortex IQ Nerve Centre

Average Position is one of hundreds of KPI pulses Vortex IQ tracks across Google Search Console and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English.

Start for free or book a demo to see this metric running on your own data.