Proofsource and Vercel: see which AI crawlers really visit
Add a log drain in your Vercel project and Proofsource counts every verified visit from GPTBot, ClaudeBot, PerplexityBot and the other AI crawlers, page by page. You find out which pages the engines read, which they skip, and whether a fix you shipped was picked up, without installing anything in your code.
| Crawler | Visits | Top page |
|---|---|---|
| GPTBot | 512 | /pricing |
| ClaudeBot | 301 | /blog/meeting-notes-guide |
| PerplexityBot | 274 | /vs/otter |
| Google-Extended | 197 | / |
Proofsource and Vercel, in short
The facts, ready to quote.
- Stage
- Live on every plan, with a guided setup in the app
- Connects with
- A log drain from the Vercel project to a Proofsource endpoint; Vercel signs each delivery
- Access it needs
- None to your code or account: Vercel pushes request logs, Proofsource only receives them
- Where it shows
- Integrations, Crawler sources, and AI traffic
- Bot check
- Every visit is checked against published IP ranges and reverse DNS
- Disconnect
- Delete the drain in your Vercel project and deliveries stop immediately
Why we love Vercel
In the makers' own words, from their own pages. Proofsource builds on it, never around it.
A preview for every change
Every branch and pull request on Vercel gets its own live preview URL, so teams can look at a change in a real environment before it goes live.
From vercel.comDrains send your data anywhere
Vercel Drains forward logs, traces and analytics to the endpoint or tool you choose, which makes your own traffic data easy to put to work elsewhere.
From vercel.comA global edge built in
Vercel serves your site from its own content delivery network, so pages load quickly for visitors and crawlers wherever they are.
From vercel.comHow Proofsource uses Vercel
Takes your Vercel request logs over a log drain and counts verified AI crawler visits page by page.
- Connect
Point a log drain at Proofsource
A guided card in the app shows the endpoint and the steps. Vercel starts sending request logs for the project you choose.
- Read
Spot the AI crawlers
Each log line is matched to a known AI crawler and checked against its published IP ranges and reverse DNS, so a fake GPTBot visit does not count.
- Show
See visits per page
The Crawler sources tab and AI traffic show which pages each crawler read, how often, and what status code it got back.
- Prove
Tie visits to your fixes
When a fix page goes live, Proofsource shows whether the crawlers came back to read it, then checks whether the engines now name you.
Set up Vercel in 4 steps
Open Integrations, Crawler sources
Choose Vercel to open the guided log-drain setup. It shows the endpoint address to copy.
Create the drain in Vercel
In the Vercel project, add a drain that sends request logs to that endpoint. Log drains need a Vercel plan that includes them.
Wait for the first visits
Proofsource shows the drain as receiving as soon as the first signed delivery arrives, then starts counting verified crawler visits.
Remove it any time
Delete the drain in Vercel and deliveries stop at once. Nothing was installed in your project.
Endpoint https://api.proofsource.co/v1/crawler-logs/vercel Signed by Vercel on every delivery
What you unlock with Vercel
Verified crawler counts
Real visits from GPTBot, ClaudeBot, PerplexityBot and more, with fakes removed.
Per-page reads
Which pages the engines read and which they never reach.
Fix pickup
See whether crawlers came back after you shipped a page.
Blocked-by-mistake alerts
Spot a 403 or 429 aimed at an AI crawler before it costs you answers.
AI traffic view
Crawler visits next to AI referral traffic in one place.
Read-only receiving
Vercel pushes logs; Proofsource never gets access to your project.
Google AI OverviewsGoogle AI Mode
Questions about Proofsource and Vercel
What does Proofsource read from my Vercel site?
Only request log lines that Vercel sends to the drain: the time, the visitor's address and user agent, the path, host, status code and referrer. Proofsource keeps the AI crawler visits and drops the rest. It cannot read your code, settings or deployments.
How do I connect Vercel?
Open Integrations, then Crawler sources, and choose Vercel. The guided card shows an endpoint to paste into a new log drain in your Vercel project. Vercel signs each delivery, so Proofsource knows the logs are really yours.
Why do I need this when I have analytics?
Browser analytics only count visitors who run scripts, and AI crawlers do not. Server logs are the only place their visits appear, so they show which pages the engines can actually read.
Can Proofsource change my Vercel site?
No. The log drain is receive-only, so nothing on Vercel is changed by Proofsource.
How do I disconnect?
Delete the drain in your Vercel project. Deliveries stop immediately and the card shows no new logs. Past counts stay in your history unless you ask us to remove them.
How does this help my AI visibility?
If a crawler cannot reach a page, the engine cannot cite it. Crawler counts show which pages are read and which are missed, so fixes go where they matter, and 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 Vercel
Put Vercel to work for your AI visibility.
Scan your brand, connect Vercel, and see what AI says about you on up to 10 engines.
Google AI OverviewsGoogle AI Mode