CTR optimization, from your Search Console
Find the pages you rank for but rarely win the click.
QueryScope raises the searches where you rank well and under-earn the click, then tells a title you can fix from an AI Overview taking the click that no rewrite recovers.
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
A page can rank well and still leave clicks on the table.
It ranks, it gets impressions, the site total looks healthy, so nothing flags it. But the click rate sits below what a result at that position normally earns, and that gap is traffic already in front of you. The honest catch: sometimes the gap is a weak title you can fix, and sometimes it is an AI Overview taking the click, which no rewrite recovers.
In the site total
No red flag in the numbers alone.
Against the curve, and the results page
The gap is the signal. The results page says whether it is winnable.
Three reads turn a low click rate at a good position into a verdict on whether a title can win it back, or an AI Overview is taking it.
Is the title weak, or is something taking the click?
A low click rate at a strong position has two causes. A title that undersells the page wins clicks back with a rewrite. An AI Overview answering the query above you does not, no matter the title. QueryScope reads the actual results page for the searches you declared, so it can tell you which one you are looking at, and whether that answer already cites you.
AI answer above you · does not cite you → the results page, not the title
Low CTR at a good position: title or AI Overview?The gap is a ceiling, not a forecast.
The expected rate comes from a published 2026 click-through curve, the multi-study median for a clean results page. That is a real yardstick and it is also an average, so QueryScope treats the clicks it implies as an upper bound rather than a promise. On a query with an AI answer the true ceiling is lower, which is exactly why the results-page read sits in front of it.
pos 4 · 1.1% against an expected 8.0% at that position
What each Search Console metric measuresThe biggest real opportunity first, not the loudest percentage.
A search shown fifteen times with one click is noise, not a quick win. QueryScope sorts by the clicks actually at stake and holds back the rows too small to carry a verdict, so what reaches you is the one worth your afternoon. You get it one at a time, with the measurement running before the next arrives.
sorted by clicks at stake · rows below the floor never surface
A real page at 0.00% click rate, read honestlyOn 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: “what should I work on?”
FAQ
Reading the click you're not winning.
How does QueryScope decide a page is a CTR quick win?
It compares the click rate on a declared search against what a result at that position normally earns, over enough impressions for the number to mean anything, and raises it as move 1 when the gap is real. Rows too small to carry a verdict are held back rather than guessed at.
How do I improve CTR on a page that already ranks?
Find the searches where the click rate sits below what a result at that position normally earns. Check the results page for an AI answer before touching anything, because no title wins back a click an AI Overview is taking. Where the click is recoverable, rewrite the title for the search that actually finds the page, then judge it from the day Google recrawls, not from the day you shipped. QueryScope does the finding and the measuring; your agent makes the edit.
Is a low click rate always a title problem?
No. A page can hold its rank and still lose clicks when an AI Overview answers the query above it. QueryScope reads the results page for your declared searches, so it can say whether an AI answer is there and whether it cites you. When the click is structurally gone, the move is becoming the thing it quotes, not a title rewrite.
What does it compare my click rate against?
A published 2026 click-through-by-position curve, the multi-study median for a results page with no AI answer on it. It is an average, and QueryScope says so: the clicks it implies are an upper bound rather than a forecast, and on a query with an AI Overview the real ceiling is lower. That is why the results-page read decides whether a gap is worth acting on, not the curve alone.
Will a better title get the clicks back?
When the title was the problem, often. QueryScope starts a measurement clock the day Google recrawls the page and tells you what the numbers actually did, rather than assuming it worked. When an AI Overview is capping the click, a rewrite does nothing, and the honest move is to make the page the thing it cites.
Does this tell me if the extra clicks convert?
No. QueryScope reads your search data and stops at the click: it shows the clicks you are being shown and not taking, and which kind of fix each one needs. Whether those visitors convert is a measurement in your analytics or your product.
Win the clicks you already earned.
Connect your site, declare the searches worth winning, and let your agent work the one where the click is closest.
7-day free trial · nothing due today · cancel in one click
Other things it finds in your Search Console