Cloudflare Logpush setup now warns when a job sends no user agent
A Logpush job saved with Cloudflare's default field selection delivers requests without the user agent, so no bot can be identified; the dashboard and setup check now say so and show the fix, and the setup step tells you to select all fields.
Cloudflare's default field selection for a Logpush job leaves out the user agent. A job saved that way delivers every request, so the feed looks healthy, but nothing can be told apart from a browser: Googlebot, AI crawlers and every other bot show as zero.
From today:
- The Create the Logpush job step says to choose Select all on the data fields step, and why.
- If a job is already sending requests without the user agent, the dashboard shows Your Logpush job sends no user agent with the three Cloudflare steps to fix it, the header badge reads Fields missing instead of Live, and the setup check reports the same.
The fix is a one-time edit of the job in Cloudflare (Analytics & Logs → Logpush → the job → Edit → select all fields → Save). No new destination URL is needed, and bots appear within minutes of the save. Requests received before the change keep their empty user agent.