Keyword metrics report

Check a limited keyword set against independent market estimates before committing to deeper research. The report keeps missing data, request cost and provider coverage visible, so a neat number never looks more certain than it is.

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

Compare a limited keyword set in one country and language.

seo reports run keyword-metrics --params '{"keywords":["seo audit tool"],"countryCode":"US","languageCode":"en"}' --json

What you get from this report

Compare search volume, trends, CPC, competition, difficulty, intent and result counts for a list of keywords in one country and language before deeper research.

Best for: You already have a keyword list and need estimates for a specific country and language.
Needs: Keyword list and search market
You get: Compare search volume, trends, CPC, competition, difficulty, intent and result counts for a list of keywords in one country and language before deeper research.
Use next: Group related search queries

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.

Keyword list and search market

Sets at most 50 terms, one country, one language, and an optional location or device context.

Connected keyword provider

Returns market-level volume, monthly history, CPC, competition, difficulty, intent, and result-count estimates where available.

Use a different report for these jobs

These jobs need a different report or a manual review.

You need evidence of searches already associated with your own pages.

Run query clusters for the Search Console property. It groups returned Search Console queries instead of estimating wider market demand.

Search query clustering report

You need to know who ranks now or whether the result page matches the intended topic.

Inspect a current result page in the same country, language, location, and device. Keyword metrics alone cannot identify current competitors or prove intent fit.

Needs more evidence

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 keyword-metrics --json

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

seo reports run keyword-metrics --params '{"keywords":["seo audit tool","technical seo audit"],"countryCode":"US","languageCode":"en"}' --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": "keyword-metrics"
}

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

{
  "id": "keyword-metrics",
  "params": {
    "keywords": [
      "seo audit tool",
      "technical seo audit"
    ],
    "countryCode": "US",
    "languageCode": "en"
  }
}

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(
  'keyword-metrics',
  {
  "keywords": [
    "seo audit tool",
    "technical seo audit"
  ],
  "countryCode": "US",
  "languageCode": "en"
},
)

console.log(result)

What to do next

Start with terms that combine useful estimated demand with a clear fit for the site. Compare them with Search Console data and inspect the current results before creating a page, expanding a template or promising an outcome.

01Compare the most promising terms with Search Console impressions, clicks, pages, and average position.
02Inspect a current result page in the same market before choosing a content or programmatic template target.

Group returned Search Console queries into repeated demand themes so content gaps, templates and competing pages are easier to inspect across the site.

Search query clustering report

Find page-one queries with useful impressions and weaker CTR evidence, then inspect the search result before changing titles, snippets or page copy.

SEO quick wins report

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

Striking distance SEO report

Sources used by this report

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

DataForSEO keyword overview API reference