URL Inspection plan

Choose which URLs to inspect before making any API calls. The plan spreads a limited quota across useful page groups instead of burning it on the first URLs in a sitemap.

Install and run the tool

Install the CLI once, then run seo start to connect your site and Google data. After setup you can run this tool 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

Plan an inspection cycle without spending URL Inspection quota.

seo index-watch --site sc-domain:example.com --sitemaps https://example.com/sitemap.xml --plan

What the tool gives you

Plan a representative Google URL Inspection sample across sitemaps and page groups without spending the daily API quota or guessing which pages matter.

Best for: A large site needs limited, repeatable index monitoring.
Needs: XML sitemap inventories
You get: Plan a representative Google URL Inspection sample across sitemaps and page groups without spending the daily API quota or guessing which pages matter.
Use next: Collect Google index snapshots

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.

XML sitemap inventories

Provide the limited URL population that needs an inspection plan.

Available Search Console properties and quota

Define ownership coverage, daily capacity, and the target monitoring cycle.

Use a different report for these jobs

These jobs need a different report or a manual review.

You need to collect Google index verdicts now rather than plan future coverage.

Run index monitor after checking the proposed sample and quota. It spends the configured URL Inspection capacity, stores exact provider results locally, and keeps deferred and failed requests separate.

Google index monitor

You need to decide whether every sitemap URL deserves indexing.

No automated report can infer page intent or business value from a sitemap. Review the intended page types and canonical strategy with the people who own the site, then use this plan to create a representative inspection cycle.

Needs more evidence

Use the tool 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 tool 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 tool with the validated parameters.

Check the current input before the agent or script runs the tool.

seo reports describe index-coverage-plan --json

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

seo reports run index-coverage-plan --params '{"site":"sc-domain:example.com","sitemaps":["https://example.com/sitemap.xml"],"dailyLimit":200,"targetCycleDays":7,"maxUrls":50000}' --json

An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the tool.

Ask the MCP server for the current tool input.

{
  "id": "index-coverage-plan"
}

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

{
  "id": "index-coverage-plan",
  "params": {
    "site": "sc-domain:example.com",
    "sitemaps": [
      "https://example.com/sitemap.xml"
    ],
    "dailyLimit": 200,
    "targetCycleDays": 7,
    "maxUrls": 50000
  }
}

Install the package in a Node 22 project when your application needs to run the tool 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 tool from your TypeScript application.

import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'index-coverage-plan',
  {
  "site": "sc-domain:example.com",
  "sitemaps": [
    "https://example.com/sitemap.xml"
  ],
  "dailyLimit": 200,
  "targetCycleDays": 7,
  "maxUrls": 50000
},
)

console.log(result)

What to do next

Review the proposed sample before spending URL Inspection quota. Run the index monitor with the accepted URLs and keep deferred pages visible for a later cycle.

01Run index monitor with a limited daily sample.
02Add appropriate URL-prefix property access if important URLs cannot be inspected.

Collect a limited set of Google URL Inspection snapshots, save them locally and keep deferred or failed pages separate from checked URLs in the report.

Google index monitor

Compare current Google URL Inspection results with saved snapshots to find selected pages whose index status or canonical changed since the last check.

URL Inspection monitor

Sources used by this tool

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