Use it first for any site. It answers “what is going on in search?” before you ask anything narrower.
Run the report
Ask your agent:
Run the SEO report for example.com
The hosted MCP runs seo_report. In a terminal, name the site:
seo report --site example.com
--site takes a domain, a URL or a Search Console property. seo sites lists the properties your sign-in can read.
Every site at once
In the weekly site audit beta, seo report with no site gives last week across all your audited sites: what needs a look, with one next step each, and what was quiet. It is the same summary as the Monday email, and it ends with the --site to ask about next. On a machine, run seo login first. Without the beta, name a site.
What comes back
Without a section, the report returns the overview: clicks, impressions, click-through rate and average position against the previous period, split by device, with the top pages and queries and how they changed. It also returns each section’s row count and its top rows, so you can see which section is worth opening.
If Bing is connected in the CLI or the local MCP server, the overview also shows Google and Bing clicks and impressions for the same dates, and each engine’s share of those clicks. The two are never added together. When Bing sends more clicks than Google, Bing’s own overview follows, with the pages and queries that moved.
The overview also shows your Google Analytics sessions for the same dates. You do not pick the property: the report finds the one whose web stream matches the site, names it, and shows:
- Organic Search sessions from Google, the number to set beside Search Console clicks.
- Organic Search sessions from every search engine, Bing and DuckDuckGo included, and how many each engine sent.
- Sessions from all channels, so you can tell a search drop from a drop in all traffic.
- Visits from AI assistants such as ChatGPT, Perplexity, Claude, Gemini and Copilot, by source, with the pages they land on. Only visits that pass a referrer or tag count. An AI app that sends neither shows as Direct.
Sessions are Google Analytics’ own count, so they never equal clicks. If no web stream matches, the report says so and carries on without it.
Ask for one section
| Section | What it lists |
|---|---|
overview | Site totals against the previous period, by device, with the top pages and queries and Google Analytics sessions. |
quick-wins | Query and page pairs at positions 4 to 10 with a click-through rate below your site’s own curve for that position. |
low-ctr | Query and page pairs at positions 1 to 4 with a click-through rate below your site’s own curve. These are titles and snippets to review. |
striking-distance | Queries just outside the top positions, with impressions, for pages that already rank. |
second-page | Pages with an average position of 11 to 20, and their queries. |
content-decay | Query and page pairs that lost clicks against the previous period. |
cannibalization | Queries where more than one of your pages gets impressions, with each page’s share. |
traffic-drop | Daily clicks and impressions checked for sudden changes, with Google updates whose dates overlap. |
ai-queries | Queries that look like AI conversations and agent searches: replies such as “yes”, follow-ups such as “what about…”, agent prompts, search operators and long chat-style questions. Rewordings are grouped into one question. A heuristic, covering the last 90 days. |
bing | Bing’s top queries and pages with Google’s numbers for the same rows beside them. Needs Bing connected in the CLI or the local MCP server. |
Ask for a section by name:
Show me the low-ctr section for example.com
In a terminal:
seo report --site example.com --section low-ctr
The first answer is a summary. Add --detail rows for the next page of rows, with --offset to move through them, or --detail full for every field. Add --json for structured output.
Sections that list pages also check their top 20 URLs live, so you can see a page that now redirects or returns an error before you spend time on it.
Dates
The report uses the latest final Search Console data: the last 28 days, or 90 days for traffic-drop and ai-queries. You can ask for a start and end date instead:
seo report --site example.com --start-date 2026-09-01 --end-date 2026-09-28
Questions people ask AI
People who use Google’s AI Mode, and AI assistants that search for them, leave a trail in Search Console: a bare “yes”, “is it common”, “what about smith”, a search with site: added, or a whole agent prompt. The ai-queries section finds these queries, groups the rewordings of one question, and shows which page Google showed for each.
It is a pattern match on the query text, not a label from Google. Search Console does not mark AI Mode, and its Generative AI report is not in its API. Some of these queries were typed by people, and rare ones are left out, so the counts are a minimum.
Read it carefully
The click-through rate curve is built from your own site’s data. It is a useful yardstick, not a Google rule. In traffic-drop, a Google update that overlaps a change only shows the timing matched. It does not prove the update caused it.
For one page, use seo page. To check a release or an update, use seo compare.