---
title: "Domain organic search overview | SEO Skill"
description: "Review estimated organic traffic, ranked keywords and ranking distribution for a domain, with optional matching Search Console evidence kept separate."
canonical: "https://seoskill.dev/docs/reports/domain-overview"
language: "en"
---

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

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 a country-level estimate of a domain's organic footprint beside optional owner-verified Search Console totals.

Best for

You need a quick independent footprint before deeper competitor or page research.

Needs

Domain and country market

You get

A country-level domain footprint with estimated traffic, keyword counts, ranking distribution, movement, and provider provenance.

Use next

Ranking pages and patterns

## What you need before you run it

This report uses country-level provider estimates for organic traffic, ranked keywords, traffic cost, ranking buckets, and movement counts. optional matching Search Console totals for a finalised date range, kept as a separate first-party source. provider coverage, cache state, request filters, warnings, observation time, and local request cost.

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

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

01

Collects estimated organic traffic, ranked keywords, traffic cost, ranking buckets, and movement counts from one provider capability.

02

Keeps provider estimates and matching Search Console totals separate so an estimate is never presented as measured traffic.

03

Preserves request filters, source coverage, invalid rows, cache state, observation time, warnings, and local request cost.

## 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 country-level domain footprint with estimated traffic, keyword counts, ranking distribution, movement, and provider provenance. |
| More detail | Optional owner-verified Search Console totals beside the estimate, with separate dates, semantics, coverage, and caveats. |
| Read it with | Use Search Console for actual performance on a site you own. Use the provider estimate to choose which domains, pages, and terms deserve independent research. |

## What the result cannot prove

Provider estimates follow the provider database and update schedule. Search Console uses the selected finalised date range. Country-level domain research does not describe a specific city, postcode, or device.

Use Search Console for actual performance on a site you own. Use the provider estimate to choose which domains, pages, and terms deserve independent research. Read coverage and warnings before reading an empty or small footprint as a real zero. Start with Search Console opportunity reports before changing priorities for a site you own.

## Use a different report for these jobs

You need a live rank for one query, place, and device. You want estimated traffic treated as measured visits or Search Console clicks.

[

### You need the individual terms or pages behind the footprint.

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

Ranked keywords report

](https://seoskill.dev/docs/reports/ranked-keywords)[

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

](https://seoskill.dev/docs/reports/serp-results)

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

### 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": "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
  }
}
```

### 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(
  '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.

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

## Related reports

[

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

Organic ranking pages report

](https://seoskill.dev/docs/reports/ranking-pages)[

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

Ranked keywords report

](https://seoskill.dev/docs/reports/ranked-keywords)[

See where clicks and impressions changed, which pages or queries account for the movement, and what to inspect next.

SEO performance report

](https://seoskill.dev/docs/reports/search-performance-overview)

## Sources used by this report

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

-   [DataForSEO domain rank overview API reference](https://docs.dataforseo.com/v3/dataforseo_labs-google-domain_rank_overview-live/)
-   [Search Console Search Analytics API guidance](https://developers.google.com/webmaster-tools/v1/how-tos/search_analytics)