Updated
To see your keyword rankings in Google Search Console, open Performance > Search results, tick Average position, and look at the Queries tab: each search that showed your site has its clicks, impressions and average position. That position is an average of where you appeared across every search, location and device in the date range, not a single live rank, so it will rarely match a rank tracker. Filter by one query, then switch to the Pages tab to see which URL ranks for it.
How to check keyword rankings in Google Search Console
- Open Search Console and choose your property.
- Go to Performance > Search results.
- Click the Average position box above the chart so it is highlighted. Turn on Average CTR too.
- Set the date range. Use at least 28 days; a week is too noisy for most searches.
- Scroll to the table and stay on the Queries tab. Sort by impressions to see the searches that matter, or by position to see where you rank best.
- To track one keyword, click it (or use + New > Query with “exact query”). The chart now shows that search only, and the Pages, Countries and Devices tabs show where its numbers come from.
plumb(er|ers|ing).*austin to catch every Austin plumbing search. Google added regex filters in 2021.How Search Console calculates average position
Google’s own definition: position is the topmost position a link to your site held in a search result, and only searches where you got an impression count. Google’s example: you appear at positions 2, 4 and 6 for one search and 3, 5 and 9 for another. Your topmost positions are 2 and 3, so the average position is 2.5.
- Only your best result counts. If two of your pages show for the same search, only the higher one sets the position.
- Position counts every element. A whole AI Overview takes one position, and every link inside it shares that position. Local packs, image blocks and other features take positions too.
- No impression, no position. If you sit at position 40 and nobody scrolls that far, you don’t get an impression and that search doesn’t pull your average down. A dash means there is no position to report.
- The chart and the table differ. The chart is aggregated by property (your topmost result for each search). In the Pages table each URL gets its own average, so the numbers don’t add up neatly (Google).
Why Search Console rankings differ from rank trackers
| Search Console | Rank tracker | |
|---|---|---|
| What it measures | Every real search that showed you | One check, from one place, on one device |
| Location | Every searcher’s location, blended | The location you set |
| Time | An average over the whole date range | A snapshot at check time |
| Personalization and features | Whatever each searcher actually saw | Usually a clean, unpersonalized results page |
| Keywords covered | Searches where you got impressions, minus anonymized ones | Only the keywords you added |
| Competitors | No | Yes |
So a rank tracker can say you are #3 for “plumbers austin” while Search Console says 7.4. Both can be right: searchers on the other side of town, on mobile, or seeing a local pack above you push the blended average down. For local and directory searches the gap is often large, because the results change by neighborhood.
Use Search Console for the truth about what happened across all searchers, and a rank tracker when you need competitors or a fixed daily check for a short list of keywords.
Keyword ranking for one query and page
A query’s position is about your best page for it, but which page is that? Filter by the query, then open the Pages tab. If two or more pages each take a share of the impressions, they may be competing, and Google switches between them. See the keyword cannibalization checker guide for how to tell real cannibalization from normal overlap.
The reverse works too: filter by one page (/plumbers/austin-tx), open Queries, and you get every search that page ranks for, with its position in each. This is the fastest way to see whether a city page ranks for its main search or only for long-tail variants.
Position by device and country
With a query filter on, the Devices tab shows position separately for desktop, mobile and tablet, and the Countries tab for each country. A page that ranks 4 on desktop and 11 on mobile usually has a mobile layout or speed problem, or mobile results carry more features above it. For a US directory, filter Country = United States first, so stray impressions from other countries don’t skew the average.
Anonymized queries and other gaps
- Rare searches are hidden. Google anonymizes searches that weren’t made by more than a few dozen users over two to three months (Google). They count in the totals but never appear as rows, and applying any query filter drops them. On a directory with thousands of long-tail “service + suburb” searches, a big share of impressions can sit here.
- 1,000 rows in the interface. The table and export stop at 1,000 rows; the API reaches about 50,000 rows a day per search type.
- 16 months of history. You can’t compare this month’s ranking with two years ago unless you saved the data.
- No search volume. Impressions are not search volume. A search with 50 impressions at position 30 may have thousands of monthly searches that you never got shown for.
Using Search Console for keyword research
Search Console is the best keyword research tool you already have, because it shows searches Google already connects with your site:
- Near misses. Filter position greater than 4 and sort by impressions. Searches at 5 to 20 with real impressions are the cheapest wins. See striking distance keywords.
- Low click rate. High impressions, good position, few clicks: the title and description don’t match the search. See organic CTR by position.
- Questions. A regex query filter like
^(who|what|how|why|when|where|best|cost)surfaces questions you could answer on the page. - Missing pages. Searches where the ranking page is a poor fit, like “emergency plumber round rock” landing on your Austin page, are pages you could build.
Tracking rankings over time
Search Console doesn’t keep a rank history per keyword the way a tracker does, but you can build one:
- Compare mode. In the date picker choose Compare, for example the last 28 days against the previous 28. The Queries table then shows both positions and the difference for every search.
- Weekly or monthly chart. With a single query filtered, switch the chart to weekly to smooth out day-to-day noise.
- Export monthly. Export the Queries table each month (1,000 rows at most) or pull it with the API, because anything older than 16 months disappears.
When average position misleads you
Average position can improve while traffic falls, and the reverse. Two common cases:
- New, low impressions drag the site average down. When Google starts showing you for hundreds of new long-tail searches at positions 30 to 60, the site-wide average position gets worse even though nothing you already had dropped. Check the position of the searches you care about, not the site average.
- Lost impressions make it look better. If you drop off page one for a big search entirely, its impressions vanish, and the average of what remains can rise. Look at clicks and impressions next to position, always.
A position change under one place on a search with a few hundred impressions is usually noise. Act on changes that hold for two or more weeks, or that affect a group of searches together.
Keyword rankings on a directory website
On a directory, the rankings that matter are category × city searches (“plumbers austin”, “emergency plumber round rock”) and business-name searches that land on listing pages. Three things make them different:
- The local pack sits above you. For many category × city searches Google shows a map pack first, which takes a position. Being “position 4” may mean the first organic result under a map, an ad block and an AI Overview.
- “Near me” blends locations. A “near me” search is answered for wherever the searcher is, so your average position for it mixes dozens of towns.
- The ranking unit is the page type. One city page at position 12 is a page problem. Six hundred city pages averaging 12 is a template problem. Group rankings by page type before acting.
How DirectoryLens shows keyword rankings
DirectoryLens stores your Search Console data every day, so you can compare a search’s position across more than 16 months, and it reads every row through the API instead of the 1,000-row table. In the app:
- Searches and pages > Searches lists every named search with clicks, impressions, CTR and average position, compared with the previous period, and filters by page type, device or country.
- Quick wins > Almost page one lists pages just below the top results and the words their titles are missing.
- Countries and devices shows position by country and by desktop, mobile and tablet.
- Competing pages finds searches where two of your own pages split the impressions.
- For directories, the Competitors report (part of the Market data add-on) checks who ranks on Google from each city for your biggest category × city searches, which Search Console can’t tell you.
Like Search Console, it can’t name anonymized searches; it shows how much of the traffic they make up instead. Positions are Google’s averages, not a live rank check.