Average position

Why average position is misleading in isolation

Two pages can have the same average position with totally different real performance:

• Page A: ranks #1 for 50% of queries, position 20+ for 50% → average position: ~10.5
• Page B: ranks #10 for 100% of queries → average position: 10

Same number; wildly different commercial outcomes. Page A wins 50% of its query mix while Page B wins nothing. Reporting “average position 10” for both hides the truth.

What to report instead (or in addition)

Better metrics that the average obscures:

• % of priority queries in top 3 — actionable; ties to commercial outcomes
• % in top 10 (page 1 of SERP) — visibility threshold
• Specific keyword positions for named priority terms — granular
• Distribution histogram — shows the spread, not just the mean
• Position trend per query — tells you which queries are improving vs declining

Search Console’s UI defaults to showing average position; the API gives you per-query data.

When average position IS useful

Three cases where it adds signal:

1. Tracking site-wide visibility trend — is the AVERAGE moving up or down over months
2. Initial ballpark — a brand new client at average position 25 has very different starting state than one at average position 8
3. Sanity checks — drastic average position drops can indicate sitewide issues (penalty, indexing problem)

For any reporting more granular than that, drill into per-query data.

Average position pitfalls

Patterns that mislead:

• Long-tail dilution — your site ranks #3 for 5 priority queries and position 80 for 1000 long-tail ones. Average looks bad; the priority queries are fine.
• AI Overview impression inflation — AI Overviews trigger impressions for pages not normally surfaced, dragging average position down without real loss.
• Mobile vs desktop blending — average position across both can hide divergence.

Always filter Search Console reports by device, country, and date range to see real patterns.

Resocial perspective

We deprecate “average position” in headline reporting. Replaced with per-priority-keyword position trends and ”% in top 3 / top 10” share metrics. Most B2B businesses care about the 30-100 queries that drive pipeline — those should be tracked individually, not averaged.