Rankings across the workspace's accounts
seo_rankings.cross_account.get
From a workspace, returns one row per rank tracking project of every Account the caller reaches (members and viewers: the Accounts assigned to them; a key: its account scope): account and project, domain, active keyword count, last check, how many keywords rank in each band on the project's main engine, country and device (top3 = 1–3, top10 = 4–10, top20 = 11–20, top30 = 21–30, not_ranking = no position in the top 30: the same bands as check_summary.distribution of seo_rankings.projects.get), the average position of the keywords in the top 30, how many improved, declined or stayed since the previous check (always within that same combination), and whether the schedule is on. Each row names that main combination (pos_key, engine, country_code, device) and brings combos: the same figures for every combination the project measures today (primary marks the main one). Plus a summary (projects, keywords, share in the top 10 of each project's keywords on its main combination, projects checked in the last 7 days). Only works on a workspace (400 workspace_only on an Account). For one account's detail use seo_rankings.projects.list on that Account.
- Scope
seo_rankings:read- Permission
- View the module
- MCP tool
seo_rankings_cross_account_getOn the full surface; on the compact one,mb_execute_operationwithid: "seo_rankings.cross_account.get".
Declared cost: up to 30000 reads and 0 writes per call (they count against the daily quota).
Parameters
No parameters.
Response
rowsarray<object>One row per rank project of each account the caller reaches.
summaryobjectThe KPI strip of the cross-account view.
Errors
Example
curl "https://api.mb-suite.com/v1/seo/rankings/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/rankings/cross-account" \
-H "Authorization: Bearer $MB_TEST_KEY"