hosting

PUT /v1/sites/{siteId}/crawler-block

Replace a site's blocked-crawler selection.

Gbogbo àwọn hosting endpoints

Ìfàṣẹ́pọ̀

Fi bọ́ọ̀lù (bearer token) ranṣẹ gẹ́gẹ́ bí kọ́kọ́rọ́ API. Kọ́kọ́rọ́ náà gbọ́dọ̀ ní ìyọ̀ǹda sites.crawler.manage; a ó kọ̀ ọ́ silẹ pẹlu 403, kii ṣe 404, ti kọ́kọ́rọ́ náà kò bá ní i.

Ojú abánisọ̀rọ̀ yìí kò gba id ajọ kankan. Kọ́kọ́rọ́ rẹ ti mọ ajọ ti o jẹ ti e, a o si fèsì nipa rẹ̀.

Gbiyanju rẹ

Rọ́pọ̀ èyíkéyìí nínú àwọn àmì ìtọ́ka < > pẹ̀lú iye tirẹ̀, àti àmì ìdánimọ̀ bọ́tìnnì náà pẹ̀lú bọ́tìnnì kan láti inú dásibọ̀ọ̀dù rẹ.

curl -X PUT https://api.zinndigital.com/v1/sites/{siteId}/crawler-block \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "blocked_bots": <string[]> }'

Ṣé o ti wọlé? Iwọ̀n api ní nú ìgbékalẹ̀ rẹ kún id àjọ gidi rẹ ati bọtini tirẹ, o si nṣiṣẹ ibeere na lòdì si api gidi ki o le rii esi gidi na. Ṣí ojú abáná yìí sílẹ̀ nínú kọnsólù API

Àwọn kúlẹ̀kúlẹ̀

Replaces the blocked set. Only keys from `available_bots` are accepted; an unknown key is rejected rather than ignored. Settings this surface does not expose (`robots_txt`, `ip_deny`) are preserved, never reset. Requires `sites.crawler.manage`.

Àwọn ìpìlẹ̀

OrúkọIruTí a nílòKini o jẹ
siteId (path)UuidBẹẹniSite ID (UUIDv7).

Akoonu ibeere naa

OrúkọIruTí a nílòKini o jẹ
blocked_botsstring[]Bẹẹni

Idahun

OrúkọIruTí a nílòKini o jẹ
site_idUuidBẹẹniUUIDv7 identifier — sortable by creation time (docs/02 §8).
blocked_botsstring[]BẹẹniCrawler keys currently blocked at the server level.
available_botsstring[]BẹẹniThe crawlers the customer may block. Contains no search engine, which is what makes de-indexing yourself impossible through this surface.
enforcementCrawlerEnforcementBẹẹkọ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…

Awọn aṣiṣe ti ibudo ipari yii le da pada

401 · 403 · 404 · 422 · 429