SEO Skill

Collect Google index snapshots within your daily quota

Use Google index monitoring to build or refresh local URL Inspection history. The report selects due sitemap URLs within your daily limit and records every inspected, deferred, blocked, or failed request.

Run this report from the CLI, an MCP client, or application code. Every surface uses the same report definition and returns the same evidence. JSON is the source of truth; Markdown makes it readable without hiding dates, limits, warnings, or skipped work.

What this report helps you decide

What indexed-state evidence did Google return for today’s monitored URL sample?

  • A repeatable sitemap-based monitoring process is already planned.
  • Local quota limits and property access are configured.

Command facts

Report id
index-monitor
Execution
Local process
Outputs
JSON and Markdown
Example parameters
site, sitemaps, dailyLimit, inspectLimit, maxUrls, languageCode
Agent discovery
seo reports describe index-monitor --json
Interactive prompts
Human CLI commands only

When this report is not the right tool

These cases need a different report, more evidence, or a human decision. Do not force this report to answer a question its data cannot support.

  • You need to know which inspected URLs regressed or recovered since an earlier snapshot. Recommended report: Review Google index changes. Run index watch after snapshots exist. It compares compatible URL Inspection fields and separates regressions, recoveries, unchanged results, and provider failures.
  • You need to diagnose the live technical state of one URL flagged by Google. Recommended report: Audit one page. Audit the live page to add current response, redirect, canonical, robots, metadata, link, and schema evidence. URL Inspection describes Google’s indexed version and can lag the deployed page.

Data sources and inputs

  • XML sitemap URLs. Provide the limited inventory from which due URLs are selected.
  • Search Console properties and URL Inspection quota. Provide exact Google index verdicts and the daily capacity available for each property.
  • Previous local index snapshots. Determine which URLs are due and preserve history for later change analysis.

What this report checks

  • Builds the sitemap inventory, maps URLs to properties, enforces local daily limits, and selects a limited due sample.
  • Stores successful Google inspection snapshots and keeps quota blocks, deferred URLs, provider failures, and unselected due URLs separate.

How it works

  • Selects a limited repeatable sample, enforces local daily capacity, stores individual results, and records operational failures separately.

The JSON result keeps dates, thresholds, limits, skipped work, and source completeness beside the finding. Missing, partial, capped, filtered, and complete data remain different states.

Run the report from the CLI

Collect a limited set of URL Inspection snapshots. Agents and CI should inspect the live schema before their first run.

Run it from the CLI

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

Check the agent input schema

seo reports describe index-monitor --json

Run it from an agent or script

seo reports run index-monitor --params '{"site":"sc-domain:example.com","sitemaps":["https://example.com/sitemap.xml"],"dailyLimit":200,"inspectLimit":25,"maxUrls":50000,"languageCode":"en-GB"}' --json

Project profiles can fill supported property and analytics inputs for the human-facing commands. The catalog form shown here is explicit by design, so agents and CI jobs do not prompt or guess.

How an MCP agent should use it

Call seo_describe_report first so the agent sees when this report is useful and gets the current input schema. Then callseo_run_report with the validated parameters. Read the status, warnings, source limits, and skipped sections before acting on a finding.

Describe the report with MCP

{
  "id": "index-monitor"
}

Run the report with MCP

{
  "id": "index-monitor",
  "params": {
    "site": "sc-domain:example.com",
    "sitemaps": [
      "https://example.com/sitemap.xml"
    ],
    "dailyLimit": 200,
    "inspectLimit": 25,
    "maxUrls": 50000,
    "languageCode": "en-GB"
  }
}

Use a follow-up report returned by the result instead of guessing the next tool. The local MCP server and CLI use the same report definition and evidence. Their outer transport envelopes differ.

Use the report in a TypeScript app

Install seo as a project dependency, then call the same report catalog used by the CLI and MCP. executeReportrejects an unknown report id or invalid parameters. Provider and runtime failures come back as structured results withisError set.

Install the library

npm install seo

Run this report from TypeScript

import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'index-monitor',
  {
  "site": "sc-domain:example.com",
  "sitemaps": [
    "https://example.com/sitemap.xml"
  ],
  "dailyLimit": 200,
  "inspectLimit": 25,
  "maxUrls": 50000,
  "languageCode": "en-GB"
},
)

console.log(result)

The TypeScript library guide also covers direct core functions, schema discovery, and the difference betweenexecuteReport and runReport.

What comes back and how to read it

  • Inventory, due, selected, inspected, deferred, failed, quota-blocked, and unselected counts with exact selection source details.
  • Current Google indexed-state snapshots, operational review rows, warnings, and a projected monitoring cycle.
  • Read exact verdict fields and inspection time. Unknown, excluded, invalid, failed, and uninspected URLs are different states.

Start with dataStatus, source details, warnings, and caveats. Then inspect the observed evidence before derived findings or suggested actions.

What this report cannot tell you

  • URL Inspection reports Google’s indexed version, not a live fetch, and provider quota limits coverage.

What to do next

  1. Run index watch against stored snapshots.
  2. Inspect live technical evidence for URLs with supported problems.
  • Review Google index changes. Inspect a limited URL set and separate current index issues, regressions, recoveries, and operational failures.
  • Audit one page. Inspect one live URL before changing its metadata, canonical, directives, structured data, links, or content.
  • Plan Google index monitoring. Turn sitemap URLs, Search Console properties, and daily URL Inspection limits into a realistic monitoring cycle.

Sources behind the guidance

These primary sources define the provider data or search controls used in the interpretation above.

Browse all reports in Technical monitoring.