SEO crawl history

Find the saved crawl that matches the site, date and scope you need. This keeps an agent from loading every report or comparing snapshots that covered different parts of the site.

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.

Runafter install

Install the SEO CLI globally.

npm i -g seo

Run setup after installation.

seo start

List the local crawl snapshots saved for a project.

seo crawl-reports --project example

What you get from this report

List saved SEO crawls by site and date, compare their scope and choose the right local snapshot before opening its pages or comparing two runs.

Best for: You need an id for a comparison or focused follow-up.
Needs: Local saved crawl metadata
You get: List saved SEO crawls by site and date, compare their scope and choose the right local snapshot before opening its pages or comparing two runs.
Use next: Open a saved crawl report

Every report follows the same rules for missing data and outside estimates.See 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.

Local saved crawl metadata

Provides report id, site, generated date, status, page count, issue count, and crawl scope.

Optional site and result limit

Narrows the list to the project and amount of history needed.

Use a different report for these jobs

These jobs need a different report or a manual review.

You need the pages and issues inside one saved snapshot.

Open the saved crawl report by id. It loads the report summary and lets you request its page or issue detail without fetching the site again.

SEO crawl report

You need to know what changed between two saved snapshots.

Compare the chosen crawl reports. It matches compatible page and issue evidence and separates additions, removals, regressions, and recoveries.

SEO crawl comparison

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.

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 crawl-history --json

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

seo reports run crawl-history --params '{"site":"sc-domain:example.com","limit":10}' --json

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": "crawl-history"
}

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

{
  "id": "crawl-history",
  "params": {
    "site": "sc-domain:example.com",
    "limit": 10
  }
}

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(
  'crawl-history',
  {
  "site": "sc-domain:example.com",
  "limit": 10
},
)

console.log(result)

What to do next

Choose snapshots with the date and crawl scope needed for the decision. Open one report for a focused investigation or compare two compatible runs when you need evidence of change.

01Open the chosen report.
02Compare two compatible snapshots when you need change evidence.

Open a saved SEO crawl by site or report ID and inspect its coverage, issues and affected pages without fetching the site or changing the saved result.