---
title: "SEO performance report | SEO Skill"
description: "See what changed in Search Console and which pages, queries, countries or devices explain the movement before choosing what to investigate next."
canonical: "https://seoskill.dev/docs/reports/search-performance-overview"
language: "en"
---

# SEO performance report

Start here when clicks or impressions changed and you do not yet know why. The report breaks the movement into useful segments and points to the focused evidence worth opening next.

## Install and run the report

Install the CLI once, then run `seo start` to connect your site and Google data. After setup you can run this report yourself or ask your agent to run it.

Install the SEO CLI globally.

```
npm i -g seo
```

Run setup after installation.

```
seo start
```

Find where search performance changed and what to inspect next.

```
seo report --project example
```

## What you get from this report

See what changed in Search Console and which pages, queries, countries or devices explain the movement before choosing what to investigate next.

Best for

Clicks or impressions changed, but you do not yet know which pages, queries, countries, or devices explain it.

Needs

Search Console performance data

You get

See what changed in Search Console and which pages, queries, countries or devices explain the movement before choosing what to investigate next.

Use next

Find which search segments moved

Every report follows the same rules for missing data and outside estimates.[See how report data works](https://seoskill.dev/docs/reports#how-report-data-works).

## What you need before you run it

The report uses the information below. Optional sources are only used when you ask for them.

### 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.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### Your question is about broken pages, redirects, canonicals, indexability controls, metadata, or internal links rather than Search Console movement.

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.

Sitemap health check and technical site crawl

](https://seoskill.dev/docs/reports/site-crawl)

### 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.

Needs more evidence

## Use the report with an agent or in code

The command above is enough for most work. These options let an agent, script or application run the same report with explicit input and structured output.

### CLI

Use the report catalog when an agent, script or CI job needs predictable JSON instead of the normal terminal output. Check the current input first, then run the report with the validated parameters.

Check the current input before the agent or script runs the report.

```
seo reports describe search-performance-overview --json
```

Once the input is valid, run the report through the report catalog.

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

### MCP

An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the report.

Ask the MCP server for the current report input.

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

Run the report after the agent has checked and filled the input.

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

### TypeScript

Install the package in a Node 22 project when your application needs to run the report directly. The result includes the same evidence, warnings and limits returned through the CLI and MCP server.

Add the SEO package to your project.

```
npm install seo
```

Run the report from your TypeScript application.

```
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)
```

## What to do next

Choose the page, query, country or device segment that explains the property-level movement. Run the narrower report for that segment before recommending a sitewide change.

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

## Related reports

[

Compare Search Console movement by page, query, country or device to find which segment explains a wider gain or loss across the selected dates.

SEO segment impact report

](https://seoskill.dev/docs/reports/segment-impact)[

Check sitemap URL status, redirects and access first. Run the full technical SEO crawl only when you need page content, links, metadata and affected URLs.

Sitemap health check and technical site crawl

](https://seoskill.dev/docs/reports/site-crawl)[

Combine Search Console opportunities and crawl evidence into a ranked SEO work list with the reason and supporting report behind every item.

SEO priority report

](https://seoskill.dev/docs/reports/refresh-priorities)

## Sources used by this report

These primary sources define the provider data or search controls used by the result.

-   [Search Console Search Analytics API guidance](https://developers.google.com/webmaster-tools/v1/how-tos/search_analytics)