seo-connect
GET /v1/seo-connection/guard
SEO Guard for this site — settings, open problems and recent fixes.
Authentication
Send an API key as a bearer token. The endpoint checks sites.view; 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 GET https://api.zinndigital.com/v1/seo-connection/guard \
-H "Authorization: Bearer zdk_live_…"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
SEO Guard checks the site from outside: the home page and up to 20 key pages for noindex (including WordPress's "Discourage search engines"), robots.txt blocking Google, the sitemap, canonical addresses changing together, the home title, the certificate's expiry and whether the site answers at all. Daily on Free, every 15 minutes on a Zinn® SEO Pro licence Freemius confirms. Created switched on at first use. Needs seo.read.
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