seo-connect

POST /v1/seo-connection/cloak-checks

Fetch a page as a visitor and as Googlebot, and compare. Free.

All seo-connect endpoints

All developer docs →

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 POST https://api.zinndigital.com/v1/seo-connection/cloak-checks \
  -H "Authorization: Bearer zdk_live_…" \
  -H "Content-Type: application/json" \
  -d '{ "url": <string> }'

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 hacked-site detector's cloak check: one page of this site fetched with a browser user agent and with Google's crawler user agent, and the two compared — status, redirect, title, text, spam words and outbound links only Googlebot sees, and the Japanese-keyword hack. Runs in the background: read it with getSeoSiteCheck. It sees cloaking keyed on the user agent, not on Google's own addresses (limits). Free, at most 200 a day per site. Needs seo.run.

Request body

NameTypeRequiredWhat it is
urlstringYesA page on the connected site.

Response

NameTypeRequiredWhat it is
idstringYes—
kindstring<cloak, lab>Yes—
urlstringYes—
statusstring<queued, complete, failed>Yes—
resultobjectYesCloak: verdict (same, differs, cloaked, unreadable), signals, similarity_bps, spam_terms_for_bot, extra_link_hosts_for_bot, visitor, googlebot, limits.…
errorstringYes—
spent_microsintegerYesNet Zinn® credits taken
currencystring<USD>Yes—
created_atstringYes—
finished_atobjectYes—

Errors this endpoint can return

401 · 403 · 422 · 503