seo-connect
PUT /v1/seo-connection/guard
Change SEO Guard for this site.
Authentication
Send an API key as a bearer token. The endpoint checks sites.create; a key without it is refused with 403, not 404.
This endpoint takes no organisation id. Your key already identifies the organisation it belongs to, and the response is scoped to it.
Try it
Replace anything in angle brackets with your own values, and the key placeholder with a key from your dashboard.
curl -X PUT https://api.zinndigital.com/v1/seo-connection/guard \
-H "Authorization: Bearer zdk_live_…" \
-H "Content-Type: application/json" \
-d '{ }'Signed in? The API console in your dashboard fills in your real organisation id and your own key, and runs the request against the live API so you can see the actual response. Open this endpoint in the API console
Details
Any of: switch it on or off, set the key pages (on this site only, at most 20), send the Pro licence (checked with Freemius — the plan is never taken from the site; a confirmed licence holds the 15-minute cadence for 8 days and is re-sent by the plugin), accept the current canonical addresses as the new normal (rebaseline), or ask for a check at the next sweep (check_now). Audited. Needs seo.run.
Request body
| Name | Type | Required | What it is |
|---|---|---|---|
enabled | boolean | No | — |
key_urls | string[] | No | — |
licence | object | No | — |
rebaseline | boolean | No | — |
check_now | boolean | No | — |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
enabled | boolean | Yes | — |
site_url | string | Yes | — |
key_urls | string[] | Yes | — |
max_key_urls | integer | Yes | — |
tier | string<free, pro> | Yes | — |
interval_minutes | integer | Yes | 1440 on Free |
pro_until | object | Yes | — |
last_checked_at | object | Yes | — |
next_check_at | object | Yes | — |
incidents | SeoGuardIncident[] | Yes | Every open problem, and those fixed in the last 30 days. |
Errors this endpoint can return
401 · 403 · 422