Cross-account

Site audit health across the workspace's accounts

seo_site_auditor.cross_account.list

Lists, from the workspace, the audited site of each account the caller reaches (an owner or admin: every account; a member or viewer: the assigned ones; an API key: only the accounts in its scope) with its latest finished audit: health_score and previous_health_score (read them with pages_crawled, pages_failed and low_coverage: a score over very few pages says little), issues_by_severity, category_scores, geo_readiness_score, last_audit_at, the Core Web Vitals of the mobile PageSpeed result (cwv: lcp and inp in ms, cls unitless, rounded), the schedule state (schedule_enabled, disabled_by_system, consecutive_failures, last_failed_at), recipients_count and crawl_method. summary has avg_health_score, critical_and_high_issues, total_sites, recently_audited (last 7 days) and avg_geo_score (the averages are null when no site has a score). Archived accounts are left out. One row per audited site, paginated (limit, default 20, up to 40: each row is about a thousand characters; follow next_cursor); summary always covers every site. Fails with workspace_only (400) when called on an account. Requires view access to Site Audit.

Scope

seo_site_auditor:read

Permission

View the module

MCP tool

seo_site_auditor_cross_account_listOn the full surface; on the compact one, mb_execute_operation with id: "seo_site_auditor.cross_account.list".

Declared cost: up to 320 reads and 0 writes per call (they count against the daily quota).

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/seo/site-auditor/cross-account" \
  -H "Authorization: Bearer $MB_API_KEY"

Try it with your test API key

With a test API key the request always goes to your practice organization: example data you can reset.

curl "https://api.mb-suite.com/v1/seo/site-auditor/cross-account" \
  -H "Authorization: Bearer $MB_TEST_KEY"