Sites

List the audited sites

seo_site_auditor.sites.list

Lists the websites this organization audits, oldest first (the first one is the site the app shows by default; an account normally has exactly one), paginated by cursor (limit up to 200). Each site carries its configuration (url, name, max_pages, schedule, notify_emails, exclude_patterns, exclude_mode, ignore_rules) and its state: next_due_at (the day, 00:00 UTC, the audit queue picks it up; null when manual, off or paused by the system), last_run_id / last_run_at / last_health_score (the latest finished audit), cloudflare_detected, and the failure count (consecutive_failures, last_failure_reason, disabled_by_system: the system pauses the schedule after 5 failures in a row). Requires view access to Site Audit.

Scope

seo_site_auditor:read

Permission

View the module

MCP tool

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

Declared cost: up to 201 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/sites" \
  -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/sites" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Get one audited site

seo_site_auditor.sites.get

Returns one audited site with its configuration (url, name, max_pages, schedule, notify_emails, exclude_patterns, exclude_mode, ignore_rules with the reason of each) and its state (next_due_at, last_run_id, last_run_at, last_health_score with last_run_coverage, the pages the latest audit could read: a score over very few pages says little, low_coverage, cloudflare_detected, consecutive_failures, last_failure_reason, disabled_by_system). Read its audits with seo_site_auditor.runs.list (site_id). Not found (audit_site_not_found) if the site does not exist in this organization. Requires view access to Site Audit.

Scope

seo_site_auditor:read

Permission

View the module

MCP tool

seo_site_auditor_sites_getOn the full surface; on the compact one, mb_execute_operation with id: "seo_site_auditor.sites.get".

Declared cost: up to 1 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/sites/{site_id}" \
  -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/sites/{site_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Add the site to audit

seo_site_auditor.sites.create

Adds the website this organization audits: url (https; a bare domain gets https://), and optionally name (default: the domain), max_pages (1–500, default 100), schedule (default, as in the app: weekly on Mondays and active, so the site enters MB Suite's audit queue at once and is crawled from Cloud Run every week; next_due_at in the answer says the day; send frequency manual to audit only on demand), notify_emails (up to 10 addresses that get the results by email after every audit), exclude_patterns and exclude_mode. It does NOT audit right away: the first audit runs on the next scheduled day, or start one with seo_site_auditor.runs.trigger. After answering, MB Suite checks once in the background whether the site is behind Cloudflare (one HTTP request to the site; cloudflare_detected). Each account audits one site: if the organization already has one it fails with audit_site_exists (409, with its site_id): change it with seo_site_auditor.sites.update. Fails with invalid_site_url (400) when the address is not a valid https domain or points inside a private network. Returns the new site. Requires edit access to Site Audit.

Scope

seo_site_auditor:write

Permission

Edit in the module

MCP tool

seo_site_auditor_sites_createOn the full surface; on the compact one, mb_execute_operation with id: "seo_site_auditor.sites.create".

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

Parameters

Response

Errors

Example

curl -X POST "https://api.mb-suite.com/v1/seo/site-auditor/sites" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "url": "URL"
}'

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 -X POST "https://api.mb-suite.com/v1/seo/site-auditor/sites" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
  "url": "URL"
}'

Change an audited site's configuration

seo_site_auditor.sites.update

Changes one or more settings of an audited site: url, name, max_pages (1–500), schedule (replaced whole: frequency manual/weekly/monthly, day_of_week or day_of_month, enabled), notify_emails (up to 10, replaced whole), exclude_patterns (up to 50, replaced whole; each starts with / or *) and exclude_mode. Only what actually changes is written: a new schedule moves next_due_at to its next day (and switching it on clears the failure count of a site the system paused); a new url forgets how the site was crawled last time and checks Cloudflare again. Changes apply from the next audit; past audits keep their results. Sending the current values changes nothing. Returns the site. Errors: audit_site_not_found (404), invalid_site_url (400). Requires edit access to Site Audit.

Scope

seo_site_auditor:write

Permission

Edit in the module

MCP tool

seo_site_auditor_sites_updateOn the full surface; on the compact one, mb_execute_operation with id: "seo_site_auditor.sites.update".

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

Parameters

Response

Errors

Example

curl -X PATCH "https://api.mb-suite.com/v1/seo/site-auditor/sites/{site_id}" \
  -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 -X PATCH "https://api.mb-suite.com/v1/seo/site-auditor/sites/{site_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY"

Delete an audited site and its audits

seo_site_auditor.sites.delete

Deletes an audited site together with ALL its audits (their issues and crawled pages). The site's configuration (url, schedule, notify emails, exclusions and intentional rules with their reasons) stays 30 days in the trash and can be restored, but the audit history does not come back: restoring brings the site back with no audits, its next scheduled audit computed from the restore day (409 audit_site_exists if the account has another site by then). Outside the screen it always needs a dry run (which counts the audits that go with it) and its confirm_token. A site with an audit still queued or running cannot be deleted (audit_in_progress, 409). Not found (audit_site_not_found) if it does not exist. Requires edit access to Site Audit 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_site_auditor:write and “Allow deletions” (seo_site_auditor:delete in OAuth)

Permission

Edit in the module

MCP tool

seo_site_auditor_sites_deleteOn the full surface; on the compact one, mb_execute_operation with id: "seo_site_auditor.sites.delete".

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

Parameters

Response

Errors

Example

curl -X DELETE "https://api.mb-suite.com/v1/seo/site-auditor/sites/{site_id}" \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "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.

curl -X DELETE "https://api.mb-suite.com/v1/seo/site-auditor/sites/{site_id}" \
  -H "Authorization: Bearer $MB_TEST_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "dry_run": true
}'