--- title: "Google index monitor | SEO Skill" description: "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." canonical: "https://seoskill.dev/docs/reports/index-monitor" language: "en" --- # Google index monitor Collect Google index snapshots within the daily URL Inspection quota and save them locally. Deferred, failed and unselected pages remain visible instead of quietly looking healthy. ## Install and run the monitor Install the CLI once, then run `seo start` to connect your site and Google data. After setup you can run this monitor yourself or ask your agent to run it. Install the SEO CLI globally. ``` npm i -g seo ``` Run setup after installation. ``` seo start ``` Collect a limited set of URL Inspection snapshots. ``` seo index-watch --site sc-domain:example.com --sitemaps https://example.com/sitemap.xml ``` ## What the monitor records 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. Best for A repeatable sitemap-based monitoring process is already planned. Needs XML sitemap URLs You get 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. Use next Review Google index changes Every report follows the same rules for missing data and outside estimates.[See how report data works](https://seoskill.dev/docs/reports#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 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. ## Use a different report for these jobs These jobs need a different report or a manual review. [ ### You need to know which inspected URLs regressed or recovered since an earlier snapshot. Run index watch after snapshots exist. It compares compatible URL Inspection fields and separates regressions, recoveries, unchanged results, and provider failures. URL Inspection monitor ](https://seoskill.dev/docs/reports/index-watch)[ ### You need to diagnose the live technical state of one URL flagged by Google. 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. SEO page audit ](https://seoskill.dev/docs/reports/audit-page) ## Use the monitor 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 monitor 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 monitor with the validated parameters. Check the current input before the agent or script runs the monitor. ``` seo reports describe index-monitor --json ``` Once the input is valid, run the monitor through the report catalog. ``` 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 ``` ### MCP An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the monitor. Ask the MCP server for the current monitor input. ``` { "id": "index-monitor" } ``` Run the monitor after the agent has checked and filled the input. ``` { "id": "index-monitor", "params": { "site": "sc-domain:example.com", "sitemaps": [ "https://example.com/sitemap.xml" ], "dailyLimit": 200, "inspectLimit": 25, "maxUrls": 50000, "languageCode": "en-GB" } } ``` ### TypeScript Install the package in a Node 22 project when your application needs to run the monitor 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 monitor from your TypeScript application. ``` 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) ``` ## What to do next Inspect failed, deferred and quota-blocked URLs before reading the checked set as coverage. Save the completed snapshots, then use the watch report to compare those same pages later. 1. 01Run index watch against stored snapshots. 2. 02Inspect live technical evidence for URLs with supported problems. ## Related reports [ 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 ](https://seoskill.dev/docs/reports/index-watch)[ 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 ](https://seoskill.dev/docs/reports/audit-page)[ Plan a representative Google URL Inspection sample across sitemaps and page groups without spending the daily API quota or guessing which pages matter. URL Inspection plan ](https://seoskill.dev/docs/reports/index-plan) ## Sources used by this monitor These primary sources define the provider data or search controls used by the result. - [Search Console URL Inspection API reference](https://developers.google.com/webmaster-tools/v1/urlInspection.index/inspect) - [Google sitemap guidance](https://developers.google.com/search/docs/crawling-indexing/sitemaps/overview)