Skip to main content
An active hosted watch schedules checks of a supplied placement. Start with check a placement, or explicitly enroll a verified candidate. Local CLI checks run only when invoked.

​
Review the latest evidence

Call list_link_watches for a compact list. Open get_link_watch for the selected record and get_history with subject: "link" and subjectId set to its watch identifier for observations. A recent attempt can be unknown while an older complete observation remains the last known state. Keep both dates in your report. Use list_events with "feed": "links" to consume changes. Apply a complete page to your local records before storing next_cursor. Use event identifiers to avoid duplicate effects during replay. Destination health has its own watches, history and event feed ("feed": "targets"). Maintain its cursor separately. An unavailable destination does not establish loss of the backlink that cites it. Google index results for linking pages in your own Search Console property have their own history and events. Google index status explains how to turn them on and read them. Read growth history and saved profile comparisons to review retained changes across a period. To inspect connections between pages on your own website, use Internal links to scan the website or check a supplied page list.

​
Control recurring work

Use update_link_watch to pause a placement or change its expectations and cadence. Pausing scheduled monitoring preserves history, classifications, saved choices and tags. It does not describe classification status. Read link types and assessment states independently of monitoring status. Cadence is a requested interval; workspace limits and scheduling affect when work runs. Read get_usage to distinguish reserved work from consumed and released check units. Source and destination checks share allowance. Request an extra check only when the task needs new evidence. Reuse the request’s idempotency value after a transport failure. A delayed job needs inspection, not repeated new submissions.

​
Recover a missed interval

For CURSOR_EXPIRED, follow the returned recovery instructions for that feed. Save the complete snapshot before resuming; it recovers current state, while expired transitions remain a history gap. Keep each feed’s cursor separate. The sync recovery details explain source exports, target snapshots and missing adapters. Email alerts and digests tell you about changes; hosted webhook delivery isn’t available yet. Read evidence semantics before reporting confirmed loss, and use troubleshooting for pending checks.