Analytics without the bots

Five detection layers filter crawlers, scrapers, headless browsers, and AI agents before they pollute your data. And unlike silent filters, Rybbit shows you everything it blocked.

Bot Detection

A meaningful share of your traffic isn't human: search crawlers, uptime monitors, scrapers, link previewers, and a fast-growing wave of AI agents. Left in your data, they inflate visitor counts, distort bounce rates, and quietly wreck conversion metrics. Rybbit checks every tracking request against five detection layers before it ever reaches your analytics.

Most analytics tools filter bots silently against a user-agent list, so you never know what was removed, or what slipped through. Rybbit stores a compact record of every filtered request and gives you a dedicated Bots report: total blocked requests, bot share of traffic, which detection layers matched, and breakdowns by page, referrer, country, device, and user-agent.

Filtered bots are excluded from dashboards, funnels, journeys, and session lists, and they never count toward your bill. One toggle per site, no changes to your tracking script.

Capabilities

What you can do

User-agent & AI crawler patterns

Catches search engine crawlers, headless browsers, SEO and monitoring tools, script and framework HTTP clients, and the growing wave of AI crawlers and agents.

Browser fingerprint checks

Header heuristics and client-side signals expose bots that fake a browser user-agent: missing browser headers, automation APIs, impossible window dimensions, empty plugin lists, and headless renderers.

ASN & network intelligence

Curated ASNs of known AI, scanner, and measurement providers trigger detection directly. Generic hosting ASNs only count as supporting evidence, so visitors on VPNs, corporate gateways, and CDNs aren't falsely flagged.

Rate & anomaly detection

Rolling windows catch crawl-shaped behavior: bursts from one IP, rapid path fan-out, rotating user-agents, and replayed tracking requests that pass every other check.

A dedicated Bots report

See everything that was filtered: total blocked requests, bot share of traffic, trends over time, and breakdowns by page, referrer, country, device, and user-agent, with the exact detection layers that matched.

Bots are never billed

Detected bot visits don't count toward your usage. You're not paying for GPTBot to crawl your docs or a scraper to hammer your product pages.

Getting Started

How it works

1. Enable Block Bot Traffic
   Flip one toggle in Site Settings. Bot detection is configured per site, and there's nothing to change in your tracking script.

2. Every request runs all five layers
   User-agent patterns, header heuristics, client signals, ASN checks, and rate anomaly detection all run on every incoming tracking request. Rybbit records every layer that matched, then makes one final decision.

3. Bot traffic is filtered, not lost
   Detected bots never touch your normal analytics. Dashboards, funnels, journeys, and session lists stay human-only, and a compact bot event record is stored separately so nothing disappears silently.

4. Inspect the Bots report
   Open the Bots page in your dashboard to audit what was blocked and why. Server-side events sent with an API key are treated as trusted and bypass detection entirely.

Use Cases

Marketing teams

Bounce rate, conversion rate, and campaign ROI all break when bots inflate the denominator. Clean traffic means decisions based on humans.

E-commerce stores

Price scrapers and inventory bots hit product pages constantly. Filter them out so product analytics reflect real shoppers.

Content & docs sites

AI crawlers now rival search engines in crawl volume. See exactly which bots are reading your content, without them polluting your stats.

Startups & SaaS

Launch-day traffic spikes bring uptime monitors, link previewers, and scrapers along. Know how much of that spike was real.

Agencies

Client reports lose credibility when numbers include bots. Show clients human traffic, and use the Bots report to explain the difference.

SEO teams

Separate crawler activity from organic visitors, and verify which crawlers actually visit your site and how often.

FAQ

How is this different from the bot filtering other analytics tools do?

Do blocked bots count toward my bill?

Will real visitors get blocked by mistake?

Does it catch AI crawlers and agents?

Does bot detection affect server-side tracking?

Does it work behind a proxy or CDN?

Stop counting bots as visitors

Five-layer detection, full visibility into what was filtered, and a bill that only counts humans.