Send AI crawler visits from Vercel

If your site is hosted on Vercel, a Log Drain can send your request logs to your project by itself. Nothing is installed on the site. The visits show on the AI crawlers page.

Only AI crawler requests are kept. Requests from people and from other bots are dropped when they arrive, and so are build and function log lines. No IP address, no user agent, no query string and no referrer is stored.

What you need

• A Vercel team on a plan that has Drains. Vercel's page says Drains are available on Pro and Enterprise. Check your plan and any usage charges with Vercel.
• A workspace Admin to make the token in Settings.
• A Vercel team owner or admin to add the drain.

Set it up

1. Open Settings, find Vercel log connection and choose Generate token. Copy the token and the Endpoint URL. The token is shown once.
2. In Vercel, go to your team's drain page and choose to add a drain.
3. Choose Logs as the data type. Give the drain a name and pick the projects that serve your site.
4. Under the log sources, tick static, edge and lambda. The other sources are build output and redirects, which are not page visits. Under environments choose production.
5. Leave sampling off, or set it to 100%. A lower rate means some AI crawler visits are never sent.
6. For the destination choose Custom Endpoint, then fill in:

• Endpoint URL: the address from Settings.
• Format: JSON or NDJSON. Both are read.
• Custom Headers: one line, X-KlientBrain-Vercel-Token: followed by your token.
• Signature Verification Secret: leave it as it is. We check the token, not the signature.

7. Create the drain. Vercel tests the endpoint when it is created, and we answer it once the token is right. Visits appear on the AI crawlers page within a few minutes. Last batch received in Settings shows the newest.

Instead of the custom header you can send Authorization: Bearer followed by the token.

Vercel can hide visitor IP addresses in drains (in the team's security settings). We never read them either way.

If nothing shows

• Creating the drain fails the test: the token is wrong or was replaced, or the Vercel log connection is not switched on for your workspace yet. Generate a new token in Settings and update the header.
• The drain shows an error in Vercel: the same. Vercel flags a drain whose deliveries mostly fail.
• No visits at all: check the drain is active, that it covers the Vercel project that serves your site, and that static, edge and lambda are ticked.
• Visits missing for one host: only requests for your project's own website are kept. A visit to a vercel.app address is left out unless that is your project's website. Check the website in Settings.
• Counts seem low: only visits from the AI crawlers we list are counted. Rows left out so far in Settings says how many were not.