Keyword opportunity report

Build one limited research queue from searches already associated with the site. Add independent market estimates only when they would change the next investigation, since outside research can cost money.

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

Build a Search Console opportunity list without making a paid provider request.

seo reports run keyword-opportunities --params '{"site":"sc-domain:example.com","days":90}' --json

What you get from this report

Combine Search Console quick wins, second-page queries and striking-distance evidence with optional keyword estimates and programmatic SEO clusters.

Best for: You want one limited review queue across quick wins, second-page queries, and striking-distance evidence.
Needs: Search Console property and date range
You get: Combine Search Console quick wins, second-page queries and striking-distance evidence with optional keyword estimates and programmatic SEO clusters.
Use next: Compare keyword metrics

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.

Search Console property and date range

Returns returned query and page rows for the selected property and finalised date window.

Opportunity and output limits

Bound quick-win, second-page, striking-distance, keyword, URL, cluster, and structured output sizes.

Optional external market

Adds provider estimates only when includeExternal is true and a country and language are supplied. This can make a paid request.

Use a different report for these jobs

These jobs need a different report or a manual review.

You already have a keyword list and only need independent market estimates.

Run keyword metrics with the exact terms, country, language, location, and device you need. It skips Search Console opportunity selection and reports provider evidence directly.

Keyword metrics report

A repeated URL pattern needs representative page and template evidence.

Run the programmatic SEO audit for the chosen scope. It reviews template population, samples, crawl findings, Search Console evidence, and optional inspection verdicts before you change the generator.

Programmatic SEO audit

You need exact rankings, current competitors, or result-page intent.

Collect a current result snapshot for the same query, country, language, location, and device. This report contains average Search Console position and optional market estimates, not a live result page.

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-opportunities --json

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

seo reports run keyword-opportunities --params '{"site":"sc-domain:example.com","days":90,"limit":10,"keywordLimit":30,"includeExternal":false}' --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-opportunities"
}

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

{
  "id": "keyword-opportunities",
  "params": {
    "site": "sc-domain:example.com",
    "days": 90,
    "limit": 10,
    "keywordLimit": 30,
    "includeExternal": false
  }
}

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-opportunities',
  {
  "site": "sc-domain:example.com",
  "days": 90,
  "limit": 10,
  "keywordLimit": 30,
  "includeExternal": false
},
)

console.log(result)

What to do next

Start with the Search Console evidence and the report section that supplied each candidate. Use provider estimates as added context, inspect the current results, and audit representative pages before creating content or expanding a template.

01Audit the strongest existing page and inspect a current result snapshot for its query and market.
02Run the programmatic SEO audit for a repeated template cluster before expanding it.

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

Keyword metrics report

Audit programmatic SEO templates, repeated URL patterns and Search Console demand. Review representative pages before changing a whole template.

Programmatic SEO audit

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

Audit one URL for technical SEO, metadata, canonicals, schema, links and Search Console queries. See the live evidence before changing the page.

SEO page audit

Sources used by this report

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