Keyword research report
Expand a small seed list without turning the result into an automatic content plan. Every idea keeps its provider source, metric state, market, coverage and request cost visible.
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 seoRun setup after installation.
seo startDiscover a limited market-specific keyword shortlist.
seo reports run keyword-research --params '{"seeds":["local seo software"],"countryCode":"US","languageCode":"en"}' --jsonWhat you get from this report
Discover market-specific keyword ideas from a small seed list with search volume, difficulty, source overlap, provider coverage, cache status and cost.
- Best for
- You need candidate terms beyond the queries already visible in Search Console.
- Needs
- Seed keywords and discovery methods
- You get
- Discover market-specific keyword ideas from a small seed list with search volume, difficulty, source overlap, provider coverage, cache status and cost.
- Use next
- Inspect live search results
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.
Seed keywords and discovery methods
Set at most five seeds and choose ideas, related terms, suggestions, or a limited combination.
Connected keyword provider
Returns candidate terms and available market estimates for the selected country, language, and optional location.
Use a different report for these jobs
These jobs need a different report or a manual review.
You need queries already associated with the site rather than independent market candidates.
Run query clusters for the Search Console property. It groups returned Search Console queries and does not make a paid discovery request.
You need to decide whether several terms deserve one page, separate pages, or no new page.
Inspect current result snapshots for a short list in the same market, then compare representative ranking pages and existing site evidence. Discovery overlap and estimated metrics cannot establish shared intent or page fit.
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 keyword-research --jsonOnce the input is valid, run the report through the report catalog.
seo reports run keyword-research --params '{"seeds":["local seo software","local search tools"],"sources":["ideas","suggestions"],"countryCode":"US","languageCode":"en","limit":40}' --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": "keyword-research"
}Run the report after the agent has checked and filled the input.
{
"id": "keyword-research",
"params": {
"seeds": [
"local seo software",
"local search tools"
],
"sources": [
"ideas",
"suggestions"
],
"countryCode": "US",
"languageCode": "en",
"limit": 40
}
}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(
'keyword-research',
{
"seeds": [
"local seo software",
"local search tools"
],
"sources": [
"ideas",
"suggestions"
],
"countryCode": "US",
"languageCode": "en",
"limit": 40
},
)
console.log(result)What to do next
Review source overlap and metric states, then inspect the current results for a short list. Compare relevant terms with Search Console data and validate representative templates before adding pages at scale.
- 01Inspect a current result snapshot for a short list in the same market.
- 02Compare relevant candidates with Search Console evidence and validate representative programmatic templates before scaling.
Related reports
Inspect exact organic ranks, domains, URLs, titles, snippets and result features for one keyword, location, language and device-specific search snapshot.
Compare search volume, trends, CPC, competition, difficulty, intent and result counts for a list of keywords in one country and language before deeper research.
Group returned Search Console queries into repeated demand themes so content gaps, templates and competing pages are easier to inspect across the site.
Audit programmatic SEO templates, repeated URL patterns and Search Console demand. Review representative pages before changing a whole template.
Sources used by this report
These primary sources define the provider data or search controls used by the result.