Cloudflare Integration

If your site is fronted by Cloudflare, a significant share of AI bot hits can land on cached pages that Cloudflare serves directly, without the request ever reaching WordPress. Visibility Kit's server-side bot detection misses these. Cloudflare Integration closes the gap.

How it works

Visibility Kit queries Cloudflare's GraphQL Analytics API for bot hits on your zone and reconciles them against what your server already logged. Anything Cloudflare saw but your server didn't gets added to your Visibility Kit data.

• You connect Cloudflare by pasting a scoped API token into your Visibility Kit site settings.
• Visibility Kit pulls bot hits from Cloudflare on a schedule.
• Duplicates are de-duped against your server-side detection so you don't double-count.

Enabling Cloudflare Integration

1. In Cloudflare, create an API token with Analytics: Read permission scoped to the relevant zone.
2. In your Visibility Kit site settings, click Connect Cloudflare and paste the token.
3. Bot hits from the last 24 hours begin syncing within a few minutes.

What this catches

• AI bot hits on fully-cached pages.
• AI bot hits on edge-rendered HTML.
• AI bot hits on static assets Cloudflare treats as cacheable.

What this doesn't catch

• AI referrals from real humans. Those are caught by the frontend tracking script regardless of caching, because the script runs in the browser after the page loads.
• Pages excluded from Cloudflare Analytics by your CF configuration.

Do you need it?

If you don't use Cloudflare, skip this entirely. If you do use Cloudflare and your server-side bot counts look lower than you'd expect, enable it. You're almost certainly missing cached bot traffic.