---
title: "Technical SEO affected URLs | SEO Skill"
description: "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."
canonical: "https://seoskill.dev/docs/reports/affected-urls"
language: "en"
---

# Technical SEO affected URLs

Open the URLs behind one crawl finding and see the evidence recorded on each page. Use this when a summary count is too broad to fix safely.

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

Run find urls affected by a crawl issue through the report catalog.

```
seo reports run affected-urls --params '{"reportId":"crawl_example_20260710","ruleId":"missing_title","severity":"high","limit":50}' --json
```

## What you get from this report

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.

Best for

A crawl summary has identified a pattern and you need the limited URL inventory.

Needs

Saved or fresh crawl findings

You get

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.

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.

### Saved or fresh crawl findings

Provides issue instances, rule ids, affected pages, severity, and technical evidence.

### Optional rule, category, and severity filters

Narrows the result to the finding you are ready to inspect.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You know several crawl issues exist but need to decide which ones deserve attention first.

Run top fixes. It compares issue severity, affected-page counts, and available search or analytics value so you get a ranked work list rather than the URLs for one chosen issue.

Technical SEO priority report

](https://seoskill.dev/docs/reports/top-fixes)[

### You do not yet understand what a crawler rule means or whether its suggested fix applies to your site.

Explain the crawl issue first. It adds the maintained rule meaning, rationale, fix, and verification method. Then return here when you are ready to inspect the real affected URLs.

Technical SEO issue guide

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

## 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 affected-urls --json
```

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

```
seo reports run affected-urls --params '{"reportId":"crawl_example_20260710","ruleId":"missing_title","severity":"high","limit":50}' --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": "affected-urls"
}
```

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

```
{
  "id": "affected-urls",
  "params": {
    "reportId": "crawl_example_20260710",
    "ruleId": "missing_title",
    "severity": "high",
    "limit": 50
  }
}
```

### 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(
  'affected-urls',
  {
  "reportId": "crawl_example_20260710",
  "ruleId": "missing_title",
  "severity": "high",
  "limit": 50
},
)

console.log(result)
```

## What to do next

The URL list is ready for inspection, not bulk editing. Open representative pages, confirm that the rule conflicts with their purpose, then recrawl the same scope after the fix.

1.  01Use explain issue for the rule guidance.
2.  02Audit representative URLs and recrawl after the fix.

## 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)[

Audit one URL for technical SEO, metadata, canonicals, schema, links and Search Console queries. See the live evidence before changing the page.

SEO page audit

](https://seoskill.dev/docs/reports/audit-page)[

Compare two saved SEO crawls to find new, fixed and changed technical issues. Check the crawl scope before treating the difference as real or complete.

SEO crawl comparison

](https://seoskill.dev/docs/reports/compare-crawls)