Proofsource and Adobe Experience Manager: know which AI crawlers reach your pages
Add one log forwarding rule to your AEM as a Cloud Service config pipeline and Proofsource counts every verified AI crawler visit from the forwarded CDN logs. Enterprise sites can see which pages ChatGPT, Claude and Perplexity actually read, without touching a template.
kind: CDN
version: 1
data:
logForwarding:
https:
default:
url: https://api.proofsource.co/v1/crawler-logs/aem
authHeaderName: Authorization
authHeaderValue: Bearer <your key>Proofsource and Adobe Experience Manager, in short
The facts, ready to quote.
- Stage
- Live on every plan
- Connects with
- A CDN log forwarding rule over HTTPS in the AEM Cloud Service config pipeline
- Access it needs
- A Bearer key limited to one brand that can only write logs; no access to your author or publish tiers
- Where it shows
- Integrations, Crawler sources, More crawler sources, Adobe Experience Manager
- Bot check
- IP ranges plus reverse DNS on every visit
- Disconnect
- Remove the forwarding rule and redeploy; delete the key in Proofsource
Why we love Adobe Experience Manager
In the makers' own words, from their own pages. Proofsource builds on it, never around it.
Cloud service that scales itself
AEM as a Cloud Service scales up and down with demand and ships updates continuously, so teams spend their time on experiences rather than infrastructure.
From experienceleague.adobe.comA managed CDN tuned for AEM
The built-in CDN serves cacheable content from edge nodes near users and gives you filter rules, redirects, custom error pages, cache purging and edge functions.
From experienceleague.adobe.comLogs you can forward
AEM's logging documentation shows how to forward logs from the Cloud Service to your own destinations, so operations data does not stay locked in.
From experienceleague.adobe.comHow Proofsource uses Adobe Experience Manager
Counts verified AI crawler visits from your AEM site's forwarded CDN logs, sent over HTTPS with a Bearer key.
- Connect
Add the forwarding rule
One CDN log forwarding rule in the config pipeline points at the Proofsource URL with a Bearer header.
- Read
Match and verify
Lines are matched to known AI crawlers and checked against published IP ranges and reverse DNS.
- Show
See reads per page
Crawler sources lists each page, crawler and status code for your AEM site.
- Prove
Check fixes were picked up
After content changes, Proofsource shows whether crawlers fetched the updated pages and whether the engines name you.
Set up Adobe Experience Manager in 4 steps
Open Integrations, Crawler sources
Choose More crawler sources, then Adobe Experience Manager. The card shows the URL and the header value.
Create a key for this brand
Make a Proofsource API key limited to this brand with write access.
Add the rule to your config pipeline
Add a log forwarding rule for CDN logs over HTTPS, using the URL, with authHeaderName set to Authorization and authHeaderValue set to Bearer followed by your key.
Deploy the config and check
Once the pipeline deploys, the card shows the first deliveries. Remove the rule and redeploy to stop.
| Section | Crawler | Visits |
|---|---|---|
| /products | GPTBot | 1,310 |
| /support | ClaudeBot | 864 |
| /news | PerplexityBot | 520 |
What you unlock with Adobe Experience Manager
Verified crawler counts
Real AI visits across a large site, with impostors removed.
Section-level reads
See which parts of a big site the engines reach.
Brand-limited key
The Bearer key writes logs for one brand and reads nothing.
Block check
Find CDN rules that turn AI crawlers away.
Fix pickup
Confirm crawlers returned after content changes.
AI traffic
Crawler visits beside AI referral clicks.
Questions about Proofsource and Adobe Experience Manager
What does Proofsource receive from AEM?
The CDN log lines your forwarding rule sends: time, client address, user agent, path, host and status. Proofsource keeps AI crawler visits and drops the rest. It has no access to author or publish, content or code.
How do I connect Adobe Experience Manager?
Add a CDN log forwarding rule over HTTPS in the AEM Cloud Service config pipeline, using the URL from the Proofsource card, with an Authorization header set to Bearer and a brand-limited key.
Does this work with AEM as a Cloud Service only?
The setup uses the Cloud Service config pipeline and its CDN log forwarding, so that is the supported route. Other CDNs in front of AEM have their own pages.
How do I disconnect?
Remove the forwarding rule from the config pipeline and redeploy. Logs stop, and you can delete the key in Proofsource. Past counts stay unless you ask us to remove them.
Can Proofsource change my AEM site?
No. Logs are pushed out and Proofsource only receives them.
How does this help my AI visibility?
On a large site it is easy to lose whole sections to a rule nobody remembers. Counts per section show what the engines reach, and Proofsource then checks whether they 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 Adobe Experience Manager
Put Adobe Experience Manager to work for your AI visibility.
Scan your brand, connect Adobe Experience Manager, and see what AI says about you on up to 10 engines.
