SEO crawl report

Reopen a saved crawl when you need its summary, warnings or a focused set of pages. It is faster and more consistent than crawling the site again halfway through an investigation.

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

Open one saved crawl snapshot by id.

seo crawl-reports --id <report-id> --json

What you get from this report

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.

Best for: An agent has a report id or needs the latest saved crawl for a site.
Needs: Saved crawl report id or site
You get: 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.
Use next: Find 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.

Saved crawl report id or site

Selects one local snapshot directly or chooses the latest report for a property.

Optional detail flags

Adds the limited page or issue inventory when the compact summary is not enough.

Use a different report for these jobs

These jobs need a different report or a manual review.

You need current live evidence rather than the pages and issues stored in an earlier snapshot.

Run a new site crawl. It fetches the current limited scope and creates a new saved report instead of presenting stale evidence as current.

Sitemap health check and technical site crawl

You need to see what changed between this saved report and another crawl snapshot.

Compare the two saved crawls. It checks scope and completeness first, then reports new, resolved, persistent, and changed page or issue evidence.

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-report --json

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

seo reports run crawl-report --params '{"id":"crawl_example_20260710","includeIssues":true}' --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-report"
}

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

{
  "id": "crawl-report",
  "params": {
    "id": "crawl_example_20260710",
    "includeIssues": true
  }
}

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-report',
  {
  "id": "crawl_example_20260710",
  "includeIssues": true
},
)

console.log(result)

What to do next

Check the saved crawl date, scope and failures before reusing it. Run a focused report against that snapshot when it is still relevant, or start a new crawl when freshness could change the decision.

01Run a focused report against the saved id.
02Start a new crawl when freshness changes the decision.

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.

SEO crawl history

Find every URL affected by a technical SEO issue, inspect the crawl evidence on each page and turn one broad finding into a practical fix list.

Technical SEO affected URLs

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.