xseek Logo
Guides
February 21, 2026•8 min read

Edgely + xSeek: No‑Code AI Bot Tracking (3‑Minute Setup)

If your site is behind a CDN and your “traffic” comes from bots that never execute JavaScript, client-side analytics will lie to you. Edgely + xSeek fixes that by tracking AI crawlers at the proxy layer.

Marc-Olivier Bouchard

Marc-Olivier Bouchard

AEO Strategy Consultant

Edgely + xSeek: No‑Code AI Bot Tracking (3‑Minute Setup)

The problem: AI crawlers don’t run your analytics

GPTBot, Claude-Web, PerplexityBot, and friends fetch your pages like a script: request HTML, parse, move on.

No browser. No JavaScript. No GA4 pageview. So you end up making decisions with a blind spot: you can’t see which URLs AI engines are reading, how often they come back, or when a change breaks crawlability.

The fix: measure at the edge

Edgely sits in front of your origin as a reverse proxy. That means it sees every HTTP request before your site platform does.

When you connect xSeek inside Edgely, Edgely detects AI crawlers on inbound requests and posts those visits to xSeek automatically. No script tags. No middleware. No deploy.

What you get in xSeek

  • AI bot visits by URL (which pages are being fetched)
  • Bot identification (User-Agent based)
  • Trends over time (did crawl frequency spike or drop?)
  • A clean baseline for AEO work: fix what crawlers actually read

3‑minute setup (no code)

  1. Proxy your domain through Edgely. In Edgely, add your custom domain and set your origin (your current site URL). Then update DNS so requests flow through Edgely.
  2. Copy your xSeek Website ID. In xSeek, open your website settings and copy the Website ID you want Edgely to send events to.
  3. Create an xSeek API key with the right permission. Generate an API key that includes ai_visits:push.
  4. Connect xSeek in Edgely. In Edgely, open Integrations → xSeek, paste the API key + Website ID, and save.

Verification checklist

Two quick checks to confirm the pipeline is working.

  1. Confirm traffic is actually flowing through Edgely. Load your site and verify it’s being served via the proxy (your domain should resolve to Edgely, not directly to the origin).
  2. Send a test request that looks like an AI crawler. From your terminal, run:
curl -I https://YOUR_DOMAIN_HERE \
  -A "GPTBot"

Then open xSeek → AI bot visits and confirm the visit shows up for the correct URL.

Troubleshooting (the 3 common misses)

1) “I see nothing in xSeek”

  • Make sure the domain is proxied in Edgely (DNS points to Edgely, not your origin).
  • Confirm you pasted the correct xSeek Website ID.
  • Regenerate the API key and ensure it includes ai_visits:push.

2) “I only see some URLs”

That’s usually a routing or caching mismatch. Start by checking whether the missing URLs are served by the same domain and path rules in Edgely as the URLs that do show up.

3) “Will this slow down my site?”

Edgely is already in the request path when you proxy your domain. The xSeek integration piggybacks on that same edge request flow and doesn’t require client-side scripts.

Where to go next