SEO performance report for finding what changed and where.

Run this report from the CLI, an MCP client, or application code. Every surface uses the same report definition and returns the same evidence. JSON is the source of truth; Markdown makes it readable without hiding dates, limits, warnings, or skipped work.

What this report helps you decide

Where did Google Search performance change, and what should I investigate next?

• Clicks or impressions changed, but you do not yet know which pages, queries, countries, or devices explain it.
• You are starting an investigation and need the strongest supported leads before opening a focused report.

Command facts

Report id

search-performance-overview

Execution

Local process

Outputs

JSON and Markdown

Example parameters

site, days, recentDays, limit, includeBrand

Agent discovery

seo reports describe search-performance-overview --json

Interactive prompts

Human CLI commands only

When this report is not the right tool

These cases need a different report, more evidence, or a human decision. Do not force this report to answer a question its data cannot support.

• Your question is about broken pages, redirects, canonicals, indexability controls, metadata, or internal links rather than Search Console movement. Recommended report: Crawl a site for technical SEO issues. Run a site crawl. It fetches the site and returns page-level technical evidence that Search Console cannot provide. The search performance overview can still help prioritise sections when search movement is also relevant.
• You need a definitive explanation for why search performance changed. No automated report can prove a cause from the available Search Console comparisons. Use the overview to locate the affected dates and segments, then review releases, tracking, demand, search-result changes, and representative live pages.

Data sources and inputs

• Search Console performance data. Provides anomaly, segment, decay, overlap, visibility, and opportunity sections.
• Official Google update windows. Adds confirmed timing context when the provider data is available.

What this report checks

• Compares recent search performance with earlier data and shows whether the movement is unusual for this site.
• Finds the pages, queries, countries, and devices behind the change, then checks for declines, overlap, weak CTR, and near-page-one visibility.

How it works

• Compares recent and earlier Search Console evidence, narrows the movement by segment, then recommends follow-ups supported by the returned findings.

The JSON result keeps dates, thresholds, limits, skipped work, and source completeness beside the finding. Missing, partial, capped, filtered, and complete data remain different states.

Run the report from the CLI

Find where search performance changed and what to inspect next. Agents and CI should inspect the live schema before their first run.

seo report --project example

seo reports describe search-performance-overview --json

seo reports run search-performance-overview --params '{"site":"sc-domain:example.com","days":90,"recentDays":7,"limit":10,"includeBrand":false}' --json

Project profiles can fill supported property and analytics inputs for the human-facing commands. The catalog form shown here is explicit by design, so agents and CI jobs do not prompt or guess.

How an MCP agent should use it

Call seo_describe_report first so the agent sees when this report is useful and gets the current input schema. Then callseo_run_report with the validated parameters. Read the status, warnings, source limits, and skipped sections before acting on a finding.

{
  "id": "search-performance-overview"
}

{
  "id": "search-performance-overview",
  "params": {
    "site": "sc-domain:example.com",
    "days": 90,
    "recentDays": 7,
    "limit": 10,
    "includeBrand": false
  }
}

Use a follow-up report returned by the result instead of guessing the next tool. The local MCP server and CLI use the same report definition and evidence. Their outer transport envelopes differ.

Use the report in a TypeScript app

Install seo as a project dependency, then call the same report catalog used by the CLI and MCP. executeReportrejects an unknown report id or invalid parameters. Provider and runtime failures come back as structured results withisError set.

npm install seo

import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'search-performance-overview',
  {
  "site": "sc-domain:example.com",
  "days": 90,
  "recentDays": 7,
  "limit": 10,
  "includeBrand": false
},
)

console.log(result)

The TypeScript library guide also covers direct core functions, schema discovery, and the difference betweenexecuteReport and runReport.

What comes back and how to read it

• A readable overview of the strongest search movements, affected segments, declines, overlap, and opportunities.
• A short list of the next reports worth running, with the evidence that made each one relevant.
• Check which data was available, then follow the first recommendation whose evidence matches the change you are investigating.

Start with dataStatus, source details, warnings, and caveats. Then inspect the observed evidence before derived findings or suggested actions.

What this report cannot tell you

• The workflow cannot recover unavailable provider data or explain a movement without supporting evidence.

What to do next

1. Run one recommended focused report.
2. Use a crawl when live technical verification is required.

Related reports

• Find which search segments moved. Compare Search Console movement by page, query, country, or device.
• Crawl a site for technical SEO issues. Map a limited part of a site, run the maintained technical checks, and save a reusable evidence baseline.
• Rank the next SEO fixes. Turn crawl and Search Console evidence into one ranked implementation list.

Sources behind the guidance

These primary sources define the provider data or search controls used in the interpretation above.

• Search Console Search Analytics API guidance

Browse all reports in Multi-report workflows.