Skip to main content
inspect_index_status Inspect one monitored source URL through its authorized Google property. This reads Google indexed state, not the live page, and requests no crawl. Retry with the same request key.
Name recorded in the 2026-10-27 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
This operation changes saved state. Review its inputs and retry behavior before calling.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Schema-validated example; IDs and dates are illustrative. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

Requires operator activation and the caller’s current project grant. Source URL indexing remains independent from backlink presence. The selected Google connection must cover the monitored source URL. A successful inspection reads Google’s indexed version; it does not test a live page or request a crawl. Every admitted attempt consumes a quota slot, including failed or interrupted attempts. Identical completed retries reuse the receipt; unsettled attempts are not automatically repeated. Actual provider error bodies remain unknown evidence.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • observation (object, required).
  • rawResponse (any, required).
  • evidenceAvailable (boolean, required).
  • replayed (boolean, required): True when the response reuses an earlier request with the same idempotency value.
  • providerError (string / null, optional).
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

When retrying with idempotencyKey, reuse the original value and the same arguments; preserve originally omitted optional fields. Generic HTTP puts idempotencyKey in the JSON body, while resource routes use the header where listed below. A changed payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

This operation has no separate resource alias. Use its generic command route in a matching environment.

Continue

list_index_observations Follow the related workflow. See capability status for availability or the command index for another operation.