Organic ranking pages report
See which pages carry a domain's estimated search footprint and whether the returned 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.
Install the SEO CLI globally.
npm i -g seoRun setup after installation.
seo startRun 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}' --jsonWhat you get from this report
See which pages carry a domain's estimated search footprint, which URL patterns repeat and how matching pages on your own site perform in Search Console.
- Best for
- You want to see which pages carry the target or a competitor's estimated organic footprint.
- Needs
- Domain and provider row filters
- You get
- See which pages carry a domain's estimated search footprint, which URL patterns repeat and how matching pages on your own site perform in Search Console.
- Use next
- Ranked keyword footprint
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.
Domain and provider row filters
Provide a limited page-level footprint with estimated traffic, keyword counts, ranking distribution, and movement.
Optional matching Search Console property
Adds returned owner-verified page metrics for exact matching URLs.
Optional local ranked-keyword exports
Groups imported keyword rows into page evidence and repeated URL patterns without a paid API request.
Use a different report for these jobs
These jobs need a different report or a manual review.
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.
You need to assess a programmatic template family on a site you own.
Run the pSEO audit to add Search Console performance, template, overlap, and page-quality evidence before changing a working page family.
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 ranking-pages --jsonOnce 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}' --jsonMCP
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
}
}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 seoRun 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 an existing 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 existing template family.
- 03Use a current result snapshot when live competitors or intent would change the decision.
Related reports
Review a limited domain or page keyword footprint with ranking URLs, demand estimates, provider limits and optional matching Search Console query evidence.
Audit programmatic SEO templates, repeated URL patterns and Search Console demand. Review representative pages before changing a whole template.
Compare competitor keywords with Search Console themes, current rankings and repeated page patterns. Exclude irrelevant terms and evidence of existing coverage.
Sources used by this report
These primary sources define the provider data or search controls used by the result.