The clicks you already earned

Find the pages you rank for but rarely win the click.

QueryScope flags the pages ranking well but under-earning the click, then tells a title you can fix from an AI Overview taking the click that no rewrite recovers.

From $14.99/mo · works in Claude Code, Cursor, Cline & Windsurf

claude code
> which pages rank well but don't get clicked?
QueryScope · below-curve click rate at a good position
Fixable title
/guides/setup pos 4 · 3,120 impr · 1.1% below your pos-4 rate
Not the title, the SERP moved
/what-is-x pos 3 · 8,400 impr · 0.2% AI Overview · cite it
1 page: a better title could win ~90 clicks/mo · 1 page capped by an AI Overview · cite it
3 low-impression pages below the click floor, ignored as noise.

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 its click rate sits below what your other pages at that position earn, and that gap is clicks 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

/guides/setup · last 28 days
Google rank4 times shown3,120 clicks34
on page 1, getting clicks: looks fine

No red flag in the numbers alone.

Against your own rate at that rank

> is /guides/setup under-earning the click?
its click rate1.1% your pos-4 rate~4% an AI Overview?no
→ a fixable title, ~90 clicks/mo on the table
not a page the SERP is capping

The gap to your baseline is the flag.

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.

01 Title or the SERP

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 separates the two, because one wants an edit and the other wants a citable answer.

pos 3 · impressions high · ~0% click rate → the SERP, not the title

Low CTR at a good position: title or AI Overview?
02 Your baseline, not a table

Judged against your own pages at that rank.

A generic CTR-by-position table is a rough gut check, not a ruler: brand, query type, and SERP features move the real number too far. QueryScope measures each page against your own site's click rate at that position, so the gap it flags is real for you, not for an average.

pos 4 · 1.1% click rate vs your pos-4 rate ~4%

What each Search Console metric measures
03 Ranked by clicks you can win

The biggest real opportunity first, not the loudest percentage.

A page shown fifteen times with one click is noise, not a quick win. QueryScope sorts by the clicks a fair title could realistically win (impressions times the gap to your baseline) and floors out the tiny pages, so the pages with real upside rise to the top.

sorted by winnable clicks · below-floor pages ignored

A real page at 0.00% click rate, read honestly

One line in your IDE. Then authorize and pick a site.

install.sh
claude mcp add --transport http queryscope https://mcp.queryscope.dev/mcp

Then ask: "which pages rank well but don't get clicked?"

Win the clicks you already earned.

Connect your site and ask your agent which pages rank well but under-earn the click. One price per site count, no credits, no metering.

7-day free trial · $0 due today · cancel anytime in one click

FAQ

Reading the click you're not winning.

How does QueryScope decide a page is a CTR quick win?

It compares each page's click rate against your own pages at the same Google rank, over enough impressions for the number to be real, and flags the ones ranking well but under-earning the click. It applies a floor so low-impression pages stay out.

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 treats high impressions, a strong position, and a near-zero click rate as a SERP change, not a weak title, because the fix is a citable answer, not a rewrite.

Should I use a CTR-by-position benchmark table?

As a rough gut check only. Brand, query type, and SERP features move the real number too far for a universal table to be trusted. QueryScope judges each page against your own site's click rate at that position instead of an average someone else measured.

Will a better title get the clicks back?

When the title was the problem, often yes, and QueryScope measures the lift over the following weeks so you know rather than guess. When an AI Overview is capping the click, a title rewrite does nothing, and the honest move is to make the page the thing it cites. Writing the title from the queries you rank for walks the actual rewrite, from the phrase gap to the H1 match.

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 page needs. Whether the visitors convert is a different measurement in your analytics or product.