Striking distance SEO report

Turn near-page-one query evidence into a smaller set of page-level actions. The report groups useful patterns, but it cannot promise that a change will move a result onto page one.

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.

Runafter install

Install the SEO CLI globally.

npm i -g seo

Run setup after installation.

seo start

Find returned query and page combinations near page one.

seo striking-distance --project example

What you get from this report

Group Search Console queries around positions 11 to 20 into focused content, snippet, internal link and template review actions for each page.

Best for: You want a limited review queue based on existing search visibility.
Needs: Returned Search Console query and page rows
You get: Group Search Console queries around positions 11 to 20 into focused content, snippet, internal link and template review actions for each page.
Use next: Find opportunities for one page

Every report follows the same rules for missing data and outside estimates.See 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 query and page rows

Provides impressions, clicks, CTR, and average position for exact query and URL pairs.

Optional page content verification

Checks a limited number of candidate pages for technical conflicts and query coverage evidence.

Use a different report for these jobs

These jobs need a different report or a manual review.

You want a compact list of individual URLs rather than grouped query and template patterns.

Run second page. It assigns supporting query evidence to a page-oriented queue, which is easier when each URL needs its own owner or review rather than one shared template action.

Second page SEO report

You need to decide the exact edit for one candidate page.

Run content optimization for that URL. It adds the live page structure and its returned Search Console query evidence to build a focused brief. Striking distance only identifies and groups plausible opportunities.

Content optimization report

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.

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 striking-distance --json

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

seo reports run striking-distance --params '{"site":"sc-domain:example.com","days":28,"minImpressions":50,"limit":10,"includeBrand":false,"verifyContent":true,"verifyLimit":5}' --json

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": "striking-distance"
}

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

{
  "id": "striking-distance",
  "params": {
    "site": "sc-domain:example.com",
    "days": 28,
    "minImpressions": 50,
    "limit": 10,
    "includeBrand": false,
    "verifyContent": true,
    "verifyLimit": 5
  }
}

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(
  'striking-distance',
  {
  "site": "sc-domain:example.com",
  "days": 28,
  "minImpressions": 50,
  "limit": 10,
  "includeBrand": false,
  "verifyContent": true,
  "verifyLimit": 5
},
)

console.log(result)

What to do next

Group the returned queries by page and prioritise cases with clear demand and a strong intent match. Make a focused page or link change, then watch the same query group instead of the property average.

01Run page opportunities or audit page for the best-supported URL.
02Use internal links when the target is sound and needs relevant discovery paths.

Compare one URL with its Search Console queries and live page evidence to find focused content, CTR and coverage opportunities before rewriting the page.

Page SEO opportunities

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

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

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