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

  • Why this matters
  • Same data, two very different sentences
  • The hidden tax of vanity metrics
  • The four-question test
  • Put it to work
  • The takeaway
  • Related reading
  • Frequently asked questions
  • Sources
  1. Blog
  2. How much of my website traffic is bots? (2026)
  1. Blog
  2. How much of my website traffic is bots? (2026)

How much of my website traffic is bots? (2026)

Clerion Research Team6 July 2026Updated 4 October 20265 min read

Probably about half. Imperva's 2026 Bad Bot Report, published May 2026, puts bots at over 53% of all web traffic. Website bot traffic quietly inflates the sessions, bounce rates and drop-offs on most dashboards, so filter it out before you judge any metric.

Photo used as the cover for a post on website bot traffic

Probably more than half of it. Imperva's 2026 Bad Bot Report, published in May 2026, found bots now account for over 53% of all web traffic. Unless your analytics filters them out, that website bot traffic sits inside every session count, bounce rate and drop-off you read.

Bots, crawlers, and scrapers are baked into every number on your dashboard. So that "bounce rate: 42%" isn't just unhelpful, it isn't even clean. Your analytics tool hands you a polluted fact and calls it insight.

Why this matters

If you run a small business or an early-stage product, your dashboard is full of numbers like this. Bounce rates. Drop-off percentages. Session durations. All of them inflated by traffic that will never buy anything, and none of them naming a cause.

You still have to do the diagnosis yourself. That's fine if you have a data team. Most founders don't. They have a product to build, customers to talk to, and about twenty minutes a week for analytics. Every number that needs interpreting is a number that gets ignored, and the problem underneath it keeps costing money.

Same data, two very different sentences

Here's identical underlying data, presented two ways.

Vanity metric: "Bounce rate: 42%. Checkout funnel drop-off, step 3: 14%."

Actionable insight: "Your checkout page takes 4 seconds to load on Safari. That's costing you sales this week."

Both come from the same numbers. Only one tells you what to do before your next coffee.

The first version is technically correct and useless on its own. It describes a symptom. You still have to dig through load times, browser breakdowns, and device segments to find out why the number looks that way, and by then half your afternoon is gone.

The second version skips straight to the diagnosis. Slow page, specific browser, real cost. You don't interpret it. You act on it.

The hidden tax of vanity metrics

A metric without a cause attached doesn't sit there harmlessly. It creates work. Someone has to notice it, question it, cross-reference it against three other metrics, and eventually guess at what's wrong.

That process is called analysis. It's a real skill and it takes real time. Time most small teams don't have.

So the vanity metric doesn't just fail to help. It taxes you every time you look at it, whether or not you ever solve the mystery underneath it.

The businesses that move fast aren't the ones with the most dashboards. They're the ones with the shortest distance between "something's wrong" and "here's the fix."

The four-question test

A metric is actionable when it passes all four:

  1. Does it name a cause, or just a symptom? "Conversion dropped" is a symptom. "Conversion dropped because your form now requires a phone number" is a cause.
  2. Could you act on it in the next five minutes? If the honest answer is "I'd need to investigate first," it's not an insight. It's a lead.
  3. Does it say what it's costing you? A percentage without a dollar amount or user count attached rarely triggers urgency, however alarming it looks.
  4. Would a non-technical teammate know what to do after reading it? If it needs translation, it hasn't done its job.

Put it to work

Open your analytics dashboard right now and do this:

  1. Pick the three metrics you check most often.
  2. Run each one through the four questions above.
  3. For every metric that fails, write down the question you'd actually need answered. Not "what's my bounce rate" but "which page is losing me money and why."
  4. Those questions are your real requirements. Judge every analytics tool, report, and dashboard against them.

Most dashboards fail all four questions on most metrics. That's not a data problem. That's a translation problem.

The takeaway

Data isn't valuable because it's collected. It's valuable the moment it tells you what's broken and what to do about it.

Metrics without causes create work instead of removing it.

The four-question test tells you in seconds whether a number deserves your attention.

This is the gap Clerion was built to close: read the data, skip the guesswork, and hand you the sentence instead of the spreadsheet. Try it on your own site and see what your numbers have been hiding.

Photo by Redd Francisco on Unsplash

Related reading

  • Bot filtering: analytics that count only humans: how Clerion filters bots by default.
  • Understanding website visitors beyond pageviews: what your real visitors look like.
  • Data visualization is not insight: why clean data matters more than more charts.
  • Fathom vs Plausible vs Clerion: which privacy analytics is best?: how each tool handles bots and AI traffic.

Frequently asked questions

How much website traffic is bots?

Imperva's 2026 Bad Bot Report, published in May 2026, found bots account for over 53% of all web traffic. Cloudflare also reported in 2026 that bots had passed humans on its network.

How does bot traffic affect analytics?

Bots load pages, bounce and register sessions without ever buying or signing up, which inflates traffic totals and distorts bounce rates and conversion rates.

What makes a metric actionable?

One that names a cause, can be acted on within minutes, states what it's costing you, and makes sense to a non-technical teammate.

Does GA4 filter bot traffic?

GA4 excludes known bots that identify themselves, but you can't see how much it removed, and disguised scrapers and headless browsers can still get through.

Sources

  • The 2026 Bad Bot Report is here (Imperva / Thales community, May 2026)
  • 2025 Imperva Bad Bot Report: How AI is Supercharging the Bot Threat
  • Bots have officially overtaken humans on the internet, says Cloudflare (TechSpot)
  • How to identify bot traffic in Google Analytics (Centinel)
product philosophywebsite bot trafficbot trafficactionable metrics
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
  • Clerion vs PlausiblePage
  • Clerion vs FathomPage
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.