Track every AI crawler.Change one DNS record.
xSeek CDN Proxy sits between AI bots and your origin server. It detects 50+ crawlers at the edge, logs every visit, and forwards traffic untouched. No code changes. No middleware. One CNAME.
Most Tracking Tools Require You to Ship Code
Middleware. Edge functions. Server configs. Every integration is a deployment risk, a maintenance burden, and a reason for engineering to say "not this sprint."
The Old Way
- ✗
Write middleware or edge functions
Custom code in your stack. New dependency. New failure mode.
- ✗
Deploy and maintain it
Every update to bot patterns means redeploying your application.
- ✗
Coordinate with engineering
Marketing needs data. Engineering has a backlog. Weeks pass.
- ✗
Risk production stability
Any bug in tracking code could slow down or break your site.
xSeek CDN Proxy
One DNS change. Done.
Point your domain to our proxy via CNAME. No code. No deploy.
Auto-updated bot patterns
New crawlers added automatically. You never touch your infrastructure.
Marketing owns it
Enable from the xSeek dashboard. No engineering ticket required.
Zero risk to your site
Tracking is async. If our proxy goes down, your origin is untouched.
Three Steps. Five Minutes. Complete AI Visibility.
No SDK. No build step. No engineering sprint. Just DNS.
Enable in Dashboard
Enter your origin URL and custom domain. xSeek provisions a dedicated Cloudflare Worker and generates your CNAME target.
Update Your DNS
Add a CNAME record pointing your domain to cdn-[id].xseekproxy.com. Takes 30 seconds in any DNS provider.
Data Flows Automatically
Every AI crawler is detected at the edge and logged in your xSeek dashboard. Your visitors see zero difference.
How Traffic Flows
Visitor / AI Bot
Requests your site
xSeek CDN Proxy
Detects bots, logs visits
Your Origin
Unchanged. Untouched.
Visitors and bots see your normal content at full speed.
Edge Detection. Zero Latency Impact.
Each customer gets a dedicated Cloudflare Worker. Bot patterns are hardcoded — no database lookups, no external API calls during detection.
Dedicated Worker Per Site
Your proxy runs in isolation. No shared infrastructure with other customers. Your own Cloudflare Worker, your own secrets.
50+ Bot Patterns
GPTBot, ClaudeBot, PerplexityBot, Gemini, DeepSeek, Grok, and 40+ more. Regex-based detection runs in microseconds.
Async Tracking
Bot detection fires after the response. Uses Cloudflare's waitUntil() — the visitor never waits for tracking to complete.
Custom Domain + SSL
Use your own domain. SSL is provisioned automatically via Cloudflare. Visitors see your domain, not ours.
Transparent Forwarding
All headers preserved. X-Forwarded-For, X-Real-IP, protocol info — your origin sees the real client. Nothing is stripped.
Markdown for Agents
Powered by Cloudflare. AI crawlers requesting text/markdown get clean markdown instead of raw HTML — 80% fewer tokens, better AI comprehension.
One-Click Enable/Disable
Toggle the proxy on or off from your dashboard. Disabling cleans up all Cloudflare resources automatically.
Markdown for Agents. Built In.
Feeding raw HTML to an AI is like paying by the word to read packaging instead of the letter inside. xSeek CDN Proxy leverages Cloudflare's Markdown for Agents to serve clean, structured markdown to AI crawlers automatically.
Why Markdown Matters for AI
80% Fewer Tokens
A typical blog post uses 16,180 tokens in HTML. The same content in markdown: 3,150 tokens. Less noise, more signal.
Better AI Comprehension
No div wrappers, nav bars, or script tags. AI agents see your actual content — headings, paragraphs, lists — clean and structured.
Content Negotiation
When an AI crawler sends Accept: text/markdown, Cloudflare converts HTML to markdown on the fly. Human visitors see your normal site.
Content Signals Included
Responses include Content-Signal headers so you control how your content is used for AI training, search, and agentic use.
How It Works
# AI agent requests markdown
curl https://your-site.com/pricing \
-H "Accept: text/markdown"
# Response headers
content-type: text/markdown; charset=utf-8
x-markdown-tokens: 725
content-signal: ai-train=yes, search=yes
# Clean markdown output
## Pricing
Plans for every team ready to
win AI search...
CDN Proxy vs. Custom Integration
Both get you AI bot tracking. One doesn't require an engineer.
| Criteria | Custom Integration | xSeek CDN Proxy |
|---|---|---|
| Setup Time | Hours to days | 5 minutes |
| Code Changes | Required | None |
| Engineering Dependency | High | None |
| Bot Pattern Updates | Manual redeploy | Automatic |
| Latency Impact | Depends on implementation | Zero (async) |
| Works With Any Stack | No — stack-specific | Yes — any origin |
| Production Risk | Your code, your risk | Isolated at the edge |
Built For Teams That Ship Fast
Marketing Teams
You need AI crawler data yesterday. Engineering has a 3-week backlog. CDN Proxy lets you own the setup without writing a single line of code.
Enable it yourself. No ticket.
Agencies
Managing 10 client sites? Enable CDN Proxy per site from the dashboard. Each client gets their own isolated worker. Scale without complexity.
One dashboard. Every client.
Platform Teams
Legacy stack? WordPress? Custom CMS? It doesn't matter. CDN Proxy works with any origin that serves HTTP. No plugins required.
Any origin. Any stack.
One DNS record. Complete AI visibility.
Stop waiting on engineering. Enable CDN Proxy, point your CNAME, and start seeing every AI bot that touches your site.
Included in all plans • 5-minute setup • No code required