Skip to main content
AI assistants don’t just answer from training data — they crawl the live web. The bot tracker tells you which AI bots are reading your site, how often, and which pages they touch. The data feeds the Analytics → Bot Traffic dashboard.

Why a separate tracker?

The JavaScript analytics pixel only fires when a real browser executes JS. Most AI crawlers fetch raw HTML and never run scripts, so they’re invisible to client-side tracking. The bot tracker runs server-side (or via the WordPress plugin) and inspects the User-Agent of every request.

Bots detected

The list is updated continuously as new agents appear.

Enable it

1

Open the website settings

In the Keupera dashboard open Settings → Website.
2

Toggle 'Enable Bot Tracking' on

Flip the switch. Keupera now accepts bot events for this website.

Install the collector

Pick whichever option matches your stack.
Detect known bot UAs in your edge layer (Cloudflare Workers, Vercel Middleware, Nginx, Express, etc.) and POST to /api/v1/track-bot with one or more events:
Batch up to 50 events per call. The endpoint is idempotent on (bot_name, path, visit_date) — duplicates increment the visit counter rather than creating new rows.

Read the data

Bot data is exposed both in the dashboard and via the API: See the full schemas in the Analytics API reference.