Guides
Keyword tracking without a rank grid
A daily rank grid produces a lot of numbers and very little decision. This guide compares rank tracking with Search Console average position, explains why the grid is noisy and expensive, and shows what to track instead when the goal is choosing a page to fix.
By the Visdenda research team · Reviewed by the Visdenda editorial team
Published 2026-11-17 · Updated 2026-11-17 · 7 min read
Two different position numbers
A rank checker answers one narrow question: for this keyword, in this location, on this device, where did my URL appear today? Its unit is a position per keyword per check. Search Console answers a different question: across the impressions Google recorded for this property in this window, what was the average position? Its unit is an average over a date range.
Because the denominators differ, the numbers differ, and neither is wrong. A search performance report should say which one it shows. If a slide puts a rank checker position and a Search Console average in the same cell, the comparison is meaningless.
Why a daily grid is noisy and expensive
A rank grid multiplies keywords by locations by check frequency. That is a real cost, and much of what it buys is noise: locations and devices return different results, SERP features move the organic list, and personalisation makes one check hard to reproduce. Day-over-day movement is usually presentation, not a durable ranking change.
The fixed keyword list has a second problem: it is a hypothesis about demand. Search Console starts from impressions, so it includes queries you never thought to track. If the goal is deciding which page needs work, demand data beats a guessed list.
What to track instead
- Search Console queries by page. The demand that already exists, including terms you did not guess.
- A short tracked-term list. The terms you care about, joined to clicks, impressions, CTR and average position for the window.
- Striking distance. Queries at position 5–20 with at least median impressions: close enough to improve.
- Decay. Pages losing clicks between the current and comparison windows, with both counts attached.
- AI Overview presence and citations. Whether an answer appeared for a tracked query and whether it cited your domain.
How this console tracks keywords
The console keeps a tracked term list per site and joins each term to Search Console clicks, impressions, CTR and average position. It does not store a daily position per keyword. Volume and difficulty come from keyword research you run, with a platform-paid allowance on Pro; the keyword guide covers the workflow.
The unit of review is a window, not a day. Compare the same window length each month and write down what changed before you explain why. That is also where the search performance view and the page row agree: both read Search Console, and both keep average position labeled as an average.
AI Overviews and competitor SERPs
AI Overviews do not expose a rank grid. What you can track is a fixed sample: the same queries and locale checked on a schedule, recording whether an answer appeared and whether it cited your domain. Free sites sample manually with their own DataForSEO key; Pro adds daily sampling. AI crawler fetches come from the server probe and are access evidence, not traffic.
Competitor SERP checks are on-demand top-10 snapshots over terms you already track, cached for 24 hours. They show whether your domain and a competitor appear; they are not rank history and not keyword mining. Competitor AI citations and traffic are out of scope.
Limits and a monthly routine
There is no stored daily position history and no rank tracking for arbitrary keywords: position is Search Console's average for the selected window. Search Console lags one to three days, may sample large properties, and retains about 16 months. Volume and difficulty are research inputs, not observed positions.
Once a month, pick a small term set, compare the same window, review striking-distance queries and decaying pages, and check AI Overview presence for the terms that matter. Run competitor SERP checks only when a term is under review. Skip the daily grid; it rarely changes the decision.
Frequently asked questions
Is rank tracking better than Search Console average position?
They answer different questions. A rank checker reports one position for one keyword, location and device at one moment. Search Console averages the positions of your property across impressions for the window you select. Neither is more accurate; they have different denominators and should not share a column.
Why is a daily rank grid noisy?
Positions move with location, device, personalisation and SERP features, so much of the daily movement is presentation rather than a durable change. A grid also costs per keyword, location and frequency, and it tracks a keyword list you guessed rather than the demand Search Console recorded.
What should I track instead of daily ranks?
Track the queries Search Console already reports, a short list of terms you care about, striking-distance queries at positions 5–20, decaying pages, AI Overview presence and citations for the terms you track, and on-demand competitor SERP snapshots. Each has a decision attached; a daily position mostly has a chart.
Does the console store daily keyword positions?
No. There is no stored daily position history. Tracked terms are joined to Search Console clicks, impressions, CTR and average position for the selected window. Competitor SERP checks are on-demand top-10 snapshots over your tracked terms, cached for 24 hours, and there is no competitor keyword mining.