KezAIStudioBot

• Only when a KezAI Studio user adds the website as one of their brands, or asks for a new scan. There is no crawling of the wider web.
• At most one full scan of a website per week, and at most 200 pages per scan.
• It reads the home page, the sitemap and the pages that describe the business (about, services, products, pricing, contact, a few articles). It doesn't sign in, submit forms or read pages behind a login.

Every page request carries this User-Agent:

Mozilla/5.0 (compatible; KezAIStudioBot/1.0; +https://app.kezaiautomation.com/bot)

Pages are fetched through DataForSEO's crawling service, so requests come from DataForSEO's network rather than from one fixed address. The robots.txt and sitemap files are read by our own server with the same User-Agent. When a user connects their own WordPress site to publish drafts, those requests say:

KezAIStudio/1.0 (+https://app.kezaiautomation.com/bot)

• KezAIStudioBot follows robots.txt (RFC 9309). If the file has a group for KezAIStudioBot, that group applies; otherwise the * group does. Disallowed pages are never requested.
• If robots.txt can't be read because the server errors or times out, nothing is read.
• It never works around a block: no rotating addresses, no browser disguise. If your firewall or bot protection turns it away, it stops and tells the user that the site blocks it.

Add this to your robots.txt:

User-agent: KezAIStudioBot
Disallow: /

If an agency you work with can't scan your site, your firewall or bot protection is probably turning KezAIStudioBot away. Allowing it lets their articles use what your pages actually say.

Cloudflare

Security → Security rules → Create rule → Custom rule. Match the User-Agent and choose the action Skip, then select what to skip (the remaining custom rules, managed rules and, on paid plans, Super Bot Fight Mode):

(http.user_agent contains "KezAIStudioBot")

On the Free plan, Bot Fight Mode can't be skipped by a rule. If it blocks KezAIStudioBot, the only switch is to turn Bot Fight Mode off for the site (Security → Settings).

nginx

If your configuration rejects user agents that contain "bot", exempt ours:

set $block_bot 0;
if ($http_user_agent ~* "bot") { set $block_bot 1; }
if ($http_user_agent ~* "KezAIStudioBot") { set $block_bot 0; }
if ($block_bot) { return 403; }

Apache (.htaccess)

RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} bot [NC]
RewriteCond %{HTTP_USER_AGENT} !KezAIStudioBot [NC]
RewriteRule ^ - [F]

WordPress security plugins and hosting firewalls

Look for an allowlist of user agents or bots and add KezAIStudioBot.

Questions about KezAIStudioBot, or a request about your site: support@kezaiautomation.com.