start_internal_link_scan
Start a bounded website scan that continues in the background. Reads the homepage and sitemaps, then follows eligible internal links. Reuse requestId after an uncertain response. No recurring monitoring or paid provider request.
This command name appears in deployment evidence dated 2026-10-16. This page describes current source; read your connected catalog for deployed inputs and access. Workspace scopes and enabled providers 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
Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data instructuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.
Full response example
Full response example
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
Saves an idempotent background intent for the selected website. Same requestId and website scope return the existing scan. Follows at most 300 eligible pages; the workspace allowance is 300 admitted pages per UTC day shared with supplied snapshots. Retries retain their original page admission. No recurring monitoring, paid supplier request or model assessment is created. Website coverage remains partial.Output fields
Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.scan(object, required): additional fields rejectedlimits(object, required): additional fields rejected
All fields and nested objects
All fields and nested objects
Errors and retries
Retry start_internal_link_scan with the original requestId in the same workspace and project. Inspect the returned scan before starting a new operation. Reusing that requestId after the website hostname changes returns IDEMPOTENCY_CONFLICT. Operation-specific errors includeINTERNAL_LINK_SCANS_UNAVAILABLE, INTERNAL_LINK_SCAN_EXPIRED, SCAN_CONTROL_CONFLICT, SCAN_FINISHED, SCAN_PAGE_LIMIT, INTERNAL_LINK_DAILY_LIMIT, INVALID_CURSOR.
See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.