Organic ranking pages report

See which pages carry a domain's estimated search footprint and whether the retained paths form repeated page families. Open representative pages before treating a path pattern as a useful 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.

Runafter install

Install the SEO CLI globally.

npm i -g seo

Run setup after installation.

seo start

Run ranking pages and patterns through the report catalog.

seo reports run ranking-pages --params '{"domain":"example.com","site":"sc-domain:example.com","countryCode":"GB","languageCode":"en","minRankedKeywords":2,"limit":50}' --json

What you get from this report

Find a domain's bounded ranking-page footprint and repeated URL patterns, with optional matching Search Console page evidence.

Best for: You want to see which pages carry a first-party or competitor domain's estimated organic footprint.
Needs: Domain and provider row filters
You get: A bounded list of ranking pages with provider estimates, movement, ranking distribution, and optional exact Search Console matches.
Use next: Ranked keyword footprint

What you need before you run it

This report uses provider page URLs with estimated organic traffic, keyword counts, traffic cost, ranking distribution, and movement fields. deterministic repeated path patterns with counts, representative URLs, and evidence references. optional matching Search Console page metrics from a bounded finalised date range.

Domain and provider row filters

Provide a bounded page-level footprint with estimated traffic, keyword counts, ranking distribution, and movement.

Optional matching Search Console property

Adds retained owner-verified page metrics for exact matching URLs.

How the report finds the opportunity

The report uses existing search and page evidence to build a limited review list. An opportunity is a reason to inspect a page, not a promise of more traffic.

Validates and deduplicates provider page rows while preserving filters, pagination, totals, invalid rows, warnings, and cost.

Groups repeated path shapes into deterministic structural patterns with counts and representative URLs.

Keeps the path-pattern heuristic separate from claims about page quality, intent, demand, or how a site creates its pages.

Check the evidence behind each opportunity

Start with the query, page and date range behind each suggestion. Thin or partial evidence belongs in the review pile, not the implementation queue.

Read first	Why it matters
Result	A bounded list of ranking pages with provider estimates, movement, ranking distribution, and optional exact Search Console matches.
More detail	Repeated path patterns, representative URLs, evidence references, source coverage, and caveats for programmatic SEO review.
Read it with	Open representative pages and compare their intent, useful fields, unique value, navigation, internal links, and source data.

What the result cannot prove

Patterns found in a filtered or paginated sample may not describe the whole domain. Estimated page traffic and keyword counts are not Search Console totals.

Open representative pages and compare their intent, useful fields, unique value, navigation, internal links, and source data. A repeated path is a prompt for review. It is not a recommendation to imitate the site or create more pages. Use a current result snapshot when live competitors or intent would change the decision.

Use a different report for these jobs

You plan to infer quality, intent, or a content generator from path structure alone. You need a complete page inventory beyond the provider and output caps.

You need the queries behind one domain or page.

Run ranked keywords with the domain or page target and the filters needed for the decision.

Ranked keywords report

You need to assess a programmatic template family on a site you own.

Run the pSEO audit to add first-party performance, template, overlap, and page-quality evidence before changing a working page family.

Programmatic SEO audit

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 ranking-pages --json

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

seo reports run ranking-pages --params '{"domain":"example.com","site":"sc-domain:example.com","countryCode":"GB","languageCode":"en","minRankedKeywords":2,"limit":50}' --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": "ranking-pages"
}

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

{
  "id": "ranking-pages",
  "params": {
    "domain": "example.com",
    "site": "sc-domain:example.com",
    "countryCode": "GB",
    "languageCode": "en",
    "minRankedKeywords": 2,
    "limit": 50
  }
}

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(
  'ranking-pages',
  {
  "domain": "example.com",
  "site": "sc-domain:example.com",
  "countryCode": "GB",
  "languageCode": "en",
  "minRankedKeywords": 2,
  "limit": 50
},
)

console.log(result)

What to do next

Open representative pages from each useful path pattern and inspect their queries, fields, source data and page value. Run the programmatic audit before expanding a first-party template, and research the data source before proposing a new one.

01Run ranked keywords for a representative page.
02Run pSEO audit before changing a working first-party template family.
03Use a current result snapshot when live competitors or intent would change the decision.

Review bounded provider keyword, ranking-page, result-type, and estimate rows with an optional matching Search Console comparison.