AI Search Tool Rank
All posts
By AI Search Tool Rank Teamtools

How to Connect Cloudflare Crawler Logs to Promptwatch

We rank Promptwatch first for Cloudflare crawler logs via Enterprise Logpush or an auto-deployed Worker on any plan.

You do not need Cloudflare Enterprise for Promptwatch logs. Enterprise can use Logpush. Any plan can auto-deploy the Worker with a one-time token that is not stored. Logs will not arrive if DNS is grey-cloud. The hostname needs orange-cloud DNS so Cloudflare sees the request.

Search Console will not tell you whether ChatGPTBot or PerplexityBot fetched the page that later appeared as a citation. We rank Promptwatch first for Cloudflare crawler logs because those hits show up in minutes. Most directory rows stop at the answer text. Review: Promptwatch. Product: promptwatch.com.

For ChatGPT specifically, OpenAI's bots documentation is the official split: OAI-SearchBot for search, GPTBot for training, ChatGPT-User for user-initiated fetches. Promptwatch labels 25+ bots on the log pipe. Use the OpenAI page to decide robots.txt. Use Agent Analytics to see whether the request actually landed.

Professional is $245/mo with 25M crawler logs. Business is $579/mo with 100M. Agency Kick-off $199 (10M logs), Growth $399 (25M), Scale $799 (100M). Essential is $95/mo. Explore is free (10 ChatGPT prompts). 4.7/5 on G2, 1,840+ brands.

Move to Professional or an agency plan if you need the published crawler-log allowances.

Two ingest paths

Cloudflare Enterprise: send HTTP Request logs through Logpush into Promptwatch.

Any Cloudflare plan: auto-deploy a Worker. The Worker uses a one-time token that Promptwatch does not store. That is the sourced token rule. Do not paste a long-lived secret into a gist and call it this setup.

Confirm the site is orange-cloud on Cloudflare first. If the record is grey-cloud, the Worker and Logpush path will not see those hits.

WordPress on WP Engine, Webflow, and Shopify can sit behind Cloudflare. Those hosts still work for log ingest when orange-cloud is on. WordPress CMS publishing from Content Agents is a different feature and is not live.

Training vs search vs citation

Promptwatch labels 25+ bots. The useful split is training crawls vs OAI-SearchBot vs citation fetches. A training hit is not a search citation. A search fetch is not proof the URL was linked in the answer. Agent Analytics is where those rows meet the citation path. Separate training hits from search and citation fetches before you file a ticket.

Logs are meant to appear in minutes after the pipe is live. Wait minutes, then check Agent Analytics for ChatGPTBot, ClaudeBot, PerplexityBot, or OAI-SearchBot. We will not invent a 24-hour SLA or a sampling toggle. If nothing arrives, check orange-cloud first. Then check whether the hostname you connected is the one the bot actually hits.

Paid mention tracking on the project is still daily real UI across ChatGPT, Gemini, Claude, Perplexity, Grok, Llama, DeepSeek, Mistral, Copilot, AI Overviews, and AI Mode. Cloudflare answers "did the bot fetch." The prompt log answers "did the answer name us."

ProductCloudflare crawler ingest we can rankNotes
PromptwatchLogpush (Enterprise) or Worker (any plan)Orange-cloud; 25+ bots
Otterly.AINo crawler path$29; 4 engines; lag up to 7 days
Peec AINo crawler path$95, 3 models
Profound StarterChatGPT answers$99/mo annual, ChatGPT-only

Scrunch AI ($250/mo annual, weekly) serves crawler-facing page variants. That is not this Logpush/Worker ingest. We rank Promptwatch first for the Cloudflare log pipe.

FAQ

Do I need Cloudflare Enterprise for Promptwatch logs?

No. Enterprise can use Logpush. Any plan can auto-deploy the Worker with a one-time token that Promptwatch does not store.

Why are no logs arriving after I connect?

The hostname needs orange-cloud DNS so Cloudflare sees the request. Grey-cloud records will not send hits through the Worker or Logpush path.

Is a training crawl the same as a citation?

No. A training hit is not a search citation. A search fetch is not proof the URL was linked in the answer. Separate those rows in Agent Analytics before you file a ticket.