The terminal, not the dashboard
Google Search Console, in your terminal.
Your own search data read where you code: what a search is worth, where you stand on it, which page is aimed at it, and the one change that moves it.
From $49/mo, everything included · works in Claude Code, Cursor, Cline and Windsurf
The real answer this site got on 2026-09-23. The rivals are the ones Google actually returned.
Side by side
The dashboard is fine. The browser tab is the problem.
Search Console is good at what it does. The friction is the alt-tab, the re-filtering, and a history that rolls off at 16 months. QueryScope reads the same data where your code is, and hands back the next change rather than another table.
In the browser tab
Everything Google has, a tab away and 16 months deep.
In your editor
Ask in plain words. Get one thing to change.
The dashboard shows you everything except the three things that change how you read it.
If any of the terminology is new, the Search Console glossary defines every metric and indexing state in a sentence, each with the caveat that makes it misleading.
It forgets everything past 16 months.
Search Console keeps a rolling 16-month window with no delta export, so the totals you trust today are gone unless something snapshots them forward. On connect QueryScope backfills the full window Google still has, then stores a daily snapshot from that day on. That stored history is also what every change you make gets measured against later.
16 months in the dashboard · backfilled once, then kept daily, here
The 16-month wall, in fullYour query clicks never add up, and the dashboard will not say why.
Google leaves rare searches out of the query report for privacy, so that table always totals less than your real clicks. Ahrefs put the hidden share near half across 22 billion clicks in April 2025. QueryScope takes volume from the page level and reads the query list for what a page is shown for, never as a count.
query total ≈ 53% of clicks · page total = 100%
Page-level vs query-level dataGoogle decides what a page is for, and it moves.
A page you wrote for one search quietly gets shown for another, and the dashboard reports both without ever saying the subject changed. QueryScope prints what Google shows each page for now, how much of what it used to be shown for is still coming through, and which searches are new. It reads shape rather than volume, because rare searches go private and a search that disappears from the list may only have gone quiet.
what it is shown for · how much of that held · what is new
When a page ranks for the wrong intentOne line in the repo of the site you want to work on. 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: “where do I stand on the searches I care about?”
Read your own search data where you already work.
Every feature in every plan. Connect in two minutes, keep the history Google drops, and get one change at a time.
7-day free trial · nothing due today · cancel in one click
FAQ
Reading Search Console in the terminal.
Is this a command-line tool I have to learn?
No. There are no flags to memorize. QueryScope is a Search Console MCP server your AI IDE reads, so you ask in plain language and the answer lands in the terminal, next to the code you would change.
Can I ask how my whole site is doing?
It answers per search rather than per site. Name a search and you get how many people run it a month, where you stand on it, which page is aimed at it, and what to change. Ask what to work on and you get the single next move across the searches your plan declared, with the page it belongs to and who is ranking above you. For a chart of site totals, the dashboard is still the right tab.
Does it replace the Search Console dashboard?
For the day-to-day question of what to change next, yes, and that is most of what anyone opens it for. The dashboard stays where it is for eyeballing a chart, submitting a sitemap, or inspecting a URL by hand.
Is it the same data as Search Console?
Yes, your own, read over a read-only OAuth grant you approve and can revoke. Plus a daily snapshot kept past Google's 16-month window, so your history stays. Below position 10, where Search Console records nothing, QueryScope reads the live results page instead, for the searches your plan declared. Every position on page 1 comes from Search Console itself.
Which IDEs work?
Claude Code, Cursor, Cline, Windsurf, or any MCP client: one URL in the IDE's MCP config, and it opens a browser once to authorize. Your IDE runs the LLM, so there is no separate AI fee.
Is QueryScope connected to Google?
QueryScope is independent and not affiliated with Google. It reads your own Search Console over a read-only grant you approve, and you can revoke it at any time from your Google account or from ours.