The gate move
Find the pages Google isn't indexing.
A page outside the index earns nothing, no matter how good it is, so QueryScope separates the pages genuinely blocked from the ones Google is handling for you.
From $14.99/mo · works in Claude Code, Cursor, Cline & Windsurf
Built from the Search Console audit we run on our own SaaS, AppScreenshotStudio.
Why the number misleads
"Not indexed" is three different situations.
One page is genuinely blocked and you can fix it today. Another was found and simply hasn't been crawled yet, where the honest answer is usually patience. Most of the rest are duplicates and redirects Google is resolving correctly, and touching them would be work for nothing. Counted together they look like one large problem, which is why the number gets ignored right up until a page that was earning clicks quietly falls out.
As one number
The count hides which ones matter.
Split by what you'd do
The split is a morning's work.
Three reads turn a coverage count into the two or three pages worth opening your editor for.
Sorted by what you would actually do about it.
QueryScope groups every unindexed URL by its reason and pairs each group with the fix: a noindex tag, a redirect chain, a 404, a page Google found but has not crawled, a duplicate it is resolving on its own. The groups that need no work say so plainly, which is the part a raw coverage number cannot tell you.
blocked → fix it · waiting → leave it · duplicate → nothing to do
What each coverage state actually meansThe unindexed page that was earning traffic comes first.
A long list of unindexed URLs is not a priority order. QueryScope only raises a page as urgent when it can show the page matters: it earned real clicks in the last 28 days, or it has a change you are still measuring, whose result cannot be judged at all while the page sits outside the index. Everything else stays in the group counts instead of on your plate.
still earned 41 clicks · open fix, lift unmeasurable while out
Reading a real account this way for 30 daysA page that dropped out is a different job from one that never landed.
Dropping out is an event with a date and a cause worth hunting: a stray noindex, a canonical now pointing elsewhere, a redirect, content Google decided to stop keeping. Never getting in is usually weaker: the page is thin, duplicated, or barely linked to. QueryScope reports the two separately, and for the never-landed case it names your strongest existing pages to link from, so your agent can add the links in the repo.
dropped out → find the cause · never landed → link to it
When competing URLs were never separate pagesOne line in your IDE. Then authorize and pick a site.
claude mcp add --transport http queryscope https://mcp.queryscope.dev/mcpThen ask: "which of my pages aren't indexed?"
Get the page in the index. Then everything else can work.
Connect your site and ask your agent what is out of the index and why. One price per site count, no credits, no metering.
7-day free trial · $0 due today · cancel anytime in one click
FAQ
Reading what is out of the index.
Why does Search Console say my pages aren't indexed?
Because that one label covers unrelated situations: a page you blocked with a noindex tag, a URL that 404s, a redirect, a page Google found but has not crawled yet, and a duplicate where Google picked a different canonical. Only the first group is work you can do today, and QueryScope separates them for you.
Which unindexed pages should I actually fix?
The ones you can prove matter. QueryScope raises a page as urgent when it earned real clicks in the last 28 days, or when it has a change you are still measuring, because that result cannot be judged while the page is outside the index. The rest stay as group counts rather than a to-do list.
Can QueryScope request indexing for me?
No, and no tool honestly can for ordinary pages. QueryScope holds a read-only grant you approve and can revoke, and the URL Inspection API is read-only by design. Google's separate Indexing API covers only job postings and broadcast events. So QueryScope finds the block and names the cause; the request-indexing click stays yours in Search Console.
Does it check every page on my site?
It checks the URLs it knows about, which come from your sitemap, once a day. Worth knowing why: the full page-indexing report exists only inside the Search Console interface and is exposed by no API, so every tool in this space reconstructs coverage from URL Inspection over the URLs it can see. A page missing from your sitemap is a page nothing here can inspect.
Is "found but not indexed yet" a problem?
Usually not, at a small site. It often means Google has the URL queued and has not judged it worth crawling yet, and the honest response is patience plus a few internal links from pages that already earn traffic. QueryScope names those source pages so your agent can add the links. At larger scale the same signal points at thin templated pages spending your crawl budget.