Connecting my Vercel-hosted site to crawler tracking keeps failing. What's going on?
Updated June 30, 2026 · Reviewed by [email protected]
Vercel-hosted sites connect through Vercel's edge middleware rather than a plugin, so the most common failure is the middleware deployment itself: either it didn't deploy to all the regions your traffic hits, or a more specific middleware/route rule on your site is intercepting requests before Trakkr's code runs.
Double-check the integration was added to the correct Vercel project and environment (production, not just preview), and that no other middleware in your project short-circuits before it. If your site also sits behind Cloudflare in front of Vercel, the Cloudflare-vs-origin setup matters too: see the Cloudflare setup guide for how the two interact.
Related questions
- Can I install crawler tracking on a site that isn't Cloudflare, Vercel, Netlify, or WordPress (like Wix, Framer, or a custom PHP site)?
- Crawler tracking shows visits from some AI bots (like Meta or Mistral) but not others (like ChatGPT or Perplexity), even though I know those engines have visited. Is tracking broken?
- I'm getting "We could not reach the WordPress crawler plugin endpoints" when connecting WordPress. How do I fix it?
- Cloudflare says it denied analytics access when I try to connect my site to Trakkr. What permissions does the token need?
- I got a robots.txt or crawler-blocking alert from Trakkr that I think is wrong. How do I check it myself?