hosting
GET /v1/sites/{siteId}/crawler-policy
Get a site's SEO-crawler-blocking (PBN footprint) policy.
Authentication
Send an API key as a bearer token. The key must carry the sites.view permission; 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/sites/{siteId}/crawler-policy \
-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
The effective crawler-block policy for a site — the stored override or the line default (the PBN/footprint-free line blocks every SEO crawler by default; other lines block none). Returns the blocked crawler keys, the catalog of blockable crawlers, and the rendered `robots.txt` + server rules. Search engines (Googlebot/Bingbot) are never blockable. Requires `sites.view`.
Parameters
| Name | Type | Required | What it is |
|---|---|---|---|
siteId (path) | Uuid | Yes | Site ID (UUIDv7). |
Response
| Name | Type | Required | What it is |
|---|---|---|---|
site_id | Uuid | Yes | UUIDv7 identifier — sortable by creation time (docs/02 §8). |
policy | CrawlerPolicy | Yes | — |
available_crawlers | CrawlerCatalogEntry[] | Yes | — |
rendered | CrawlerPolicyRendered | Yes | The rendered rule artifacts for the worker / Zinn® plugin to write. |
enforcement | CrawlerEnforcement | No | Whether the stored crawler policy is actually a rule on a web server, and if not why not (#1954, D8300). ⛔ These are two different questions and collapsing them is the defect th… |
Errors this endpoint can return
401 · 403 · 404 · 429