One push from page 1
Find your striking distance keywords.
One call reads every search this site already ranks 11 to 30 for, with the demand behind each one. You pick which are worth a slot, and your agent works them onto page 1 one at a time.
From $49/mo, everything included · works in Claude Code, Cursor, Cline and Windsurf
Built from the Search Console audit we run on our own SaaS, AppScreenshotStudio.
Why it hides
The near-miss is a search, not a page.
A page’s position is your topmost spot, blended across every search it appears for. One search sitting at 12, averaged in with thirty ranking far lower, reads as 19 and looks hopeless. The searches themselves are where it surfaces, and QueryScope reads that whole band in one call.
In the page total
The average buries the opportunity.
In the searches themselves
The band is where it surfaces. The page average is where it hides.
Three reads turn a blended page average into a short list of searches worth a slot, and then into one climb at a time.
Every search you sit 11 to 30 for, in one call.
QueryScope reads the entire 11-30 band out of your Search Console query rows, not a sample of it, then drops your own brand searches, the searches your plan already claims, and anything seen fewer than three times. What is left is sorted by monthly demand, with your own impressions breaking the tie. Each cut is counted out loud, so an empty section means nothing is close rather than nobody looked.
whole band read · brand, declared and sub-3-impression rows counted, not swallowed
Striking distance: the query your average hidesThe plan holds fifty searches, so each one costs something.
Every row arrives with what kind of search it is beside it, and that label is shown and never sorted on: the buyer shapes (best, top, vs, compare) are also the ones an AI answer most often absorbs, so ranking them to the top would promote the least clickable work on the page. You make the call and record it: go after it with a value and a reason, or rule it out as the wrong buyer, not yet, or not winnable. Ruling one out is recorded too, so the same search does not come back next session.
demand decides the order · intent shown, never sorted on
When a page ranks for the wrong intentEarn the placement, and know who holds it.
Once a search is declared, your agent asks for the next thing to do and gets one. Below page 1 the climb is the job: deepen the section that answers the search, match the heading to it, and where there is a page worth linking from, that link goes first, because it settles in six weeks rather than a quarter and needs no sign-off. On page 1 with a measured click gap and no answer absorbing it, the move is the title instead. And because Search Console records nothing below position 10, QueryScope reads the results page itself for your declared searches and names the sites holding the places above you.
below page 1 → the results page · page 1 → Search Console
When a good rank still loses the clickOn a live site
The plan board, on a SaaS we run ourselves.
AppScreenshotStudio's declared searches, read from production: where each one stands and whether it moved.
How the plan is doing
21 May to 25 Sep · arrows are places moved, up is better
On page 1
where clicks happen · was 0 on 21 May
Below page 1
ranking, earning almost nothing · was 2 on 21 May
Not ranking
no reading on 10+ impressions · was 55 on 21 May
Coverage
<1%The whole site earned 528 clicks in 28 days, most of it on searches this plan never claimed.
On page 1
figma app store screenshot template
#9.9
▲3
320/mo
Demand
38
Impressions
2
Clicks
One line in your IDE. Then authorize and pick a site.
claude mcp add --transport http queryscope https://mcp.queryscope.dev/mcpWorks the same in Cursor, Cline and Windsurf. Your IDE opens a browser once to authorize.
Then ask: “where are we already close?”
FAQ
Reading the near-miss.
What is a striking distance keyword?
A search your site ranks for just off page 1, close enough that a modest gain turns a result nobody sees into real traffic. QueryScope reads that band, positions 11 to 30, out of your Search Console query rows in one call, skipping your brand searches, the searches your plan already claims, and anything seen fewer than three times.
Why doesn't the page report show it?
A page's position is your topmost spot averaged across every search it appears for, so one search at the edge of page 1 blended with others ranking far lower gets averaged out of sight. The band is read from Search Console's query rows, and those rows carry no page at all: the position belongs to the site for that search, and which of your pages should own it is a decision you record rather than one QueryScope guesses.
Which near-misses are worth chasing?
The order is monthly demand first, then how often this site has actually been seen for the search. What kind of search it is sits beside each row and never moves it: the buyer-shaped ones are also the ones an AI answer most often absorbs, so sorting on intent would promote the least clickable work. The plan holds fifty searches, so each declaration spends a slot, and the ones you rule out are recorded with your reason instead of coming back.
Is this the same as fixing a low click rate?
No. A low click rate means you are on page 1 and getting skipped, which is a title or AI answer problem. A near-miss means you are not on page 1 yet, so the job is the ranking. QueryScope splits them on evidence rather than position alone: the title only becomes the move where there is a measured gap between what the search earns and what its position normally earns, over enough impressions for the gap to be real, and where no AI answer is taking the click.
Can it tell me who is ahead of me below page 1?
Yes, for the searches you declare. Search Console records nothing below position 10, so QueryScope reads that results page directly and hands back the domains ranking above you with their titles and addresses, so your agent can open those pages and see what Google prefers there. What it does not read is backlinks, which sit outside Search Console and outside this product, so a climb is a candidate rather than a promise.
Does QueryScope write the page for me?
No. It never touches your repo and generates no content: your own agent makes every edit. A climb changes what a visitor reads, so the proposal goes into queryscope.md and waits for your commit. Once the change is recorded, the clock starts the day Google recrawls the page and runs at least four weeks of settled data, and that search is not handed back meanwhile, because a second edit inside the window destroys the baseline the first one is judged against.
Push the searches that are one step from page 1.
Connect your site, read the band you already compete in, and let your agent work the climbs you declared.
7-day free trial · nothing due today · cancel in one click
Other things it finds in your Search Console