Separate people from machines
Know which traffic was people — and what the rest of it was.
Every HTTP request proxied through the edge is classified before it becomes a number: human visit, verified search crawler, AI agent, other automation, suspicious request or blocked attack. The business view counts people. The rest stays visible in its own report, because knowing that a crawl happened is worth as much as keeping it out of the total.
Why it matters
What Traffic Quality is for
Request volume is not activity
Total requests rise for reasons that have nothing to do with customers. When the total doubles overnight while human visits stay flat, the honest reading is that something crawled the site — and a chart without this split reports it as growth.
Classified in the request path
Classification happens at the edge, on proxied HTTP traffic, before anything reaches your origin. Smart Beacon only records browsers that run it, so automation that never executes JavaScript is absent from a beacon-only chart rather than classified in it.
Excluded, never discarded
Each class keeps its own report, and any metric can be re-run with a class included. The classifier computes the split deterministically; the AI explains what moved and where to look. A number you cannot take apart is a number you cannot defend.
What's included
Inside Traffic Quality
Each capability is its own surface, and all of them read the same four data layers under one set of metric definitions.
Real People
The human-only view every other module counts and divides by.
Learn moreSearch Crawlers
Crawler activity from verified operators — volume, coverage and the status codes they were served.
Learn moreAI Crawlers
AI-agent crawl volume and the content areas being read — not the same as a referral.
Learn moreBots
Monitors, scrapers, feed readers, link previews and your own tooling, classified by behaviour.
Learn moreSecurity Traffic
Suspicious requests with challenge outcome and reputation context, read as analytics rather than alerts.
Learn moreBlocked Attacks
Attack volume summarised for analytics, with the forensics handed to the edge console.
Learn moreThe platform
The rest of the engine
AI Overview
Opens with a written briefing: what changed, why it matters, what to check.
5 capabilitiesAsk AI
Plain questions become governed metric queries. Every answer arrives with the definition behind it.
5 capabilitiesAcquisition
Channels, campaigns, referrers and AI assistants, sorted by revenue rather than traffic volume.
6 capabilitiesConnect a site today. Read tomorrow's brief instead of building it.
Connect a site and the first brief arrives with the day's changes already explained — traffic separated from bots, conversions attached to revenue, and the evidence behind every sentence one click away.
Real people separated from bots Every answer shows its evidence Reveliqo runs on Reveliqo