Opus Growth

SEO Site Crawl

Site-WIDE technical crawl (SEO Intelligence add-on, ASYNC — not a single page).

Tipo
Solo lectura
Créditos
1
Plataforma
SEO Intelligence
Aprobación
No hace falta, nada cambia

Qué hace

Site-WIDE technical crawl (SEO Intelligence add-on, ASYNC — not a single page). A call WITHOUT task_id STARTS the crawl and returns a task_id; a call with that task_id after ~30-90s returns the summary: pages crawled, average on-page score, and issue counts (broken pages / duplicate titles / thin content / missing H1, etc.) with the first 5 URLs of each issue, plus which pages link to each broken URL (`broken_link_sources`). The FULL URL list of one issue comes from a call with the same task_id and `issue` = the issue name from the summary (no_h1_tag and so on); paged with limit/offset. It audits a whole site, not just one URL. Costs SEO add-on credits on the START call; every task_id fetch is free. Top up in the panel → Add-ons.

La descripción está en inglés porque es el texto oficial que ve tu IA.

MCP: seo_site_crawl

Cómo usarla

No llamas a las herramientas por su nombre. Escribe lo que quieres en ChatGPT, Claude u otro asistente conectado a Opus Growth; la IA elige esta herramienta cuando encaja.

Parámetros

NombreTipoObligatorioPor defecto
domainstringObligatorio·Domain name to analyse, monitor, or use, without an unrelated display label.
max_pagesintegerOpcional100Numeric max pages value for seo site crawl. Use the provider's expected unit, range, and precision.
task_idstringOpcional·Exact task identifier to target. Use the ID returned by an Opus Growth list or create operation, not a display name.
refreshbooleanOpcionalfalseWhether to request fresh provider data instead of using an eligible cached result.
issuestringOpcional·Exact issue value for seo site crawl. Supply text in the provider's required format; when it selects an existing resource, use the exact identifier returned by the relevant list or search operation.
limitintegerOpcional50Maximum number of rows returned in this response. When the result has_more flag is true, continue with next_page_token rather than assuming the list is complete.
offsetintegerOpcional0Zero-based position at which to start reading results. Use the next_offset returned by the previous response when present.