---
title: "SEO priority report | SEO Skill"
description: "Combine Search Console opportunities and crawl evidence into a ranked SEO work list with the reason and supporting report behind every item."
canonical: "https://seoskill.dev/docs/reports/refresh-priorities"
language: "en"
---

# SEO priority report

Rank a mixed list of technical and content work using the evidence already collected for the project. The score helps order the queue, but it should never hide a weak or missing input.

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

Build a limited review queue from supported search signals.

```
seo refresh-priorities --project example
```

## What you get from this report

Combine Search Console opportunities and crawl evidence into a ranked SEO work list with the reason and supporting report behind every item.

Best for

A content team needs one queue assembled from several site data sources.

Needs

Search Console diagnosis and opportunity reports

You get

Combine Search Console opportunities and crawl evidence into a ranked SEO work list with the reason and supporting report behind every item.

Use next

Audit one page

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.

### Search Console diagnosis and opportunity reports

Provides decay, position, CTR, query overlap, and property movement evidence with shared source details.

### Optional live-page verification

Checks a limited number of candidates before the workflow recommends deeper investigation.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You only want technical crawl fixes and do not want content or Search Console opportunities mixed into the queue.

Run top fixes against a saved crawl. It ranks crawl issue groups by rule evidence and affected scope, with sample URLs and verification guidance still attached.

Technical SEO priority report

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

### You need an exact content brief for one page already selected for review.

Run content optimization for that URL. It adds the live page structure and returned query evidence needed for a focused brief. Refresh priorities orders candidates but cannot decide that a rewrite is required.

Content optimization report

](https://seoskill.dev/docs/reports/content-optimization)

## 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 refresh-priorities --json
```

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

```
seo reports run refresh-priorities --params '{"site":"sc-domain:example.com","days":90,"recentDays":7,"limit":10,"includeBrand":false,"verifyContent":true,"verifyLimit":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": "refresh-priorities"
}
```

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

```
{
  "id": "refresh-priorities",
  "params": {
    "site": "sc-domain:example.com",
    "days": 90,
    "recentDays": 7,
    "limit": 10,
    "includeBrand": false,
    "verifyContent": true,
    "verifyLimit": 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(
  'refresh-priorities',
  {
  "site": "sc-domain:example.com",
  "days": 90,
  "recentDays": 7,
  "limit": 10,
  "includeBrand": false,
  "verifyContent": true,
  "verifyLimit": 5
},
)

console.log(result)
```

## What to do next

Inspect the evidence behind the highest-ranked technical and content items before accepting their order. Update the queue when a missing input, stale crawl or page review changes the case for the work.

1.  01Audit the highest-supported page.
2.  02Record and measure any material change.

## Related reports

[

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

Build a content brief from one page, its Search Console queries and the headings or topics already present. Keep every suggestion tied to demand.

Content optimization report

](https://seoskill.dev/docs/reports/content-optimization)[

Compare matched Search Console periods around a recorded SEO change and keep releases, demand shifts and other confounders beside the result.

SEO change measurement

](https://seoskill.dev/docs/reports/measure-change)

## Sources used by this report

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

-   [Search Console Search Analytics API guidance](https://developers.google.com/webmaster-tools/v1/how-tos/search_analytics)