---
title: "Technical SEO priority report | SEO Skill"
description: "Rank technical SEO issues using crawl severity, affected pages and available search evidence so the next fix has a clear reason and supporting evidence."
canonical: "https://seoskill.dev/docs/reports/top-fixes"
language: "en"
---

# Technical SEO priority report

Turn a long crawl issue list into a smaller implementation queue. The ranking combines reach and available value, but you should still confirm intent on representative pages before changing a template.

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

Turn a crawl into a short technical implementation queue.

```
seo crawl-queue https://example.com
```

## What you get from this report

Rank technical SEO issues using crawl severity, affected pages and available search evidence so the next fix has a clear reason and supporting evidence.

Best for

A broad crawl is too large to act on directly.

Needs

Saved or fresh crawl findings

You get

Rank technical SEO issues using crawl severity, affected pages and available search evidence so the next fix has a clear reason and supporting evidence.

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, affected pages, rule severity, and technical evidence.

### Joined Search Console and Google Analytics page metrics

Adds available search visibility, sessions, users, and conversions for affected pages.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You need every URL affected by one known crawl rule rather than a ranked list of issue groups.

Run affected URLs with the saved crawl and rule id. It returns the matching URL inventory and issue evidence for that rule, which is the right input for estimating scope and planning a template-level fix.

Technical SEO affected URLs

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

### You need to confirm that a release fixed the selected technical issue.

Run a comparable crawl diff after the release. It separates new, resolved, and persistent findings while keeping fetch and scope changes visible. A priority score cannot verify implementation.

SEO crawl diff

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

## 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 top-fixes --json
```

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

```
seo reports run top-fixes --params '{"reportId":"crawl_example_20260710","category":"metadata","limit":5}' --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": "top-fixes"
}
```

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

```
{
  "id": "top-fixes",
  "params": {
    "reportId": "crawl_example_20260710",
    "category": "metadata",
    "limit": 5
  }
}
```

### 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(
  'top-fixes',
  {
  "reportId": "crawl_example_20260710",
  "category": "metadata",
  "limit": 5
},
)

console.log(result)
```

## What to do next

Open the affected URLs behind the highest-ranked issue and inspect representative pages before changing a template. Recrawl the same scope after the fix so the priority queue reflects fresh evidence.

1.  01Explain the selected rule.
2.  02Open its affected URLs and verify a fix with another 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)[

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)