Google index coverage audit

Compare what your site exposes with what Search Console returns before spending URL Inspection quota. The audit points to representative pages that deserve a direct Google check.

Install and run the audit

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

Choose representative pages for URL Inspection from crawl, sitemap, and Search Console evidence.

seo index-coverage --project example

What you get from this audit

Compare crawl, sitemap and Search Console evidence to find page groups that need a closer Google URL Inspection check before spending limited quota.

Best for: You need an evidence-based sample for an index coverage investigation.
Needs: Saved crawl report
You get: Compare crawl, sitemap and Search Console evidence to find page groups that need a closer Google URL Inspection check before spending limited quota.
Use next: Review Google index changes

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.

Saved crawl report

Provides the pages fetched locally, their current crawl controls, and explicit crawl scope and completeness.

XML sitemap inventory when available

Adds pages the site submitted for discovery. A saved crawl can provide declared sitemap document URLs, but it does not contain a complete sitemap inventory by itself.

Finalized Search Console page rows

Shows which pages appeared with Google Search impressions in the chosen date range, up to the explicit row limit.

Use a different report for these jobs

These jobs need a different report or a manual review.

You need Google’s current indexed verdict for a specific URL.

Run index watch for a limited URL set. It adds direct URL Inspection verdicts and saved-history comparisons instead of inferring index state from crawl, sitemap, or Search Analytics data.

URL Inspection monitor

You need a definitive count of every indexed URL on a large site.

No automated report can produce that count from Search Analytics or a quota-limited URL Inspection sample. Use this report to select representative URLs, inspect them directly, and review Search Console indexing reports alongside the site’s intended URL inventory.

Needs more evidence

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

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

seo reports describe index-coverage --json

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

seo reports run index-coverage --params '{"site":"sc-domain:example.com","crawlReportId":"crawl_saved","sitemaps":["https://example.com/sitemap.xml"],"days":90,"rowLimit":100000}' --json

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

Ask the MCP server for the current audit input.

{
  "id": "index-coverage"
}

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

{
  "id": "index-coverage",
  "params": {
    "site": "sc-domain:example.com",
    "crawlReportId": "crawl_saved",
    "sitemaps": [
      "https://example.com/sitemap.xml"
    ],
    "days": 90,
    "rowLimit": 100000
  }
}

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

import { executeReport } from 'seo/mcp'

const result = await executeReport(
  'index-coverage',
  {
  "site": "sc-domain:example.com",
  "crawlReportId": "crawl_saved",
  "sitemaps": [
    "https://example.com/sitemap.xml"
  ],
  "days": 90,
  "rowLimit": 100000
},
)

console.log(result)

What to do next

Use the grouped evidence to choose representative URLs for Google URL Inspection. Spend the limited quota on pages that can confirm or challenge the crawl and sitemap pattern.

01Choose representative URLs from important page types and template groups.
02Run URL Inspection for that limited sample and keep provider failures separate from page findings.

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

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

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

Sources used by this audit

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