Rank Tracking

Rank tracking is the most over-collected and under-used data in SEO. A list of 2,000 tracked keywords produces a chart that moves constantly and tells nobody what to do.

Track a small deliberate set, understand what rank now means, and use Search Console for everything else.

Rank is less meaningful than it was

Say this before setting anything up, because it changes what you promise.

• Results are personalised and localised. There is no single ranking, only a distribution
• SERPs vary by device, region and time
• Features displace organic. Position 3 below an AI Overview, a video carousel and four ads is not position 3 as anyone imagines it
• Google rewrites titles, so what appears isn't what you wrote
• AI Overviews absorb clicks without changing position at all
• Tracking tools query from a location and profile that isn't your customer's

Position is an input; clicks and conversions are the outcome. A report leading with average position is measuring the wrong thing, and it will eventually diverge visibly from revenue.

Track a small set, deliberately

20-60 keywords for most sites
100-200 for large ecommerce, segmented

Choose for decision value, not coverage:

Head commercial terms          the ones with real revenue attached
Category and comparison terms  where the buying decision happens
5-10 competitor-defining terms where you must be present
A few branded terms            to detect brand SERP problems
Terms tied to active projects  so you can see the work landing

Don't track the long tail. Search Console has all of it, measured rather than sampled, and it's free. Rank trackers sample; Search Console reports what actually happened.

Rank tracker         a small set, daily, with SERP features
Search Console       everything else, weekly and monthly

Configure it honestly

[ ] Device split: mobile and desktop separately, not blended
[ ] Location set to where your customers are, not your office
[ ] Local tracking at postcode level for local businesses
[ ] Language set correctly
[ ] SERP features captured, not just position
[ ] Competitors tracked on the same terms
[ ] Weekly frequency for most terms, daily only where volatile

Blended mobile and desktop hides real problems. A page ranking 4 on desktop and 11 on mobile shows as 7 and looks fine.

Capture SERP features. Knowing you rank 3 is much less useful than knowing you rank 3 below an AI Overview, a People Also Ask block and a video carousel — because that combination explains a CTR that position alone doesn't.

Read it correctly

Under three positions of movement is noise on most terms. Set the reporting threshold accordingly, or you'll spend meetings explaining fluctuations.

"All terms moved together" is usually the tool, not the site. Check the tracking location and device settings changed before diagnosing an update.

Report it as a distribution

Position bucket   Terms   Change
1-3                  12      +2
4-10                 24      -1
11-20                14      -3
21+                  10      +2

Better than an average, which is dominated by a few outliers and can improve while everything that matters gets worse.

Also useful:

Share of terms in top 3
Share of terms with a SERP feature above us
Terms where a competitor outranks us
Terms newly entering or leaving the top 10

"Share of terms with a feature above us" is the modern metric and almost nobody reports it. It's the number that explains falling CTR at stable positions.

Use Search Console as the primary source

For anything beyond the tracked set:

Real positions, averaged over real impressions
Every query, including the long tail
Actual clicks and CTR
Device, country and date segmentation
No sampling, no location guessing

Its limits: a 16-month window and export caps in the UI. The bulk export removes both. See gsc-bigquery-analysis.

The honest division of labour: rank tracking gives you daily granularity and SERP feature visibility on a few important terms; Search Console gives you complete, measured performance on everything. Most reporting should be built on the second.

Track AI answer presence separately

Rank tracking doesn't cover answer engines, and they're an increasing share of the same intent.

Rank tracker      classic SERP position, SERP features
Prompt set        presence and citation in AI answers

Keep them as separate metrics with separate methods — an AI answer has no position, so folding it into a rank report misrepresents both. See the companion GEO pack.

Review the tracked set

Quarterly    remove terms that no longer matter
             add terms tied to new projects
             re-check location and device settings
             confirm competitor set is still right
Annually     rebuild the list from the commercial priorities

A tracked list only ever grows unless someone prunes it. Sixty terms nobody reads is worse than twenty someone acts on.

Tooling

Any rank tracker will do the mechanical part. What matters is the configuration above — device split, real customer location, SERP features captured, competitors on the same terms — and that most of your reporting sits on Search Console instead.

For the answer-engine half, which rank trackers don't cover, Keupera tracks per-prompt presence, position, sentiment and citations across ChatGPT, Perplexity, Google AI, Claude, Grok and Codex, with competitor benchmarking:

claude mcp add --transport http keupera https://mcp.keupera.com/mcp -s user

Keep the two metrics separate. An AI answer has no position, and folding it into a rank report misrepresents both.

Don't

• Don't track thousands of keywords.
• Don't track the long tail. Search Console has it.
• Don't blend mobile and desktop.
• Don't report average position as the headline.
• Don't react to movements under three positions.
• Don't ignore SERP features. They explain the CTR.
• Don't lead a report with rankings. Lead with clicks and revenue.
• Don't fold AI answer presence into rank reporting.

Related skills

gsc-bigquery-analysis, serp-feature-targeting, traffic-drop-diagnosis, competitor-seo-analysis, seo-forecasting, seo-split-testing