Your pages, competing with each other
Find the pages competing for the same search.
QueryScope reads your own Search Console week by week and tells you when two of your pages keep taking turns at the top of one search: the one pattern of keyword cannibalization worth fixing.
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
Two pages on one search is normal. Two pages taking turns is the problem.
Most sites rank more than one page for their best searches, and Google says that is fine: three pages in one result "doesn't seem problematic to me just because it's 'more than 1'," in John Mueller's words. The conflict is when Google cannot decide between them, and the lead keeps passing back and forth from week to week. No single week shows it. The sequence does.
Counted
The same flag fires on most of your best searches.
Read week by week
The return is the signal. A one-way move is Google settling.
Three reads turn "two of my pages rank for this" into a verdict on whether they are actually competing.
It fires when the lead goes back to a page it lost.
QueryScope reads which of your URLs led the search in each of the 13 most recent weekly snapshots of your Search Console data. A move from an old page to a new one and staying there is Google settling, so it passes. A lead that returns to a page it had already lost is Google undecided, so it is named, with the week it last went back.
A → B → A · went back → two pages trading places
Keyword cannibalization in Search Console: the honest testMost multiple rankings need nothing.
Ahrefs hand-reviewed 80 keywords where one site ranked with several pages and found one case that needed action. A checker that flags every search with two of your URLs on it hands you the other 79 too, and merging pages that were never competing is how a fix costs traffic. A URL also needs three impressions in a week before it counts as the leader, so a tie decided by one impression never reads as a swap.
80 multiple rankings reviewed · 1 needed action
What each Search Console metric measuresDifferentiate, merge, or point the plan at one page.
Your agent has both pages open in the repo, which is where the decision lives: give each page its own job, fold one into the other with a redirect, or aim the search at one page in your plan. A change to what a visitor reads goes into queryscope.md first, and nothing is edited until you commit it.
named pages · dated last swap · your commit decides
Which page survives a mergeOn 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 pages that compete for one search.
What counts as keyword cannibalization here?
Two of your pages taking turns leading one search across recent weeks, where the lead goes back to a page it had already lost. Two pages ranking side by side is normal and is left alone: Google has said that several pages from one site in a result is not a problem in itself.
Why not flag every search where two of my pages rank?
Because that is most of a healthy site. Ahrefs hand-reviewed 80 keywords with multiple rankings from one site and found one that needed action. A flag on count would bury that one under the rest and push merges on pages that were never competing.
Which searches does it check?
Any search you name to your agent, and every search declared in your plan. It reads the 13 most recent weekly snapshots of your own Search Console data, and a URL needs three impressions in a week before it counts as leading.
What should I do when two pages are trading places?
Pick one job per page. Retarget one of them so each answers a different search, or redirect the weaker one into the stronger and keep a single page on the topic, or keep both and aim the search at one of them in your plan. The guide on which page survives a merge covers the choice.
Does QueryScope change my pages?
No. Your own agent makes every edit. A change to what a visitor reads is written into queryscope.md as a proposal, and it waits there until you commit it.
Settle the searches your pages keep trading.
Connect your site, declare the searches worth winning, and your agent tells you which of them two of your pages are taking turns on.
7-day free trial · nothing due today · cancel in one click
Other things it finds in your Search Console