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
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.
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.
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.
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.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
| Feature | WysLeap | Google 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
Other guides
Bots flagged at ingest, a raw and clean view, and AI crawlers tracked on their own.