The terminal, not the dashboard

Google Search Console, in your terminal.

The same data Google gives you, read where you code instead of a browser tab you open twice a year.

Connect your site See the install

From $14.99/mo · works in Claude Code, Cursor, Cline & Windsurf

claude code
> how's my site doing this month?
QueryScope · last 28 days vs prior 28
Clicks 3,180 ▲ +12% Impressions 214,500 ▲ +6% CTR 1.48% ±0 Avg position 9.4 ▲ +0.8 (toward #1)
Worth a look
⚠ /docs/setup ranks informational, built to convert ▼ /changelog -54 clicks vs prior 28d
History kept since you connected, past Google's 16-month wall.

Built from the Search Console audit we run on our own SaaS, AppScreenshotStudio.

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 the history that quietly disappears. QueryScope reads the same data, in the terminal.

In the browser tab

/pricing history · in the dashboard
newesttoday oldest kept~16 months back before thatwiped
and re-filter it on every visit

The same data, a tab away and only 16 months deep.

In your terminal

> how far back does /pricing go?
kept daily since you connected
oldestJun 2024 newesttoday span26 months
past Google's 16-month wall

Ask in plain words, full history and all.

The dashboard shows you everything except the three things that change how you read it.

01 History

It forgets everything past 16 months.

Search Console keeps a rolling 16-month window with no delta export. The totals you trust today are gone unless you snapshot them forward. QueryScope stores a daily snapshot the moment you connect.

history: 16 months in the dashboard · kept since you connected, here

The 16-month wall, in full
02 The under-count

Your query clicks never add up, and it won't say why.

Google hides rare queries for privacy, so the query table always totals less than your real clicks. About half, on average. QueryScope takes volume from the page level and treats the query list as intent, never a count.

query total ≈ 53% of clicks · page total = 100%

Page-level vs query-level data
03 Intent

It shows what you rank for, not whether it fits the page.

A page built to convert can rank mostly for informational searches, and the dashboard will never flag it. QueryScope reads the page plus the queries and tells you when the intent is off.

/docs/setup ranks informational · built to convert ⚠

When a page ranks for the wrong intent

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

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

The dashboard stays where it is. This just brings the data to your editor.

Read your own search data where you already work.

One price per site count. No credits, no metering. Connect in two minutes and keep the history Google throws away.

Connect your site See pricing

7-day free trial · $0 due today · cancel anytime 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 an MCP server your AI IDE reads, so you ask in plain language and the answer lands in the terminal.

Does it replace the Search Console dashboard?

For reading and analysis, mostly. The dashboard is still there when you want to eyeball a chart or submit a sitemap. QueryScope takes over the day-to-day reading and keeps the history.

Is it the same data as Search Console?

Yes, your own, read over an OAuth grant you approve and can revoke. Plus a daily snapshot kept past Google's 16-month window, so your history does not disappear.

Which IDEs work?

Claude Code, Cursor, Cline, Windsurf, or any MCP client. Your IDE runs the LLM, so there is no separate AI fee.