Proofsource and Amazon CloudFront: every AI crawler visit, counted
Send CloudFront real-time logs to Proofsource through Kinesis and Firehose and every verified AI crawler visit is counted per page. Grant a role with your distribution ID and the AI-readable page fix can also serve crawlers a clean copy of a page. Logs you already keep in S3 work too.
- Fields: timestamp, c-ip, sc-status, cs-method, cs-host, cs-uri-stem, cs-user-agent, cs-referer
- Destination: Kinesis, then Firehose to the URL below
- Key: write access, this brand only
POST https://api.proofsource.co/v1/crawler-logs/cloudfront
Proofsource and Amazon CloudFront, in short
The facts, ready to quote.
- Stage
- Live on every plan
- Connects with
- Real-time logs via Kinesis and Firehose with a brand-limited key; or standard logs through the S3 source
- Access it needs
- Logs: a write-only key limited to one brand. AI-readable pages: an AWS role plus the distribution ID
- Where it shows
- Integrations, Crawler sources, More crawler sources, and Fix it, AI-readable pages
- Bot check
- IP ranges plus reverse DNS on every visit
- Disconnect
- Delete the Firehose delivery or the real-time log configuration; remove the AWS role to stop edge changes
Why we love Amazon CloudFront
In the makers' own words, from their own pages. Proofsource builds on it, never around it.
A very large global network
CloudFront delivers content through hundreds of points of presence in cities worldwide, with regional caches and embedded locations in ISP networks, so content sits close to viewers.
From aws.amazon.comLogs within seconds
CloudFront real-time logs arrive within seconds, with the sampling rate, fields and cache behaviors all yours to choose.
From docs.aws.amazon.comSecurity and code at the edge
CloudFront adds layered protection with AWS Shield and WAF, TLS 1.3 and signed URLs, and lets developers run code at the edge with CloudFront Functions and Lambda@Edge.
From aws.amazon.comHow Proofsource uses Amazon CloudFront
Counts verified AI crawler visits from CloudFront logs and can change the distribution through a role you grant.
- Connect
Create the real-time log setup
A real-time log configuration with eight fields goes to a Kinesis stream, then Firehose delivers it to Proofsource.
- Read
Verify each visit
Lines are matched to AI crawlers and checked against published IP ranges and reverse DNS before they count.
- Ship
Serve a readable copy
With an AWS role and a distribution ID, the AI-readable page fix can change the distribution so crawlers receive a readable copy of a page.
- Prove
Measure pickup and answers
Proofsource shows whether crawlers fetched the page and then asks the engines again whether they name you.
Set up Amazon CloudFront in 4 steps
Open Integrations, Crawler sources
Choose More crawler sources, then CloudFront. The card shows the URL to use and lets you create a write key limited to this brand.
Create the real-time log configuration
Use these fields only: timestamp, c-ip, sc-status, cs-method, cs-host, cs-uri-stem, cs-user-agent and cs-referer. Send it to a Kinesis data stream.
Add Firehose to the Proofsource URL
Create a Firehose stream from Kinesis to an HTTP endpoint with the URL from the card, and put the brand key in the access key field.
Or use standard logs
If your logs already go to S3, use the Amazon S3 source instead. For AI-readable pages, add the role and distribution ID under Fix it.
What you unlock with Amazon CloudFront
Verified crawler counts
Real AI visits per page with impostors removed.
Edge pages
A readable copy served to AI crawlers from CloudFront.
Per-page reads
See which pages each engine fetched and when.
Brand-limited key
The write key can only send logs for one brand.
Block check
Spot rules that turn AI crawlers away.
Fix pickup
Confirm crawlers came back after each fix.
Google AI OverviewsGoogle AI Mode
Questions about Proofsource and Amazon CloudFront
What does Proofsource receive from CloudFront?
Only the eight log fields in the setup: time, viewer address, status, method, host, path, user agent and referrer. Proofsource keeps AI crawler visits and drops the rest.
What access does Proofsource need?
For logs, a write-only key limited to one brand, which cannot read anything. For AI-readable pages, an AWS role that you create and can remove at any time, together with the distribution ID.
I already store CloudFront logs in S3. Can I use those?
Yes. Use the Amazon S3 source, which reads those standard logs every 15 minutes through a read-only role. Real-time logs are the faster route.
How do I disconnect?
Delete the Firehose delivery or the real-time log configuration to stop logs, and remove the AWS role to stop edge changes. Past counts stay unless you ask us to delete them.
Will AI-readable pages change what visitors see?
No. The copy is for AI crawlers. Visitors still get the page exactly as designed, and you can preview what crawlers see before turning it on.
How does this help my AI visibility?
Engines can only cite pages they can read. Logs show which pages crawlers reach, and a readable copy repairs the ones they could not. Proofsource then checks whether the engines name you.
Which AI engines does Proofsource check?
Up to 10 depending on your plan: ChatGPT, Perplexity, Claude, Google AI Overviews, Google AI Mode, Gemini, Microsoft Copilot, Grok, DeepSeek and Meta AI. The free scan and the trial run four.
Pairs well with Amazon CloudFront
Put Amazon CloudFront to work for your AI visibility.
Scan your brand, connect Amazon CloudFront, and see what AI says about you on up to 10 engines.
Google AI OverviewsGoogle AI Mode