Bot filter
Your numbers are humans only.
Crawlers, scrapers, headless browsers, and AI bots flagged the moment they arrive. Excluded from your metrics, but never hidden from you.
of raw traffic was bots, flagged and excluded
What you get
Flagged on arrival
Bots are classified as the traffic lands, not cleaned up later. Your live view is human from the start.
Network-level signals
Datacenter IP ranges and hosting ASNs betray bots that fake a perfect browser user-agent.
Headless browser detection
Puppeteer and friends get caught by browser-environment signals, not just user-agent strings.
Named AI crawlers
GPTBot, ClaudeBot, and other AI crawlers identified by name. See exactly who's reading your site.
Excluded, not deleted
Bot traffic stays inspectable in its own view. Filtered out of your metrics, available when you're curious.
Zero configuration
No filter rules to maintain, no IP lists to update. Classification ships with the platform.
How much of your traffic isn't human?
Somewhere between a fifth and half of typical website traffic is automated: search crawlers, scrapers, uptime monitors, headless test runners, and increasingly, AI crawlers harvesting content. If your analytics counts them as visitors, every number downstream is wrong. Traffic inflates, conversion rates deflate, and phantom spikes send you hunting for causes that don't exist.
OakData classifies traffic as it arrives, combining user-agent analysis, datacenter IP ranges, hosting-provider ASNs, and browser-environment signals. A bot that fakes a perfect Chrome user-agent still gets caught by the network it came from.
See the bots without counting them
Filtering isn't the same as deleting. Bot sessions remain visible in their own classified view, whether it's GPTBot crawling your docs or a scraper hammering your pricing page. You can answer "who's scraping us?" while your dashboards stay clean. As AI crawlers become a bigger share of the web, knowing which ones read your site is data worth having.
Questions
Through layered signals: known crawler user-agents, datacenter IP ranges, hosting-provider ASNs, and browser-environment checks that catch headless browsers. A bot that spoofs its user-agent is still caught by the network it operates from.
No. They're classified and excluded from your human metrics, but remain inspectable in their own view. You can always see what automated traffic is doing on your site.
Yes. Known AI crawlers are identified by name, so you can see exactly which AI companies are reading your content and how often.
No. Classification is built into the platform and updated on our side. There are no rules to configure or lists to keep current.
Related
Try it
Bot detection is five minutes away.
One snippet, every feature, at every tier. Free for the first 14 days.
14-day free trial