Cloudflare AI Visibility Integration

Finseo offers a native Cloudflare integration that streams AI crawler requests from your zone into its Bot Traffic dashboard using a lightweight Worker or an Enterprise Logpush job. You see which pages the crawlers behind ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews, and Microsoft Copilot fetch, which grounds Answer Engine Optimization (AEO) in real crawl data.

Yes. Connect Cloudflare to Finseo and the Worker reports every request whose User-Agent matches GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot, Google-Extended, Bingbot, and other known crawlers. Bot Traffic groups them by crawler and URL, so you know whether ChatGPT and Claude reach your pricing and documentation pages or stop at the homepage, within seconds of each visit.

Yes. Finseo is a Generative Engine Optimization (GEO) platform with a native Cloudflare integration. The two do different jobs: Cloudflare delivers and protects your site at the edge, while Finseo turns the crawler requests it sees into AI visibility insight, correlating what GPTBot or PerplexityBot fetch with the sources ChatGPT and Perplexity actually cite.

Copy your Zone ID and Account ID from the Cloudflare Overview page and create a custom API token with Workers Scripts: Edit, Workers Routes: Edit, and Zone: Read. In Finseo, open Bot Traffic, Sync, click Connect on the Cloudflare card, paste the three values, and click Deploy Worker. Alternatively copy the Worker script and deploy it yourself.

Finseo receives only crawler requests: IP address and User-Agent, host, method, path and query string, referrer, HTTP status and response size, country, city, region, timestamp, and time to first byte. Regular visitor traffic never leaves Cloudflare. Your API token is used once to deploy the Worker and then discarded; Finseo never stores it.

Yes. Every Finseo plan includes the Cloudflare integration with no per-integration fee. On the Cloudflare side, the Worker method runs on every plan including Free, while the Logpush method needs a Cloudflare Enterprise plan because the http_requests dataset is only available there. The Worker delivers the same fields with lower latency.

Yes. Enterprise customers can push the Cloudflare http_requests dataset to Finseo through a Logpush job instead of deploying a Worker. The API token then needs Zone: Logs: Edit, and Logpush sends a test upload immediately. Both methods transmit the same fields per bot request and land in the same Bot Traffic project, deduplicated alongside manually uploaded logs.

AI crawlers such as GPTBot, ClaudeBot, and PerplexityBot never execute JavaScript, so client side analytics snippets never see them, and the only record of what ChatGPT, Claude, or Perplexity read on your site is the edge request log. Finseo turns that Cloudflare log into a live feed per crawler and URL for Answer Engine Optimization (AEO) work.

No. The finseo-bot-traffic Worker forwards every request unchanged and reports crawler visits in the background only after the response is sent, so visitors are never delayed or altered. If the Workers Free plan limit of 100,000 requests per day is exceeded, Cloudflare serves traffic normally and simply skips the Worker. Disconnecting in Finseo invalidates the ingest token.

An AI engine can only cite a page its crawlers can read. Bot Traffic shows which crawlers reach which pages, sorted by purpose (live answer, search index, training), and where they are blocked or hit errors, so you can fix access before it costs you visibility in ChatGPT, Claude or Perplexity.