KlaviyoAIBot user agent
Operated by Klaviyo
KlaviyoAIBot is the crawler Klaviyo uses to read a brand's website for its AI marketing features.
The KlaviyoAIBot bot at a glance
- KlaviyoAIBot is operated by Klaviyo and fetches a page when a person asks an AI assistant about it or shares its link.
- The robots.txt token for KlaviyoAIBot is KlaviyoAIBot.
- Blocking an AI assistant fetcher has no effect on search rankings.
- KlaviyoAIBot robots.txt support: Yes.
- Recommendation for Generative Engine Optimization (GEO): Your choice.
What is KlaviyoAIBot?
KlaviyoAIBot reads a customer’s own site so Klaviyo’s AI can write on-brand content.
Public registries report that it follows robots.txt.
Should you block KlaviyoAIBot?
Blocking KlaviyoAIBot is a business decision: it protects your content but can lower how well AI products know your brand.
| Effect on search rankings | Blocking an AI assistant fetcher has no effect on search rankings. |
|---|---|
| Effect on AI visibility | Blocking stops the assistant from reading your page when a user asks about it or pastes your link, so its answer falls back to other sources. |
| Follows robots.txt | Yes |
| Recommendation | Your choice |
How to block or allow KlaviyoAIBot
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token KlaviyoAIBot is matched case-insensitively.
robots.txt: block
# Block KlaviyoAIBot
User-agent: KlaviyoAIBot
Disallow: /robots.txt: allow
# Allow KlaviyoAIBot
User-agent: KlaviyoAIBot
Allow: /robots.txt: partial
# Keep KlaviyoAIBot out of private areas only
User-agent: KlaviyoAIBot
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to KlaviyoAIBot
if ($http_user_agent ~* "(KlaviyoAIBot)") {
return 403;
}Apache
# Apache .htaccess: return 403 to KlaviyoAIBot
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (KlaviyoAIBot) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "KlaviyoAIBot")How to verify real KlaviyoAIBot traffic
Klaviyo publishes no IP list or reverse DNS pattern for KlaviyoAIBot, so the user agent cannot be verified. Anyone can send the same string. Rate-limit unusual volume instead of trusting the name.
How to find KlaviyoAIBot in your server logs
Search the web server access log for the token. The command below counts KlaviyoAIBot requests per URL on Nginx or Apache.
grep -i "KlaviyoAIBot" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
KlaviyoAIBot FAQ
KlaviyoAIBot uses the robots.txt token "KlaviyoAIBot". Klaviyo does not publish a full user-agent string, so match the token inside the User-Agent header.
Yes. Klaviyo states that KlaviyoAIBot follows robots.txt rules written for the "KlaviyoAIBot" token.
Blocking an AI assistant fetcher has no effect on search rankings. Blocking stops the assistant from reading your page when a user asks about it or pastes your link, so its answer falls back to other sources.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: KlaviyoAIBot" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Not reliably. Klaviyo publishes no IP list or reverse DNS pattern for KlaviyoAIBot, so anyone can send the same user agent. Rate-limit unusual volume instead of trusting the name.
Search your server access log for "KlaviyoAIBot", for example with: grep -i "KlaviyoAIBot" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Public bot registry. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
