Sitemaps

List the sitemaps of a Search Console property

seo_indexation.sitemaps.list

Lists the sitemaps submitted to a Search Console property connected to the organization (site_url from seo_indexation.properties.list), live from Google: for each one its path (the sitemap URL), last_submitted and last_downloaded (ISO dates), is_pending (Google has not processed it yet), warnings, errors and contents (type, submitted URLs; indexed is deprecated by Google and usually 0). Not paginated. Errors: 404 external_account_not_linked (that site_url is not connected to this organization; Google is not called), 409 integration_not_connected (no Search Console connection: connect it in Integrations), 409 integration_reconnect_required (details.reason: expired, the connection expired or was revoked; missing_permission, it lacks a permission; access_lost, the connected Google account lost access to the property), 429 external_rate_limited, 503 external_unavailable. Spends Google quota. Requires view access to Indexation.

Scope

seo_indexation:read

Permission

View the module

MCP tool

seo_indexation_sitemaps_listOn the full surface; on the compact one, mb_execute_operation with id: "seo_indexation.sitemaps.list".

Declared cost: up to 2 reads and 0 writes per call (they count against the daily quota). Touches an external platform (google): it counts against the external operations quota.

Parameters

Response

Errors

Example

curl "https://api.mb-suite.com/v1/seo/indexation/sitemaps?site_url=SITE_URL" \
  -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. In the practice organization this operation is not simulated (it reaches another platform): it answers 409 sandbox_external_unavailable.

Submit a sitemap to a Search Console property

seo_indexation.sitemaps.submit

Submits (or resubmits) a sitemap to a Search Console property connected to the organization: site_url from seo_indexation.properties.list and feedpath, the full http(s) URL of the sitemap file (e.g. https://www.example.com/sitemap.xml). Google fetches and processes it afterwards; its status shows later in seo_indexation.sitemaps.list (is_pending, errors, warnings). Submitting one that is already there asks Google to read it again. Changes the property in Google Search Console, not in MB Suite. Errors: 404 external_account_not_linked (Google is not called), 409 external_rejected (Google rejected the sitemap: it must be reachable, be valid XML and live inside the property), 409 integration_not_connected, 409 integration_reconnect_required, 429 external_rate_limited, 503 external_unavailable. Spends Google quota. Requires edit access to Indexation.

Needs confirmation: first dry_run: true (preview and confirm_token, valid 10 minutes and for one run), then the same body with confirm_token. In a few operations only with certain data: the description says when. Why and how: Dry run and confirm_token.

Scope

seo_indexation:write

Permission

Edit in the module

MCP tool

seo_indexation_sitemaps_submitOn the full surface; on the compact one, mb_execute_operation with id: "seo_indexation.sitemaps.submit".

Events it can emit

seo_indexation.sitemap.submitted

Declared cost: up to 2 reads and 0 writes per call (they count against the daily quota). Touches an external platform (google): it counts against the external operations quota.

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/seo/indexation/sitemaps" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "site_url": "SITE_URL",
  "feedpath": "FEEDPATH",
  "dry_run": true
}'

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. In the practice organization this operation is not simulated (it reaches another platform): it answers 409 sandbox_external_unavailable.

Remove a sitemap from a Search Console property

seo_indexation.sitemaps.delete

Removes a submitted sitemap from a Search Console property connected to the organization: site_url and feedpath (the sitemap's path in seo_indexation.sitemaps.list; over REST both go in the JSON body of the DELETE, since they are URLs). Google stops reading that sitemap; the file on the site is untouched and it can be submitted again with seo_indexation.sitemaps.submit. Nothing goes to MB Suite's trash (the sitemap lives in Google). Outside the screen it always requires a dry run first (dry_run: true reads the property's sitemaps and describes the one to remove, 404 sitemap_not_found if it is not submitted) and then the same body with its confirm_token. Errors: 404 external_account_not_linked, 404 sitemap_not_found, 409 external_rejected, 409 integration_not_connected, 409 integration_reconnect_required, 429 external_rate_limited, 503 external_unavailable. Spends Google quota. Requires edit access to Indexation and, for a credential, deletion enabled.

Needs confirmation: first dry_run: true (preview and confirm_token, valid 10 minutes and for one run), then the same body with confirm_token. In a few operations only with certain data: the description says when. Why and how: Dry run and confirm_token.

Scope

seo_indexation:write and “Allow deletions” (seo_indexation:delete in OAuth)

Permission

Edit in the module

MCP tool

seo_indexation_sitemaps_deleteOn the full surface; on the compact one, mb_execute_operation with id: "seo_indexation.sitemaps.delete".

Events it can emit

seo_indexation.sitemap.deleted

Declared cost: up to 2 reads and 0 writes per call (they count against the daily quota). Touches an external platform (google): it counts against the external operations quota.

Parameters

Response

Errors

Example

curl -X DELETE "https://api.mb-suite.com/v1/seo/indexation/sitemaps" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "site_url": "SITE_URL",
  "feedpath": "FEEDPATH",
  "dry_run": true
}'

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. In the practice organization this operation is not simulated (it reaches another platform): it answers 409 sandbox_external_unavailable.