See the AI crawler activity your logs can show.
Upload a server log or add a Cloudflare Worker snippet to inspect AI bot visits and errors. Log uploads are read in your browser, and only daily counts are stored for reporting.
Free with an account. Sign in when you run it; this page stays open to read.
Requests are activity, not answer citations.
Illustrative exampleChoose a crawler and inspect the sample daily counts and errors.
Crawler activity and errors, with a clear storage boundary.
Fictional aggregated logs. No file is uploaded and no crawler identity is verified here.
Find access problems in the request record
Review crawler counts and errors by day. Logs can show that a request occurred or failed under the identification method used. They do not show a human visit, a citation in an answer or a lead influenced by AI.
When the logs suggest an access problem, the AEO audit adds website-check evidence to the review.
Choose a collection path that fits your setup
Use a log upload for an existing file or review the Worker snippet for your Cloudflare deployment. Understand what is collected before adding a snippet. The product retains daily counts rather than storing uploaded raw request lines.
The Search Console integration supplies a separate search-impression context; neither measurement turns crawler requests into buyers.
How it works
- Choose a server-log upload or the Worker snippet route.
- Inspect daily bot counts and errors.
- Review relevant access issues alongside the site audit.
What to know before you use it
- Uploaded logs are read in the browser; only daily counts are stored.
- Bot labels depend on the log and identification rules.
- Crawler visits do not establish citations, training use, human visits or revenue.
Questions
Do you store the raw uploaded log?
The described upload flow reads it in the browser and stores only daily counts.
Does a crawler visit mean we were cited?
No. A request is separate from an AI answer or a human visit.
Put crawler activity in context.
Review access findings as one part of your content, entity and external-source programme.