Live SERP results report

See the current limited result page for one query and market. The snapshot keeps exact ranks separate from Search Console averages and does not turn repeated domains into a strength score.

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

Inspect one limited location and device-specific result snapshot.

seo reports run serp-results --params '{"keyword":"local seo software","countryCode":"US","languageCode":"en","device":"mobile"}' --json

What you get from this report

Inspect exact organic ranks, domains, URLs, titles, snippets and result features for one keyword, location, language and device-specific search snapshot.

Best for: A keyword needs a current intent and result-page review before a content decision.
Needs: Keyword and search market
You get: Inspect exact organic ranks, domains, URLs, titles, snippets and result features for one keyword, location, language and device-specific search snapshot.
Use next: Discover keyword candidates

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 and search market

Set one query, country, language, optional location, device, and a result depth of at most 100.

Connected result provider

Returns the observed result page, organic rows, result features, corrected query, coverage, and acquisition evidence.

Use a different report for these jobs

These jobs need a different report or a manual review.

You need independent demand estimates or related candidates rather than the current result page.

Run keyword research to build a limited shortlist, then inspect result snapshots only for the candidates that deserve an intent review.

Keyword research report

You need ranking history or a definitive explanation for why one page outranks another.

Use repeated, comparable snapshots for rank history and inspect the ranking pages directly. One snapshot cannot prove causation, domain strength, content quality, or future ranking feasibility.

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 serp-results --json

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

seo reports run serp-results --params '{"keyword":"local seo software","countryCode":"US","languageCode":"en","device":"mobile","depth":20}' --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": "serp-results"
}

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

{
  "id": "serp-results",
  "params": {
    "keyword": "local seo software",
    "countryCode": "US",
    "languageCode": "en",
    "device": "mobile",
    "depth": 20
  }
}

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(
  'serp-results',
  {
  "keyword": "local seo software",
  "countryCode": "US",
  "languageCode": "en",
  "device": "mobile",
  "depth": 20
},
)

console.log(result)

What to do next

Open representative ranking pages and confirm the query intent. Match market, device, query and observation time before comparing the exact snapshot with Search Console average position or a later check.

01Open representative ranking pages and confirm the dominant intent before choosing an existing or new target page.
02Match query, market, device, and date before comparing the snapshot with Search Console position data.

Discover market-specific keyword ideas from a small seed list with search volume, difficulty, source overlap, provider coverage, cache status and cost.

Keyword research 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.

Keyword metrics 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

Build a content brief from one page, its Search Console queries and the headings or topics already present. Keep every suggestion tied to demand.

Content optimization report

Sources used by this report

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

DataForSEO live Google SERP API reference