See which AI crawlers are requesting your pages.
Browser analytics cannot see crawlers that never run JavaScript. Chad's server adapter records bounded request facts for known AI user agents and reports them separately from human visits.
AI crawler analytics measures machine requests from known AI user agents at the server. Useful fields include provider, crawler category, requested path, response status, and time—not browser sessions or conversions.
Classify the request by purpose
User-agent names describe the requester, not the business outcome. A crawl is evidence that a machine requested a page; it is not evidence of a citation, referral, lead, or sale.
- User retrieval: a tool fetched a page for a person's current request.
- AI search indexing: a crawler discovered content for answer or search experiences.
- Model training: a crawler fetched content for model development.
- Traditional search and monitoring: kept separate from AI-specific categories.
Why server-side tracking is required
The normal Chad snippet runs in a human browser. Known crawlers generally fetch HTML without executing that script, so an adapter at the framework, server, Worker, or WordPress layer is needed.
- Adapters for common JavaScript frameworks and servers.
- Cloudflare option for Webflow custom domains.
- WordPress plugin with crawler tracking.
- Fire-and-forget reporting that avoids request bodies, cookies, and authorization headers.
Ask better content questions
Use the report to find public paths that AI search, retrieval, or training bots request most often; identify important pages they cannot reach; and compare crawler demand with separate human referral trends.
Common questions
Can JavaScript analytics track AI crawlers?
Usually not. Known crawler requests need server-side request visibility.
Does a crawler request mean my page was cited?
No. It proves only that the crawler requested the path.
Does Chad store request bodies or authorization headers?
The crawler adapter is designed to send bounded request metadata such as method, path, user agent classification, status, and time—not bodies, cookies, or authorization headers.