SEO prioritization

Know which SEO change to make first.

QueryScope reads your own Search Console against the searches you chose and hands your agent one change at a time, in an order it can explain, holding back any page that is still being measured.

From $49/mo, everything included · works in Claude Code, Cursor, Cline and Windsurf

claude code
> what should I work on?
QueryScope · one change, and why this one
search pages ranking for wrong search intent page /find-pages-ranking-for-the-wrong-intent move 0 · get it indexed why first Google read the page and is not keeping it
43 targets you scored higher sit on pages still being measured. The first opens on 2026-11-15.
→ the best work available today, not the best work on the site.

The answer QueryScope gave on its own site, 2026-11-14.

Why a list is not enough

Forty findings and no order is a week of guessing.

An audit hands you everything it found at once, and the hard part, deciding what to do first, is left to you. Worse, nothing stops you editing a page you changed last week, which leaves you with two changes and no way to tell which one worked. A prioritization tool has to say what goes first, why, and what to leave alone until it has been read.

Four rules, applied in order, every time you ask.

01 Judge what shipped

A change ready to judge comes before any new work.

If a change you already made has reached the end of its window, reading it comes first. Its baseline ages a little more every day it sits unjudged, and every later pick is made without what it showed. Reading it costs nothing: the data is already stored.

measure first · then open new work

How a change gets judged
02 The index gate

A page Google is not keeping indexed jumps the queue.

A page out of the index cannot be pushed, re-aimed or rewritten into ranking, so every other move on it is wasted until it is back. A page that is merely new and waiting for its first crawl does not count as blocked: it gets time, because there is nothing to fix yet.

not indexed → nothing else on the page can work

Find the pages Google is not indexing
03 What you said matters

Then the searches you scored highest, closest to done last.

Every search in your plan carries a score from 0 to 3 for how close it is to what you sell, set by your agent from your repo. The queue sorts on that first. Inside each score: searches the site can reach before long shots, money searches before the pages that feed them, known demand before unknown, and then whichever is furthest from ranking.

your score · reach · money before feeder · demand · distance

Keyword research over MCP
04 What it holds back

A page still being measured is not handed back.

Once a change is recorded, that page is held until the window for that kind of change closes: 4 weeks for a title, 6 for links and redirects, up to 90 days for content, counted from the day Google rereads the page. A second edit inside the window would leave two changes and no answer. You see what is held and when it opens.

28 · 42 · 90 days, from the recrawl

How long Google takes to recrawl a page

On 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

1

where clicks happen · was 0 on 21 May

Below page 1

10

ranking, earning almost nothing · was 2 on 21 May

Not ranking

46

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

Read from production on 2026-10-02. Its first tracked searches shown.

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

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

Works the same in Cursor, Cline and Windsurf. Your IDE opens a browser once to authorize.

Then ask: “what should I work on?”

FAQ

How the order works.

How does QueryScope decide which SEO change to make first?

In a fixed order. A change you already made that is ready to judge comes first. Then a page Google is not keeping indexed. Then the searches you scored highest for your business, and inside each score the ones the site can reach, money searches before the pages that feed them, known demand before unknown, and the one furthest from ranking. Pages still being measured are left out until their window closes.

Why does it put my score ahead of search volume?

Because volume is often unknown. Long, specific searches are the ones buyers type, and keyword tools frequently decline to price them. A queue that sorted on volume would bury them or rank them as zero. Your score says what the search is worth to the business; demand breaks the tie inside it.

Can I work on something else?

Yes. Every change it hands back comes with what is next in line and the figures that ranked it, so your agent can name another search and take that one instead. The one thing it will not do is hand back a page that is still being measured, because a second edit there wipes out the reading of the first.

Does it make the change?

No. Your agent makes the edit in your repo. Anything a visitor reads (a title, a paragraph, a new page) is written into queryscope.md first and waits for your commit. Indexing and internal links change nothing a reader sees, so those go ahead without asking.

Will doing them in this order bring more signups?

QueryScope cannot say. It reads your Search Console and stops at the click. It measures whether each change moved the search it was for; what visitors do after they arrive is in your analytics.

Get the one next change for your site.

Connect your site, let your agent read your repo for what you sell, and ask what to work on.

7-day free trial · nothing due today · cancel in one click

More of what your agent can ask