Clerion
  • Explore ClerionFeaturesUse casesMCP server
    Feature pagesAI trafficRevenue by sourceCustom eventsError intelligenceBriefing and signalsSecurity
  • Docs
  • Pricing
  • Privacy-first toolsPlausibleFathomMatomo
    Large platformsGoogle AnalyticsMixpanelCloudflare Web AnalyticsPostHogAmplitude
  • LearnBlogHelp centreChangelog
    CompanyAbout usBrandContact
Sign inStart free trial ›
  • Explore ClerionFeaturesUse casesMCP server
    Feature pagesAI trafficRevenue by sourceCustom eventsError intelligenceBriefing and signalsSecurity
  • Docs
  • Pricing
  • Privacy-first toolsPlausibleFathomMatomo
    Large platformsGoogle AnalyticsMixpanelCloudflare Web AnalyticsPostHogAmplitude
  • LearnBlogHelp centreChangelog
    CompanyAbout usBrandContact
  • Contact sales
Sign inStart 14-day trial

On this page

  • What changed
  • What it catches
  • What it doesn't do yet
  • Why the problem keeps getting bigger
  • How this compares to what you have now
  • Why it matters
  • Related reading
  • Frequently asked questions
  • Sources
  1. Blog
  2. Bot filtering: analytics that count only humans
  1. Blog
  2. Bot filtering: analytics that count only humans

Bot filtering: analytics that count only humans

Clerion Research Team3 July 2026Updated 3 October 20264 min read

Bot filtering analytics keeps crawlers, SEO scanners and scripts out of your visitor counts, sessions and funnels, so your numbers count only humans. Clerion now does this automatically for self-identified bots and shows how many requests it filtered, with no setup needed.

Cover image for Clerion's bot filtering feature release

A good chunk of the traffic hitting most sites was never human. Search crawlers, SEO scanners, link checkers, and scripts all show up in raw logs, and when they slip into your analytics they quietly inflate everything downstream. Your visitor count looks healthier than it is. Your conversion rate looks worse than it is. Every decision you make on top of those numbers inherits the error.

Starting today, Clerion filters that traffic out for you. The numbers you see are people.

What changed

Clerion now recognizes bots and crawlers as they arrive and keeps them out of your visitor counts, sessions, funnels, and engagement metrics. Nothing gets deleted and nothing gets hidden. Bot traffic just gets held apart from the human traffic your reports are meant to describe.

You'll also see a small badge at the top of your dashboard showing how many bot requests were filtered. You should be able to see the work happening on your behalf, not just trust that it happened.

What it catches

This release focuses on the traffic that most reliably distorts a dashboard: visitors that identify themselves as automated.

  • Search engine crawlers like Googlebot, Bingbot, and DuckDuckBot
  • SEO and monitoring tools like AhrefsBot and SemrushBot
  • Platform crawlers like Applebot and the Facebook link fetcher
  • Common scripting tools like curl, wget, and headless browsers

Together these account for most of the non-human traffic on a typical site, and they're the ones most likely to skew a small or growing audience.

What it doesn't do yet

We'd rather be precise than impressive. This first release identifies bots by how they present themselves, which means a scraper deliberately disguised as a real browser can still get through. Catching that kind of traffic takes behavioral signals, and that work is underway. For now, you get clean numbers against the bots that make up most of the problem, and honest limits on the rest.

Why the problem keeps getting bigger

This isn't a niche issue anymore. Imperva's 2025 Bad Bot Report found automated traffic made up 51% of all web traffic in 2024, the first time in a decade it passed human activity. Much of the growth comes from AI crawlers and agents that didn't exist a few years ago.

For a small site, that matters more than for a big one. A few hundred crawler hits barely register on a site with a million visits. On a site with two thousand, they can be the difference between a good week and a bad one.

How this compares to what you have now

Some tools already filter part of this. GA4, for example, excludes traffic from known bots and spiders using Google's own research and an industry list maintained by the IAB. But you can't turn that off, and you can't see how much it removed. The traffic that's left isn't a verified count of people, it's just what wasn't on the list.

That's the gap we wanted to close: not only filtering, but showing you the filtered count, so you know how much of your raw traffic was never human. If that number is large, it's worth knowing before you read anything else on the dashboard.

Why it matters

Clean traffic isn't a vanity metric. It's the difference between a conversion rate you can act on and one that quietly lies to you. When the denominator is right, everything built on it gets more trustworthy: your funnels, your channel comparisons, your sense of whether last week's change actually worked.

