---
title: "Second page SEO report | SEO Skill"
description: "Find URLs and queries averaging positions 11 to 20, then inspect whether content, links, snippets or technical issues deserve attention on each page."
canonical: "https://seoskill.dev/docs/reports/second-page"
language: "en"
---

# Second page SEO report

Find returned page and query combinations sitting around positions 11 to 20. Average position moves around, so use the list to inspect pages rather than treating it as a fixed rank tracker.

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

Find visible pages averaging positions above 10 through 20.

```
seo second-page --project example
```

## What you get from this report

Find URLs and queries averaging positions 11 to 20, then inspect whether content, links, snippets or technical issues deserve attention on each page.

Best for

You need a compact page-oriented opportunity set.

Needs

Returned Search Console page and query rows

You get

Find URLs and queries averaging positions 11 to 20, then inspect whether content, links, snippets or technical issues deserve attention on each page.

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.

### Returned Search Console page and query rows

Provides impressions, clicks, CTR, and average position for the selected finalised window.

### Optional live-page verification

Checks a limited number of candidate pages before returning investigation prompts.

## Use a different report for these jobs

These jobs need a different report or a manual review.

[

### You want repeated query and URL patterns grouped into shared actions rather than a flat page list.

Run striking distance. It keeps query and page pairs together, groups repeated patterns, and separates content, snippet, internal-link, and technical investigations across the selected rows.

Striking distance SEO report

](https://seoskill.dev/docs/reports/striking-distance)[

### You need to know whether a specific page should be rewritten.

Audit that page first. It adds a fresh fetch, technical controls, metadata, headings, schema, links, and available Search Console query evidence. The second-page position filter alone cannot justify a rewrite.

SEO page audit

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

## 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 second-page --json
```

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

```
seo reports run second-page --params '{"site":"sc-domain:example.com","range":28,"minImpressions":50,"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": "second-page"
}
```

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

```
{
  "id": "second-page",
  "params": {
    "site": "sc-domain:example.com",
    "range": 28,
    "minImpressions": 50,
    "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(
  'second-page',
  {
  "site": "sc-domain:example.com",
  "range": 28,
  "minImpressions": 50,
  "limit": 10,
  "includeBrand": false,
  "verifyContent": true,
  "verifyLimit": 5
},
)

console.log(result)
```

## What to do next

Audit the page and query pairs that have useful demand and a realistic content match. Choose the content, snippet, link or technical change supported by that page, then check the same pair again later.

1.  01Audit the best-supported page.
2.  02Use internal links or content optimization only when the evidence points there.

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

Find pages with related search demand that may deserve an internal link to a target URL. Inspect the source page for context and intent before adding anything.

Internal linking report

](https://seoskill.dev/docs/reports/internal-links)

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