Ranking on the First Page but No Traffic: Three Ceilings
By Ugur Saritepe · October 5, 2026
Ranking on the first page but no traffic? The position column cannot tell you why, and the impressions column can. On my site, six guides at positions 4.0 to 6.6 drew 105 impressions in 28 days between them. A sibling guide at 6.6 drew 1,637 and 61 clicks. Another at 9.1 drew 6,135 and 2 clicks. Three ceilings, one site, one month.
Where this came from
game-scout.app is my games directory and the site I test things on before I say them here. On 2026-10-04 I asked for a plan to write a guide article a day, using the guide series we had already started as the model. Here is the exchange, and the pull that answered it.
I am thinking about having new routing that will create auto article every day but I am thinking about these articles having a good structure like we have in comparison articles and I would like to have detailed articles instead of generic nonsense. For example our asphalt guides are not bad at all and I am sure some other games can have similar guide series. We already started one with asphalt gauntlet tracks
all /articles/ pages, last 28 days, grouped by page
asphalt best-cars (tier list) 1,495 impr 59 clicks pos 6.7 six gauntlet track guides, combined ~80 impr 1 click pos 5 to 7 it takes two co-op guide 5,823 impr 2 clicks pos 9.2 all 67 articles 22,121 impr 130 clicks pos 8.8
The Gauntlet track guides rank but nobody searches track names.
"Our asphalt guides are not bad at all" was true of one of them. The series I wanted to copy was ranking on the first page and drawing almost nothing. So on 2026-10-05 I re-pulled every article page for the 28 days to 2026-10-05 (Search Console data ends 2026-10-02), with the date each page was added, to see what separated the three groups.
Nine pages, three ceilings
Same site, same article template, same 28 days. Sorted by what capped each page.
page added pos impr clicks CTR demand ceiling gauntlet / tuscany riverine launch 09-12 5.18 28 0 0% gauntlet / tuscany vineyard voyage 09-16 4.81 26 0 0% gauntlet / himalayas freefall 09-16 6.62 21 0 0% gauntlet / himalayas leap of faith 09-18 5.88 8 0 0% gauntlet / san francisco railroad 09-27 5.20 20 1 5% gauntlet / san francisco the tunnel 10-01 4.00 2 0 0% six pages together 5.41 105 1 0.95% click ceiling it takes two / co-op guide 08-12 9.08 6,135 2 0.03% neither asphalt / gauntlet explainer 09-13 6.87 315 3 0.95% asphalt / best cars (tier list) 06-09 6.64 1,637 61 3.73%
The six track guides hold better positions than every other row and the fewest impressions. Their impression-weighted position is 5.41. The tier-list page sits at 6.64, a place lower, and drew fifteen times the impressions of all six combined. Position did not separate them. Impressions did.
The demand ceiling: position 5 on queries nobody types
Google's own definition is the whole explanation. An impression is recorded when a user has seen, or potentially seen, a link to your site, and a link must get an impression for its position to be recorded. Position is an average over the searches that happened. A page at position 4.0 on 2 impressions was shown twice in 28 days and was fourth both times. Nothing about that number says the page is doing well, because the denominator is two.
The age objection is the obvious one, so I checked it. The track series began on 2026-09-12 and the explainer for the same game mode was added one day later, 2026-09-13, on the same template. The explainer drew 1, 8, 8, 8, 14 and 25 impressions on its first six days and 35, 40 and 29 a day by its third week. The six track pages together never passed 17 in a day and sat at 0 to 7 on 18 of their first 21 days. One day apart, same site, same mode: one page found its searches, six did not.
The query report says the same thing a different way. Google omits rare queries from the table as anonymized rows and keeps them in the totals, as its discrepancies page documents. The explainer shows 12 visible query rows. The six track guides show 3, holding 3 of their 105 impressions. Ninety-seven percent of the searches that found those pages were too rare for Google to name. That is what a demand ceiling looks like from inside Search Console: a good position, a tiny count, and a query table that is almost empty. I measured the same anonymization on this site in the queries-do-not-add-up post.
One position, two meanings
Before calling it demand I had to rule out the other reading: that the page ranks well only on rare long-tail queries and sits on page three for the query that matters. A reported 6.6 cannot distinguish the two. So I searched both head queries on 2026-10-05 from the US.
asphalt legends gauntlet riverine launch 1 2 5 7 9 YouTube reference-run videos 3 Reddit r/Asphalt9 4 Asphalt wiki 6 game-scout.app, the track guide 8 Facebook group 10 asphaltlegends.com asphalt legends gauntlet freefall 1 5 7 9 YouTube 2 3 Reddit r/Asphalt9 4 8 10 Facebook groups 6 Asphalt wiki absent game-scout.app
Riverine Launch is the clean case. The guide holds position 6 on its own head query, the query exists, people make videos about it, and the page still drew 28 impressions in 28 days. The position is real and the demand is one search a day. Freefall is the other reading. Its reported 6.62 comes from queries Google does not show me; on the query I built the page for, it is not in the top ten, and the slots are reference-run videos and two Reddit threads. Same reported position, two different problems, and only the live results page tells them apart. The averaging behind that is the subject of is average position accurate.
The click ceiling: 6,135 impressions, 2 clicks
The It Takes Two co-op guide is the opposite failure and it looks healthy from the position column too. Position 9.08, 6,135 impressions, two clicks, a 0.03% click rate. The query report is not empty here; it is truncated at 60 rows and every row is a yes/no question: "can you play it takes two split screen" at 148 impressions and 0 clicks, "does it takes two have split screen" at 90 and 0. The results page answers those, so nobody needs the page. I measured that class at 0.13% across 2,000 queries in are listicles good for SEO, and the comparison pages on this site sit on the same ceiling at 0.42%.
The point of putting it next to the track guides is that the two failures share a symptom and nothing else. Both are "ranking but no traffic". One has no searches to win and one has searches that cannot be won by a page. Rewriting the track guides' titles would change nothing, because almost nobody sees them. Rewriting the It Takes Two title would change little, because the people who see it have their answer already.
The page that works, and why
The tier-list page is the control. Position 6.64, 1,637 impressions, 61 clicks in the 28 days; 5,269 impressions and 233 clicks over 90. Its two biggest visible queries over 90 days are "asphalt legends tier list" at position 3.04 with 79 impressions and 24 clicks, a 30.4% click rate, and "asphalt legends car tier list" at 3.29 with 66 and 14. The query asks for a ranked set and the page is one. It has demand and it has a click shape a page can win. Its position is worse than every track guide's, and it earns more than all of them and the explainer put together.
The demand check we skipped
The track series was designed on 2026-09-12 around an annotated map nobody else publishes, with a queue of 44 tracks. Nothing in that design asked whether anyone searches a track name. On 2026-10-05 I ran the check it should have had, with the demand tool I built for exactly this.
keyword autocomplete bing monthly asphalt legends tier list present 5,707 asphalt legends gauntlet present 4,583 riverine launch asphalt legends absent 4,583
The volume column is useless here: the mode and one track inside it get the identical figure, because volume tools bucket close variants, the failure I measured in is keyword search volume accurate. The tier-list figure is about three times the page's entire monthly impressions across every query it ranks for. The autocomplete column is the honest one. Google suggests the mode and does not suggest the track. That single bit, checked before the first page, would have told me what 105 impressions told me three weeks later.
Google frames the same thing from its side. Its guide to traffic drops says changes in user behavior change the demand for certain queries, and lists it as a cause you diagnose rather than fix. Demand is the one input to a page's traffic that the page cannot change.
What this does not tell me
- Two of the six track pages are too young to count. The Tunnel has one day of data and Railroad Bustle five. They are in the table because they exist, not because they prove anything.
- I checked the live results for two of six head queries. Riverine ranks and Freefall does not. The other four could be either.
- Low impressions are evidence of low demand only once the page is shown to rank for its head query. That held for Riverine and not for Freefall, which is why the live read is part of the method and not an optional step.
- One site, one window, games guides. A guide series about a product with a catalogue people search by model number will have a different floor.
- The visible-query share is a floor. Three visible rows out of 105 impressions says the queries are rare; it does not say what they were.
What we have not done
We have not stopped or re-pointed the track series. The weekly routine that builds one track guide a week is still enabled with 38 of 44 tracks queued, and the proposal from the 2026-10-04 session, to pick series by units people search by name and to set a pass bar of position 8 and 300 impressions a month by week six before the first page ships, is a decision I have not made. The comparison routine, the other format sitting on the click ceiling, was graded failed on 2026-10-03 and built another comparison on 2026-10-05. If either changes, this post gets a dated follow-up.
How to run this on your own site
- Pull your pages and sort by position, best first. In Search Console, Performance, Pages tab, 28 days. Read the impressions column beside each good position. Under about one impression a day on a first-page position is the flag.
- Open the flagged page's queries. A nearly empty table under a non-trivial impressions total means the searches were rare. Many rows of questions with zero clicks means the click ceiling instead.
- Search the head query yourself. If you are in the top ten and the impressions are still tiny, the demand is the ceiling and no edit lifts it. If you are absent, the reported position came from other queries, and the head query is a ranking problem you can work on.
- Before the next page in a series, check demand for the unit name. Autocomplete presence for the exact phrase, and whether the unit name has ever appeared as a query on a page you already rank. Treat identical volume figures across phrasings as one bucket.
If you want the indexing and raw-HTML side of a page checked while you are at it, the free triage report runs eight checks from the URL alone. The rest of these measured reads are in the AI-assistant SEO series.
FAQ
Why is my page ranking on the first page but getting no traffic?
One of three ceilings. Either the queries it ranks for are searched so rarely that a top position produces a handful of impressions (a demand ceiling), or the queries are searched often but Google answers them on the results page so nobody clicks (a click ceiling), or the position is an average over queries you cannot see. Search Console separates them: read the impressions column next to the position, then the page's query list. On game-scout.app six guides at positions 4.0 to 6.6 drew 105 impressions in 28 days, while a sibling guide at 6.6 drew 1,637.
What does a high average position with low impressions mean in Search Console?
It means the page was shown rarely and ranked well on the occasions it was shown. Google records a position only when a link gets an impression, so a position of 4.0 on 2 impressions is two searches, not a strong ranking. It can also mean the page ranks well on a few rare queries and not at all on the one you care about. Check the live results for your head query: on 2026-10-05 one of our guides sat at 6 on its head query and still drew about one impression a day, and another was absent from the top ten on its own head query despite a reported position of 6.6.
Can a page have thousands of impressions on the first page and still get no clicks?
Yes, when the queries are yes/no questions that the results page answers directly. Our It Takes Two co-op guide drew 6,135 impressions at position 9.1 in 28 days and got 2 clicks; every visible query was a question like 'can you play it takes two split screen'. That is a click ceiling, and it is a different problem from the demand ceiling. The fix for one does nothing for the other.
How do I check demand before writing a series of pages?
Check whether anyone has typed the unit name into Search Console on a page you already have, and check autocomplete for the exact phrase. Treat a volume tool's figure with care: on 2026-10-05 our keyword-demand tool returned the identical 4,583 monthly searches for 'asphalt legends gauntlet' and for 'riverine launch asphalt legends', because volume tools bucket close variants, while autocomplete presence was 1 for the mode and 0 for the track. The presence signal was the one that told the truth.
The whole diagnosis is two pulls and one search, and the first pull is the one people skip because the position column looks fine. Create a free account and the MCP serverlets your assistant pull every page with its position and impressions side by side, open one page's queries, and tell you which ceiling it hit, in one message. The nine-page table above took eight pulls and a spreadsheet.