Nothing to turn on. It's already running on your account. Open your dashboard and the numbers you see are the ones that were always supposed to be there.

Related reading

  • Bot traffic: the non-human half of the web: how big the bot problem really is.
  • Understanding website visitors beyond pageviews: understanding the humans who remain.
  • Privacy-first web analytics, on by default: analytics with no cookies and no banner.

Frequently asked questions

What is bot filtering in analytics?

Bot filtering separates automated traffic, such as search crawlers, SEO tools and scripts, from human visits so metrics like visitors, sessions and conversion rate describe real people.

Which bots does Clerion filter?

Self-identified bots: search engine crawlers like Googlebot and Bingbot, SEO tools like AhrefsBot and SemrushBot, platform crawlers like Applebot, and scripting tools such as curl, wget and headless browsers.

Does Clerion catch every bot?

Not yet. Scrapers disguised as real browsers can still get through. Catching them requires behavioral signals, which Clerion is working on.

Is filtered bot traffic deleted?

No. Bot traffic is held apart from human traffic, not deleted, and a badge on the dashboard shows how many bot requests were filtered.

Do I need to turn bot filtering on?

No. Bot filtering is on by default for every Clerion account.

Sources

  • 2025 Imperva Bad Bot Report: How AI is Supercharging the Bot Threat
  • How to identify bot traffic in Google Analytics (Centinel)
  • Filtering out known-bot traffic (Mediavine Help)
feature releasebot filtering analyticsbot trafficweb analytics
Clerion

Website intelligence for AI founders.See what AI sends you, and what to fix.

Start free trial ›

14 days free, no card.

Keep reading

All writing →
  • How to add Clerion to your site: paste this one lineArticle
  • How to track Perplexity traffic to your website (2026)Article
  • Is ChatGPT sending me traffic? How to check in 5 minutesArticle
  • Clerion vs Google AnalyticsPage
  • Do you need a cookie banner for analytics?Guide
  • Best AI analytics toolsGuide
Next step

See your numbers with the bots taken out.

Written from real site data by the team building Clerion.
Count people, not bots ›
Clerion

Website intelligence for AI founders.

Product

  • Features
  • Use cases
  • Docs
  • Quickstart
  • MCP server
  • Pricing
  • Sign in

Compare

  • vs Google Analytics
  • vs Plausible
  • vs Fathom
  • vs Matomo
  • vs Mixpanel
  • vs Cloudflare
  • vs PostHog
  • vs Amplitude

Resources

  • Blog
  • Help centre
  • Is it agentic?
  • What is SI?
  • What is Clerion?
  • Changelog
  • Sitemap

Company

  • About us
  • CareersHiring
  • Brand
  • Contact
  • Security
  • Privacy policy
  • Terms

Compliance

  • GDPR
  • Schrems II
  • ePrivacy
  • PECR
  • COPPA
  • CCPA
  • Our data journey
Product
  • Features
  • Use cases
  • Docs
  • Quickstart
  • MCP server
  • Pricing
  • Sign in
Compare
  • vs Google Analytics
  • vs Plausible
  • vs Fathom
  • vs Matomo
  • vs Mixpanel
  • vs Cloudflare
  • vs PostHog
  • vs Amplitude
Resources
  • Blog
  • Help centre
  • Is it agentic?
  • What is SI?
  • What is Clerion?
  • Changelog
  • Sitemap
Company
  • About us
  • CareersHiring
  • Brand
  • Contact
  • Security
  • Privacy policy
  • Terms
Compliance
  • GDPR
  • Schrems II
  • ePrivacy
  • PECR
  • COPPA
  • CCPA
  • Our data journey

Clerion (“Clerion”), at getclerion.com and clerion.si, is website intelligence for AI founders: web analytics, AI-assistant traffic, conversions and revenue by source, SEO and AI-readiness, speed and errors from one script tag. It finds the patterns in the data, ranks what changed and tells you the fix. Designed with taste: one typeface, no accent colour, and nothing that moves unless it tells you something. AI is now also called SI, super intelligence; the channel is the same. It sets no cookies, stores no personal data, needs no consent banner, and holds data in the EU. Every briefing is written from your own numbers, and every figure in it comes from your data rather than from the model. Clerion is a software product and does not provide marketing, legal or advisory services. We have no ad budget: if Clerion helps you, telling a friend does more for us than any campaign could.

© 2026 Clerion. Independent and self-funded.

Served from the Netherlands.