Rank Tracker Example: 47 Keywords with Live GSC Data
This example shows the aiwebpageseo Rank Tracker connected to a Google Search Console account. 47 keywords are tracked with average position 14.3. The report shows 8 keywords that improved positions this week, 5 that dropped and identifies which pages are driving the most clicks.
| Keyword | Position | Change | Clicks | Impress. | CTR |
|---|---|---|---|---|---|
| aeo checker free | 3.2 | ↑ +2.1 | 347 | 1,840 | 18.9% |
| site audit tool | 7.4 | ↑ +1.8 | 218 | 2,340 | 9.3% |
| answer engine optimisation | 8.1 | ↑ +4.2 | 184 | 2,100 | 8.8% |
| schema markup generator | 12.7 | ↓ −1.4 | 142 | 3,200 | 4.4% |
| llms.txt generator | 5.8 | ↑ +6.4 | 167 | 1,480 | 11.3% |
| core web vitals checker | 14.3 | ↓ −2.1 | 98 | 2,840 | 3.5% |
| technical seo audit | 18.4 | → 0.0 | 76 | 4,120 | 1.8% |
| e-e-a-t checker | 9.2 | ↑ +3.1 | 124 | 1,360 | 9.1% |
schema markup generator — 3,200 impressions, only 142 clicks (CTR 4.4%)
High impressions and few clicks usually means the result is ranking below the fold, or the title does not match what the searcher wanted. Check the actual average position for this query before rewriting anything — a 4.4% CTR is unremarkable at position 8 and alarming at position 2. Note also that click-through rate is not a direct ranking signal, so a better title earns you the clicks it earns and nothing further. Rewrite the title to include "free" and "instant" — test "Free Schema Markup Generator — Instant JSON-LD" to improve CTR to 8%+.
core web vitals checker — 2,840 impressions, 98 clicks (CTR 3.5%)
Just outside page one. FAQPage schema will not move it — FAQ rich results have been restricted to recognised government and health sites since 2023, so there is no enhancement to win here. Improve the meta description so it says what the tool measures (LCP, CLS, INP), and improve the page so it is a better answer than the ten above it. 3 positions improvement would double clicks at this impression volume.
technical seo audit — 4,120 impressions, 76 clicks (CTR 1.8%)
High impression volume but deep page 2 position. This keyword has significant traffic potential. Build a dedicated landing page targeting this exact query with comprehensive content, schema and internal links from your top pages.
An average position of 14.3 across 47 keywords is a mean of means, and it is worth understanding how little it is telling you. It averages across devices, locations, days and searchers. A keyword reported at 14.3 could be at 8 on desktop in one city and 22 on mobile everywhere else, and the average describes neither of those realities.
More importantly, position has become a weaker proxy for traffic than it used to be. The results page is now stacked with things that are not organic results: AI Overviews, featured snippets, local packs, shopping carousels and ads. A first-place organic result underneath all of that can be further down the visible page than a third-place result on a clean SERP. The number went up; the visibility went down.
So use position to detect movement, and then go to impressions and clicks to find out what the movement cost. Those two are measurements. Position is an inference.
Every traffic loss is one of two things, and Search Console distinguishes them cleanly if you ask it to. Getting this wrong is how teams spend a quarter rewriting titles when the real problem was that they lost the ranking.
You lost the position
Fewer people are being shown your result at all. This is a ranking problem: either you got worse, somebody else got better, or an algorithm update reassessed the whole set. The response is content and competitiveness, not presentation. Rewriting the title changes nothing here.
You kept the position and lost the click
The result is still being shown and fewer people are choosing it. Sometimes that is a poor title or a description that fails to match intent. Increasingly it is that an AI Overview answered the question above you, or the SERP grew another feature and pushed you below the fold. The first is fixable by writing; the second frequently is not, and pretending otherwise wastes effort.
One correction while we are here, because it drives a great deal of bad advice: click-through rate is not a direct ranking signal. Google has said so repeatedly. Improving a title to win more clicks is worth doing because clicks are worth having — not because the clicks will then push you up the results. There is no flywheel to spin.
The familiar curve — about a quarter of clicks at position one, a tenth at position three, a few percent by position ten — is derived by averaging across millions of unrelated queries. It is a useful shape and a terrible benchmark for any individual keyword.
Actual click-through rate on a given query depends on how many ads are shown, whether an AI Overview sits above the results, whether a local pack occupies the top of the page, whether the query is navigational (in which case the top result takes nearly everything) or exploratory (in which case clicks spread), and on how well the title matches what the searcher had in mind. Two queries at the same position can differ by an order of magnitude, and both are normal.
So compare a keyword's CTR to its own position and its own history, not to a curve. A 4.4% rate is unremarkable at position eight and a serious problem at position two — and the report cannot tell you which without the position beside it.
The conventional advice is to attack positions 11 to 20, on the reasoning that they are closest to page one. It is a decent filter and a poor decision rule, because it ignores the two things that determine whether the work will pay.
Read the pages above you before you commit
If the top ten are thorough, evidently first-hand and written by people who know more than you do, a position of 12 is not a near miss — it is an accurate assessment. If they are thin, hedged and interchangeable, then even a difficult-looking keyword is available to whoever writes the genuinely best answer. No metric in this report can tell you which situation you are in. Twenty minutes of reading can.
Would this searcher ever buy from you?
A high-volume term at deep page two looks like the biggest opportunity on the report and is frequently the worst use of a quarter. Traffic that cannot convert costs you the writing time, dilutes the site's focus, and flatters the dashboard. A smaller keyword that describes exactly what you sell is worth more than a large one that describes the category loosely.
And be honest about ceilings. On queries where an AI Overview now answers the question completely, the click is not coming back, and the correct strategic response is to stop competing for it and to compete instead where the answer genuinely requires the caveats, the numbers and the method — which is where the page that supplies them still earns both the citation and the click.
How does the Rank Tracker connect to Google Search Console?
The aiwebpageseo Rank Tracker uses the Google Search Console API with OAuth2 authentication. Connect your account in Settings and select your property. Data is fetched daily and stored for trend analysis. You need at least Restricted User access to the GSC property.
What is a good average position in Google?
Average position 1–3 is excellent — you appear in the top 3 results for most queries. Position 4–10 is on page one — typically good traffic. Position 11–20 means page 2 — a major improvement opportunity. Below 20 means most users will not see you. Focus improvement efforts on keywords ranked 11–20 first as these are closest to page one.
What is CTR in Google Search Console?
Click-through rate is the share of impressions that resulted in a click. The published curves — roughly a quarter of clicks at position one, falling steeply from there — are averages across millions of unrelated queries, and your query is not an average. CTR varies enormously with intent, with whether an AI Overview or a local pack sits above the results, and with how many ads are shown. Two things follow. Compare a keyword's CTR against its own position, not against a curve. And do not treat CTR as a ranking lever: Google has consistently said clicks are not a direct ranking signal, so a better title wins you the clicks it wins, and nothing beyond that.
Is average position a number I can act on?
Only loosely, and it misleads more often than it helps. Average position is a mean across every impression for a query — different users, different locations, different devices, different days. A keyword sitting at 14.3 might be at 8 on desktop and 22 on mobile, and the average describes neither. Worse, position now says less about traffic than it used to: a first-place result beneath an AI Overview and a set of ads can be further down the visible page than a third-place result on a clean SERP. Use position to spot movement, then look at impressions and clicks to find out what the movement actually cost you.
Which keywords should I work on first?
Not simply the ones at positions 11 to 20, though that is the standard advice and it is a reasonable starting filter. The better sort is by whether you can plausibly become the best answer for that query, and whether the person searching it would ever buy from you. A keyword at position 12 where the top ten are thorough, expert pages is not a quick win; a keyword at position 18 where the results are thin and generic is. And a high-volume term that brings people who will never be customers is a cost, because the writing time was real and the conversion is not.
Why is my ranking position not producing traffic?
Usually because the SERP has changed shape underneath you. An AI Overview, a featured snippet, a local pack or a row of ads can push a technically strong position well below the fold, and for a question fully answered in three sentences the click may simply no longer happen. Search Console tells you this if you ask it properly: steady impressions with collapsing clicks means you held the position and lost the click, which is a SERP-layout problem. Falling impressions means you lost the position, which is a ranking problem. They demand entirely different responses, and conflating them wastes months.
Does Search Console data match what I see when I search?
No, and it should not. What you see is one personalised, localised result on one device at one moment, and it is influenced by your own history. Search Console reports aggregates across everyone who saw your site, which is the thing you actually want to know. Checking your own rankings by searching for them is one of the most reliably misleading habits in SEO — it produces confident conclusions from a sample of one. Trust the aggregate data, and treat what you see in your own browser as an anecdote.
Related Demo Reports
Run Rank Tracker on Your Own Site
Get your real audit report with specific issues, fixes and actionable improvements — free to start.