Content optimization report

Use one page and its returned Search Console queries to plan a focused update. The report shows missing or weak coverage without turning every related phrase into a heading.

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 brief from one page and its Search Console queries.

seo content optimize --url https://example.com/page --project example

What you get from this 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.

Best for: One page has Search Console visibility and needs a careful content or snippet review.
Needs: Exact-page Search Console queries
You get: Build a content brief from one page, its Search Console queries and the headings or topics already present. Keep every suggestion tied to demand.
Use next: Audit one page

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.

Exact-page Search Console queries

Provides the returned demand, clicks, impressions, CTR, and position associated with the URL.

Live page content and technical evidence

Provides current metadata, headings, text, links, canonical, and indexability observations.

Use a different report for these jobs

These jobs need a different report or a manual review.

You only need a technical check of one live URL before changing its metadata, canonical, directives, links, or schema.

Run the page audit. It focuses on observed live-page evidence and does not build a content brief from query demand.

SEO page audit

You need to decide whether to rewrite the current page, create a new page, merge it with another page, or leave it alone.

No automated report can make that editorial and information-architecture decision. Review search intent, the live SERP, conversions, backlinks, business goals, and overlapping pages. This report can still provide the page evidence and returned queries used in that decision.

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 content-optimization --json

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

seo reports run content-optimization --params '{"site":"sc-domain:example.com","url":"https://example.com/guides/seo","days":90,"limit":20,"minImpressions":50,"verifyContent":true}' --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": "content-optimization"
}

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

{
  "id": "content-optimization",
  "params": {
    "site": "sc-domain:example.com",
    "url": "https://example.com/guides/seo",
    "days": 90,
    "limit": 20,
    "minImpressions": 50,
    "verifyContent": true
  }
}

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(
  'content-optimization',
  {
  "site": "sc-domain:example.com",
  "url": "https://example.com/guides/seo",
  "days": 90,
  "limit": 20,
  "minImpressions": 50,
  "verifyContent": true
},
)

console.log(result)

What to do next

Choose the gaps supported by returned queries and the page's existing purpose. Update the page around a focused intent, then measure the same query and page set after enough Search Console data has arrived.

01Make one clear, user-serving change and record it.
02Measure the result after a complete comparison window.

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

Compare one URL with its Search Console queries and live page evidence to find focused content, CTR and coverage opportunities before rewriting the page.

Page SEO opportunities

Compare matched Search Console periods around a recorded SEO change and keep releases, demand shifts and other confounders beside the result.

SEO change measurement

Sources used by this report

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