CDN log connectors for AI crawler tracking
Proofsource connects to the logs your site already produces, from Cloudflare, a storage bucket or a custom HTTPS drain, and turns them into AI crawler analytics. Each source shows its status and last sync, and the screen explains what is missing until one is live. It is for web and SEO teams who want AI bot data without adding code to their site.
| Source | Type | Status | Last sync |
|---|---|---|---|
| driffle.ai zone | Cloudflare | Ingesting | 4 min ago |
| driffle-edge-logs | Storage bucket | Ingesting | 12 min ago |
| blog drain | Custom HTTPS | Waiting for first batch | - |
Crawler log sources, in short
The facts, ready to quote.
- Sources
- Cloudflare, a storage bucket and custom HTTPS log drains; the WordPress plugin is in early access
- Site changes needed
- None for CDN connections: logs are read from the source
- Status
- Each source shows connected, ingesting or waiting, with its last sync
- Before logs arrive
- Until a source is live, the AI Traffic screen explains what is missing and links to setup
- Feeds
- AI Traffic Analytics, crawler verification and the Crawled step of the AI Funnel
- Access
- Read-only; you can disconnect a source at any time
What is a CDN log source for AI crawler tracking?
CDN log tracking means reading the request logs your content delivery network or hosting already writes, instead of adding a tracking script to the page. Every request is in those logs, including requests from AI crawlers that never run JavaScript, so they are the most complete record of how AI bots use your site.
The hard part is plumbing: every CDN and host exports logs differently, field names vary and pipelines break quietly. Teams often give up before the data is useful.
Proofsource maps and ingests logs from Cloudflare, from storage buckets and from custom HTTPS drains, keeps each source's status visible and syncs on a schedule. If no source is connected yet, the AI Traffic screen says so in plain words and links to the crawler sources page, so nobody mistakes an empty chart for zero AI interest.
How it works
Connect Cloudflare, a storage bucket or a custom log drain so Proofsource can count AI crawler visits from your real traffic.
Pick a source
Choose Cloudflare, a storage bucket, or a custom HTTPS drain on the crawler sources page.
Grant read access
Connect with read access to the logs. Proofsource never changes your CDN rules.
Logs are mapped and synced
Fields from each source are mapped to one shape and new requests are ingested on a schedule, or on demand with Sync now.
Read AI crawler analytics
Once ingesting, AI bot visits appear in AI Traffic Analytics, crawler verification and the AI Funnel.
See it in the product
Screens from the Proofsource app, drawn with sample data for an example brand.
| Bot | Visits | Top page |
|---|---|---|
| GPTBot | 1,640 | /pricing |
| ClaudeBot | 1,122 | /features |
| PerplexityBot | 861 | /compare/otter |
| OAI-SearchBot | 559 | /blog/meeting-notes |
Every capability, live today
3 shipped capabilities behind crawler log sources, each in the product now.
CDN connectors and crawler log sources
Connect a CDN such as Cloudflare, a storage bucket or a custom HTTPS drain, map its logs into one shape and keep them syncing, each with its own status and a manual Sync now.
Connection notes
Explains a missing log source and the Cloudflare connection state, with a link to the crawler sources page.
Log drains for crawler data
Send Cloudflare logs or any custom log drain to Proofsource to track AI crawler visits.
Who it is for
Add AI bot data without a deploy
Connect the CDN you already run and get crawler analytics with no code on the site.
Use the log pipeline you have
Point an existing storage bucket or log drain at Proofsource instead of building a new export.
Know every source is healthy
Each source shows connected, ingesting or waiting with its last sync, so a quiet pipeline never looks like zero AI interest.
Why it matters
Complete bot data
Logs include every AI crawler request, which page scripts can never see.
Status you can trust
Every source shows whether it is ingesting and when it last synced.
No empty-chart confusion
Until logs arrive, the screen says what is missing instead of showing zero.
Crawler log sources: Proofsource and other tools
Most crawler analytics products read CDN or server logs; here are the sources each public page names.
| Capability | Proofsource | Profound | Peec AI | Otterly.AI | Rankscale |
|---|---|---|---|---|---|
| Cloudflare connection | YesCloudflare connector with status and Sync now | YesForwarding from AWS, Akamai, Cloudflare, Fastly, GCP, Netlify, VercelSource | YesBot visit insights via Cloudflare, CloudFront, AkamaiSource | YesUpload, webhook, Cloudflare or WordPress pluginSource | YesRead-only Cloudflare connection for AI visitsSource |
| Storage bucket logs | YesIngests logs delivered to a storage bucket | YesCDN logs from Cloudflare, Fastly, CloudFront, Akamai sent by S3 log deliverySource | Not listed | Not listed | Not listed |
| Custom drain or webhook | YesCustom HTTPS log drains | Not listed | Not listed | YesWebhook log connectionSource | Not listed |
| WordPress plugin | YesWordPress plugin as a log source, in early access | Not listed | Not listed | YesWordPress plugin log connectionSource | Not listed |
| Logs, not a JavaScript tag | YesReads logs your site already produces, with no code added | YesReads server logs, not a JavaScript trackerSource | YesBot visit insights via CDN and log providers; Cloudflare, CloudFront, AkamaiSource | YesWhich AI crawlers and agents visit your site, from server logsSource | Not listed |
| Hosting provider logs | YesCustom HTTPS drains take logs from hosting providers | YesForwarding from AWS, GCP, Netlify, Vercel and moreSource | Not listed | Not listed | Not listed |
| Genuine bots told from spoofed ones | YesFeeds crawler verification | YesSeparates genuine AI bots from spoofed crawlersSource | Not listed | Not listed | Not listed |
| Status and last sync per source | YesEach source shows connected, ingesting or waiting, with its last sync | Not listed | Not listed | Not listed | Not listed |
Where each of them shines
Log forwarding from AWS, Akamai, Cloudflare, Fastly, GCP, Netlify and Vercel, plus Shopify and Adobe. Compare in full
Crawler analytics from Cloudflare, CloudFront and Akamai joined to page-level citations. Compare in full
Four simple ways to send logs: upload, webhook, Cloudflare or a WordPress plugin. Compare in full
A read-only Cloudflare connection that keeps setup light.
Questions about crawler log sources
Which CDN and log sources can I connect?
Cloudflare, a storage bucket that receives your logs and a custom HTTPS log drain. A Proofsource WordPress plugin for sites without their own CDN is in early access: join and we turn it on for your workspace.
Do I need to add code to my website?
Not for CDN, bucket or drain connections. Proofsource reads the logs your infrastructure already writes. The WordPress plugin, in early access, is the option for sites that do not manage a CDN.
Why use logs instead of Google Analytics for AI bots?
AI crawlers do not run JavaScript, so tag-based analytics never records them. Logs contain every request, bots included.
How do I know a source is working?
Each source shows its status, such as ingesting or waiting, and its last sync time. You can also press Sync now.
What happens before any logs arrive?
The AI Traffic screen shows a plain note that no log source is connected, or that Cloudflare is not connected yet, with a link to the crawler sources page. It never shows a misleading zero.
Is my log data used for anything else?
It is used to show your own AI crawler analytics, verification and AI Funnel inside your workspace.
How is this different from Profound or Otterly log connections?
Profound covers a very wide range of hosts and CDNs, and Otterly offers upload, webhook, Cloudflare and WordPress. Proofsource feeds the same logs into crawler analytics, verification and a crawled-to-converted funnel for each page.
Keep exploring
Try it on your own brand.
Proofsource is live: scan your brand and see crawler log sources at work with your own answers, competitors and sources.