---
title: "SEO crawler rules | SEO Skill"
description: "Browse the technical checks built into the SEO crawler and find the exact rule ID needed for plain-English guidance or affected URLs from a saved crawl."
canonical: "https://seoskill.dev/docs/reports/crawler-rules"
language: "en"
---

# SEO crawler rules

Browse the maintained rule catalog before running a crawl or when a finding needs a translation. Each rule includes the ID used by follow-up reports and commands.

## Install and run the tool

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

Install the SEO CLI globally.

```
npm i -g seo
```

Run setup after installation.

```
seo start
```

Browse the technical checks built into the crawler.

```
seo rules
```

## What the tool gives you

Browse the technical checks built into the SEO crawler and find the exact rule ID needed for plain-English guidance or affected URLs from a saved crawl.

Best for

An agent needs a valid rule id.

Needs

Local crawler rule catalog

You get

Browse the technical checks built into the SEO crawler and find the exact rule ID needed for plain-English guidance or affected URLs from a saved crawl.

Use next

Understand a crawler issue

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.

### Local crawler rule catalog

Provides the current rule ids, categories, severity, and guidance metadata.

### Optional rule category

Limits the catalog to checks such as metadata, canonicals, or indexability.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You need a plain-English explanation and verification steps for one rule.

Run explain crawl issue with the rule id. It adds the rule meaning, why it may matter, practical fix guidance, and a check you can perform after the change.

Technical SEO issue guide

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

### You need the URLs currently affected by a rule in a saved crawl.

Run affected URLs with the saved crawl and rule id. It returns the observed page instances, counts, limits, and available search evidence rather than the rule definition alone.

Technical SEO affected URLs

](https://seoskill.dev/docs/reports/affected-urls)

## Use the tool 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 tool 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 tool with the validated parameters.

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

```
seo reports describe crawler-rules --json
```

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

```
seo reports run crawler-rules --params '{"category":"metadata"}' --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 tool.

Ask the MCP server for the current tool input.

```
{
  "id": "crawler-rules"
}
```

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

```
{
  "id": "crawler-rules",
  "params": {
    "category": "metadata"
  }
}
```

### TypeScript

Install the package in a Node 22 project when your application needs to run the tool 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 tool from your TypeScript application.

```
import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'crawler-rules',
  {
  "category": "metadata"
},
)

console.log(result)
```

## What to do next

Choose the rule by its maintained meaning rather than its severity label alone. Open the rule guidance, then inspect affected URLs from a real crawl before deciding that the site needs a change.

1.  01Explain the selected rule.
2.  02Fetch affected URLs from a saved crawl.

## Related reports

[

Look up one technical SEO crawler rule in plain English. See why it may matter, how to fix it and what to check on a live page after the change.

Technical SEO issue guide

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

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

](https://seoskill.dev/docs/reports/affected-urls)