---
title: "Technical SEO monitor | SEO Skill"
description: "Run recurring crawl, index and link checks together to find technical SEO changes while keeping missing or quota-limited evidence visible on every run."
canonical: "https://seoskill.dev/docs/reports/technical-watch"
language: "en"
---

# Technical SEO monitor

Run a repeatable set of technical checks across crawl health, index snapshots and link recovery. The monitor separates a confirmed change from a page it could not check.

## Install and run the monitor

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

Install the SEO CLI globally.

```
npm i -g seo
```

Run setup after installation.

```
seo start
```

Run crawl and Google index monitoring together.

```
seo technical-watch --project example
```

## What the monitor records

Run recurring crawl, index and link checks together to find technical SEO changes while keeping missing or quota-limited evidence visible on every run.

Best for

A scheduled technical check needs crawl and URL Inspection evidence in one workflow.

Needs

Current and previous limited crawl evidence

You get

Run recurring crawl, index and link checks together to find technical SEO changes while keeping missing or quota-limited evidence visible on every run.

Use next

Monitor crawl changes

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.

### Current and previous limited crawl evidence

Provides live technical and page changes for the selected same-origin scope.

### Sitemap inventory and URL Inspection snapshots

Provides a quota-limited sample of Google indexed-state evidence and prior snapshots.

### Optional link-recovery evidence

Adds broken or poorly redirected URLs that retain search value.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### The site has no comparable crawl or URL Inspection baseline yet.

Run a site crawl first to capture current live technical evidence and save the baseline. Technical watch needs comparable prior evidence to call something a regression or recovery.

Sitemap health check and technical site crawl

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

### You need exact Google indexed-state evidence for a small list of important URLs rather than combined monitoring.

Run index watch with the selected URLs. It compares exact URL Inspection snapshot fields and separates current issues, regressions, recoveries, unchanged results, and provider failures. The result remains a quota-limited Google snapshot rather than a live fetch.

URL Inspection monitor

](https://seoskill.dev/docs/reports/index-watch)

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

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

```
seo reports describe technical-watch --json
```

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

```
seo reports run technical-watch --params '{"site":"sc-domain:example.com","startUrl":"https://example.com/","sitemaps":["https://example.com/sitemap.xml"],"limit":250,"dailyLimit":200,"inspectLimit":25,"recoverLinks":true}' --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 monitor.

Ask the MCP server for the current monitor input.

```
{
  "id": "technical-watch"
}
```

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

```
{
  "id": "technical-watch",
  "params": {
    "site": "sc-domain:example.com",
    "startUrl": "https://example.com/",
    "sitemaps": [
      "https://example.com/sitemap.xml"
    ],
    "limit": 250,
    "dailyLimit": 200,
    "inspectLimit": 25,
    "recoverLinks": true
  }
}
```

### TypeScript

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

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

const result = await executeReport(
  'technical-watch',
  {
  "site": "sc-domain:example.com",
  "startUrl": "https://example.com/",
  "sitemaps": [
    "https://example.com/sitemap.xml"
  ],
  "limit": 250,
  "dailyLimit": 200,
  "inspectLimit": 25,
  "recoverLinks": true
},
)

console.log(result)
```

## What to do next

Open the crawl, index or link component that produced the change before treating the whole site as unhealthy. Fix scope, quota or provider failures first, then rerun the same watch configuration.

1.  01Audit representative regressions directly.
2.  02Compare the next run with the same scope.

## Related reports

[

Repeat a limited crawl and compare it with the previous run to find technical SEO issues that appeared, changed or disappeared after a release.

SEO crawl diff

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

Compare current Google URL Inspection results with saved snapshots to find selected pages whose index status or canonical changed since the last check.

URL Inspection monitor

](https://seoskill.dev/docs/reports/index-watch)[

Find broken URLs and weak redirects that still have Search Console value, then decide which pages to restore, redirect or leave alone using search evidence.

Broken link recovery report

](https://seoskill.dev/docs/reports/link-recovery)

## Sources used by this monitor

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

-   [Search Console URL Inspection API reference](https://developers.google.com/webmaster-tools/v1/urlInspection.index/inspect)
-   [Google sitemap guidance](https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview)
-   [Google robots.txt guidance](https://developers.google.com/search/docs/crawling-indexing/robots/intro)