AI search

KlaviyoAIBot

Indexes connected website content for Klaviyo’s customer agent.

See your agent traffic
PurposeAI search
HTTP identifierKlaviyoAIBot
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

Requests should relate to sources connected to a Klaviyo account.

Fetched pages
Failed retrievals
Repeat fetches

Your next move

Check configured source domains and verify signatures before allowing unexpected requests.

The technical details

Markdown
How to identify it

Look for the KlaviyoAIBot identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Validate the published HTTP message signature or check Cloudflare’s verified-bot result, as described by Klaviyo.

Access and robots.txt

The operator documents robots.txt rules for this identifier.

Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.

User-agent: KlaviyoAIBot
Disallow: /
Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See KlaviyoAIBot in context

See their requests. Find the pages that matter.

See your agent traffic