WysLeap
Guide · Bot traffic

How do I filter bot and AI agent traffic out of my website analytics?

Use an analytics tool that flags automated traffic before it reaches your reports, and keep a raw view to check it against. WysLeap does this at ingest: it flags known bots and AI crawlers, headless and automated browsers (the way many AI agents browse) and repeat visits that don't behave like people, keeps them out of its human metrics, and shows raw and clean numbers side by side. Google Analytics only drops bots on known lists and doesn't show what it removed; Cloudflare Bot Management can score and block bots in front of your site.

Updated

Tools that filter bots and AI agents for you

  • WysLeap: flags bots, AI crawlers and automated browsers when each hit arrives, keeps them out of human metrics, reports AI crawlers separately and has a raw and clean toggle with a Data Quality Score. See bot detection.
  • Google Analytics 4: excludes bots on Google's and the IAB's known lists automatically. You can't see or adjust what it removes.
  • Cloudflare Bot Management: scores and blocks bots before they reach your site, for sites behind Cloudflare.

Three kinds of automated traffic

Crawlers that don't run JavaScript

Search and AI crawlers such as Googlebot, GPTBot, ClaudeBot and PerplexityBot mostly fetch your HTML and leave. Script-based analytics never runs for them, so they rarely pollute your numbers. You still want to know what they read: see how to see which AI crawlers visit your site.

Known bots that do run JavaScript

Monitoring services, SEO tools and some crawlers render pages in a browser. Most announce themselves in the user agent, and most analytics tools drop them automatically. GA4 does this using Google's research and the IAB bots list.

Automated and AI agent browsers

This is what slips through. Scrapers, testing scripts and AI agents that browse on someone's behalf drive a real browser, run your JavaScript and often use an ordinary browser user agent. They show up as visitors with odd behavior: no scrolling or mouse movement, identical visits repeated, very short or perfectly regular timing, traffic from data centers.

How to filter them

  1. Start with what your tool does automatically. In GA4 that's the known-bot exclusion, which you can't see or adjust.
  2. Leave out your own team and referral spam. In GA4, define internal traffic by IP and activate the data filter. Spam referrers need a segment or report filter.
  3. Look for automation. Headless browsers and automation frameworks leave traces (for example navigator.webdriver), and behavior gives the rest away. This needs detection in the tracking script or a bot-management service in front of your site.
  4. Compare raw and filtered numbers. A filter you can't check is a guess. Keep a raw view and watch the gap, especially after a traffic spike.

What WysLeap does

WysLeap checks every hit at ingest: known bot and AI crawler user agents, automation and headless-browser detection, simple browser signals, and signals across visits, such as one device coming back to the same page under new visitor IDs with the same scroll depth and no clicks. If you connect Google Search Console, visits that claim to come from Google search on pages Search Console shows no Google clicks for are flagged too.

Flagged hits are kept out of human metrics such as visitors, sessions and conversions. A raw and clean toggle and a Data Quality Score show what was removed. Read more on bot detection and data quality.

No bot filter is perfect, WysLeap's included. Treat the clean view as your best estimate and the raw view as the check on it.

Side by side

Bot filtering in WysLeap and GA4

FeatureWysLeapGoogle Analytics 4
Known bots excluded automatically
Automation and headless-browser detection
Not documented
Signals across visits (same device, new IDs)
See raw vs filtered traffic
AI crawlers reported separately
Referral spam left out
Manual
Internal traffic left out

FAQ

Frequently asked questions

Does Google Analytics 4 filter bots?
Yes. GA4 automatically excludes traffic from known bots and spiders, identified by Google's research and the IAB's International Spiders and Bots List. You can't turn it off or see how much traffic was excluded, and it doesn't catch bots that aren't on those lists.
Do AI agents like ChatGPT's agent show up in analytics?
They can. An agent that browses with a real browser runs your JavaScript, so script-based analytics may count it as a visitor. Crawlers that only fetch HTML, such as GPTBot or PerplexityBot, usually don't run the script and don't appear.
How does WysLeap detect bots?
Known bot and AI crawler user agents (our own curated list), automation and headless-browser detection, and simple browser signals, plus signals across visits, such as one device returning to the same page under new visitor IDs with the same scroll depth and no clicks. Bots are flagged at ingest and kept out of human metrics. Referral spam (a curated list of about 70 domains) and your own team's visitor IDs are left out of the clean view too.
Can I see what was filtered?
Yes. WysLeap has a raw and clean toggle, so you can compare all traffic with the filtered view, and a Data Quality Score from 0 to 100. AI crawler visits are reported separately on the SEO & GEO dashboard.

Count people, not bots.

Bots flagged at ingest, a raw and clean view, and AI crawlers tracked on their own.