Skip to content
Traffic Quality

Separate people from machines

An AI reading your site is not an AI sending customers.

AI crawlers fetch your pages to index, train on or answer from them. This report shows which agents, how much they fetch and which sections they concentrate on. A person arriving from an assistant is a different fact entirely, counted in Acquisition as an AI referral, and the two are never added together.

AI Crawlers

  • Named agents with crawl volume
  • Crawl concentration by content area
  • Kept separate from AI referrals
  • Origin load during crawl bursts

How it helps

What AI Crawlers gives you

1

Crawl is not referral

The two move independently. A documentation crawl that triples brings nobody to the checkout, and assistant referrals can rise in a week the crawl falls. Reported as one number, both facts disappear.

2

Which content is being read

Crawl concentration by area shows whether agents are working through the docs, the pricing page or the changelog. That is the material most likely to be reflected when an assistant describes your product, which makes it worth keeping accurate.

3

The cost of being read

AI crawl is origin load: bandwidth and requests for pages no customer asked for. Volume is reported beside origin response times, so a crawl that overlaps slower responses for real visitors is visible rather than assumed.

Connect 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