Domain organic search overview

Get a quick country-level view of a domain before opening its pages and keywords. Provider estimates and owner-verified Search Console totals stay side by side, with no invented ratio between them.

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 domain search footprint through the report catalog.

seo reports run domain-overview --params '{"domain":"example.com","site":"sc-domain:example.com","countryCode":"GB","languageCode":"en","days":28}' --json

What you get from this report

Review estimated organic traffic, ranked keywords and ranking distribution for a domain, with optional matching Search Console evidence kept separate.

Best for: You need a quick independent footprint before deeper competitor or page research.
Needs: Domain and country market
You get: Review estimated organic traffic, ranked keywords and ranking distribution for a domain, with optional matching Search Console evidence kept separate.
Use next: Ranking pages and patterns

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 country market

Define the domain and country-level provider database used for the independent search footprint.

Optional matching Search Console property

Adds owner-verified clicks, impressions, click-through rate, and average position for a finalised date range.

Use a different report for these jobs

These jobs need a different report or a manual review.

You need the individual terms or pages behind the footprint.

Run ranked keywords for a limited term-level view, or ranking pages when page families and representative URLs matter more.

Ranked keywords report

You need a current result for one query, location, and device.

Run SERP results. A country-level provider database cannot replace a live result snapshot with explicit location and device settings.

Live SERP results 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 domain-overview --json

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

seo reports run domain-overview --params '{"domain":"example.com","site":"sc-domain:example.com","countryCode":"GB","languageCode":"en","days":28}' --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": "domain-overview"
}

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

{
  "id": "domain-overview",
  "params": {
    "domain": "example.com",
    "site": "sc-domain:example.com",
    "countryCode": "GB",
    "languageCode": "en",
    "days": 28
  }
}

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(
  'domain-overview',
  {
  "domain": "example.com",
  "site": "sc-domain:example.com",
  "countryCode": "GB",
  "languageCode": "en",
  "days": 28
},
)

console.log(result)

What to do next

Use the footprint to choose a narrower domain, page or keyword investigation. Keep provider estimates separate from Search Console measurements, and check current results before changing priorities.

01Run ranking pages to find the URLs behind the footprint.
02Run ranked keywords to inspect a limited set of terms and ranking pages.
03Start with Search Console opportunity reports before changing priorities for a site you own.

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.

Organic ranking pages report

Review a limited domain or page keyword footprint with ranking URLs, demand estimates, provider limits and optional matching Search Console query evidence.

Ranked keywords report

See what changed in Search Console and which pages, queries, countries or devices explain the movement before choosing what to investigate next.

SEO performance report

Sources used by this report

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