Connect xSeek to what you already use.
Some connections take one sign-in from your marketing team. Others go into your site's code, so a developer installs them. Both are below, in that order.
Connect it yourself. No developer needed.
Each of these is a sign-in, a few fields or a plugin upload. If you can run your CMS, you can do these.
Google Search Console + GA4
Sign in with Google once, read-only. xSeek reads your Search Console clicks and impressions per page, and the GA4 visits that come from ChatGPT, Perplexity and other AI assistants.
See AI traffic
Publish to your CMS
Send articles from Content Studio to WordPress, Webflow, Ghost or HubSpot. They arrive as drafts unless you switch a connection to publish live. HubSpot always gets a draft.
See Content StudioWordPress bot tracking plugin
Upload the xSeek plugin in WordPress, paste your API key and website ID, send a test event. From then on, every AI crawler visit is logged server-side.
Plugin guide
ChatGPT, Claude or Cursor
Add the xSeek MCP server to your assistant and set up your account from the chat: brand, competitors, audiences and the questions to track.
Connect your assistantTrack AI crawlers on your site's stack.
AI crawlers rarely run JavaScript, so a browser tag never sees them. These installs log each visit on your server or at the CDN edge. Hand this part to whoever deploys your site.
Pick your stack
8 platforms
Next.js
nextjs.orgAdd the xSeek middleware to your Next.js app. It spots AI crawlers on the server and logs each visit, without touching your routes.
Lovable
lovable.devGive Lovable two prompts: one adds AI crawler tracking to server.ts, the other adds a /blogs section that pulls your xSeek articles.
Cloudflare
cloudflare.comA Cloudflare Worker spots AI crawlers at the edge, logs each visit to xSeek and passes the request on to your site unchanged.
Amazon CloudFront
aws.amazon.comA Lambda@Edge function logs AI crawler visits at CloudFront's edge, then passes every request on to your origin.
Custom API
xseek.ioCall the xSeek tracking endpoint from your own server or proxy. Works on any stack that can send an HTTP request.
Fastly
fastly.comNot available yet: there is no Fastly Compute snippet. Until there is, call the xSeek API from your own Fastly service, or track at Cloudflare or CloudFront.
Imperva
imperva.comNot available yet: there is no Imperva rule to copy. Until there is, call the xSeek API from your server, or track at Cloudflare or CloudFront.
Akamai
akamai.comNot available yet: there is no Akamai EdgeWorker snippet. Until there is, call the xSeek API from your server, or track at Cloudflare or CloudFront.
Build a custom integration.
Our API works with any server, edge, or proxy layer. If you can make an HTTP request, you can track AI bots. Founder-level support included.
Server, edge, or proxy?
Each layer has tradeoffs. Compare them on what they see, the latency they add and the time they take to set up.
| Method | Layer | Sees JS-less bots | Latency added | Setup |
|---|---|---|---|---|
| Server-side plugin | Origin | Yes | ~0 ms | 2–5 min |
| Edge worker | CDN edge | Yes | <5 ms | 4–12 min |
| Reverse proxy | Between user & origin | Yes | <10 ms | 2 min |
| Custom API | Anywhere | Yes | Depends | 15 min |
| Client JS (not used) | Browser | No | n/a | n/a |
Start tracking AI bots in under five minutes.
Pick your stack, follow the guide, watch the data land. No credit card, no call required to start.