Opus Growth

SEO Site Crawl

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

النوع
قراءة فقط
الرصيد
1
المنصة
SEO Intelligence
الموافقة
غير مطلوبة، لا يتغير شيء

ماذا يفعل

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.

وصف الأداة بالإنجليزية لأنه النص الرسمي الذي يراه الذكاء الاصطناعي.

MCP: seo_site_crawl

كيفية الاستخدام

لا تستدعي الأدوات بأسمائها. اكتب ما تريد في ChatGPT أو Claude أو أي مساعد متصل بـ Opus Growth بكلماتك، وسيختار الذكاء الاصطناعي هذه الأداة عندما تناسب.

المعلمات

الاسمالنوعإلزاميالافتراضي
domainstringإلزامي·Domain name to analyse, monitor, or use, without an unrelated display label.
max_pagesintegerاختياري100Numeric max pages value for seo site crawl. Use the provider's expected unit, range, and precision.
task_idstringاختياري·Exact task identifier to target. Use the ID returned by an Opus Growth list or create operation, not a display name.
refreshbooleanاختياريfalseWhether to request fresh provider data instead of using an eligible cached result.
issuestringاختياري·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.
limitintegerاختياري50Maximum 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.
offsetintegerاختياري0Zero-based position at which to start reading results. Use the next_offset returned by the previous response when present.