For SEOs and founders who live in an AI IDE
Google Search Console, in your IDE.
Ask your coding agent how your site is doing. QueryScope reads your real Search Console data, in the terminal, and tells you what is wrong. No browser tab, no third-party estimates.
> how's my site doing?
QueryScope · last 30 days vs prior 30
Clicks 1,240 ▲ +18%
Impressions 86,400 ▲ +9%
CTR 1.43% ±0
Avg position 11.2 ▲ +1.4 (toward #1)
Biggest movers
▲ /pricing +84 clicks
▼ /guides/old-post -31 clicks
Indexing: 142 of 168 indexed · 3 recently de-indexed
One line in your IDE. Then authorize and pick a site.
claude mcp add --transport http queryscope https://mcp.queryscope.dev/mcp
Works in Claude Code, Cursor, Cline, Windsurf, or any MCP client.
See
Your search performance, without leaving the editor.
Clicks, impressions, position, what moved, and which pages are slipping. Ask in plain language; get the answer where you already work.
- • Pages, queries, countries, and indexing, each a tool.
- • Your real Search Console data, not a third-party estimate.
- • History kept past Google's 16-month window.
> which pages are decaying?
Decaying pages (≥20% click drop vs prior period)
/guides/old-post 412 → 180 structural
/blog/2024-roundup 301 → 210 recoverable
/compare/x-vs-y 188 → 96 recoverable
recoverable = CTR held, impressions fell. refresh, keep the title.
> is /pricing ranking for the right queries?
/pricing 1,210 impressions · pos 8.4
Likely role (URL): transactional
Ranks mostly for: informational
⚠ Possible mismatch. A transactional page pulling mostly
informational traffic. Check the copy against who it should
convert.
what is screenshot studio informational 6.2
screenshot tool pricing transactional 9.7
Analyze
Ranking for the wrong audience? It says so.
QueryScope hands the agent each page's real ranking queries and their intent. The agent reads your page and your positioning from the repo, so it can tell you when a page converts the wrong visitor.
- • Per-page query intent, classified.
- • Striking-distance queries, one rewrite from page 1.
- • The verdict is the agent's; the data is ours.
Fix
Ask what's next?
Decay, under-clicked snippets, page-2 near-misses, and indexing problems land as a queue. Get the next one pre-briefed, claim it, ship the fix from your IDE.
- • A weekly audit files the work automatically.
- • Deduped by fingerprint. No duplicate tickets.
- • One-hour claim lease. Two sessions never collide.
> what should I fix next?
▸ P0 CTR-broken: /features
pos 4.2 · 3,400 impressions · 0.6% CTR (expected ~7%)
~210 missed clicks/mo. Rewrite the title + meta.
Claim it? [y/n] y
✓ Claimed. 1h lease. Say "done" when it ships.
Sounds right? See, analyze, fix, from your IDE.
See pricingPricing
One price per site count. No credits, no metering.
Every plan includes the full toolset. Pick by how many sites you run.
Solo
1 site connected
One site, your own.
- Full MCP in Claude Code, Cursor, Cline & Windsurf
- Overview, Pages, Queries, Countries & Indexing
- Per-page query intent + alignment analysis
- Weekly audit + fix queue (decay, CTR, indexing)
- Search history kept past Google's 16-month limit
- No credits, no per-call fees
Studio
3 sites connected
A small portfolio.
- Full MCP in Claude Code, Cursor, Cline & Windsurf
- Overview, Pages, Queries, Countries & Indexing
- Per-page query intent + alignment analysis
- Weekly audit + fix queue (decay, CTR, indexing)
- Search history kept past Google's 16-month limit
- No credits, no per-call fees
Agency
10 sites connected
Consultants and multi-site.
- Full MCP in Claude Code, Cursor, Cline & Windsurf
- Overview, Pages, Queries, Countries & Indexing
- Per-page query intent + alignment analysis
- Weekly audit + fix queue (decay, CTR, indexing)
- Search history kept past Google's 16-month limit
- No credits, no per-call fees
FAQ
Questions buyers actually ask.
Is this made by, or affiliated with, Google?
No. QueryScope is an independent tool. It reads your own Google Search Console data on your behalf, over an OAuth grant you approve and can revoke at any time.
Search Console is free. Why pay for this?
Search Console lives in a browser tab and forgets everything past 16 months. QueryScope brings the data and the analysis into the IDE where you already work, and keeps the history so you can see trends.
Which IDEs and clients work?
Claude Code, Cursor, Cline, Windsurf, or any Model Context Protocol client. Your IDE runs the LLM; QueryScope hands it the data. There is no separate AI fee.
Do you store my Search Console data?
Yes, encrypted at rest, only for the sites you connect, so the dashboard can show history. Revoke access any time from your settings. Full subprocessor list at /subprocessors.