Skip to main content

Solutions

Traffic from AI answers

Visits from AI assistants often land in analytics as direct traffic. How to attribute them and connect the crawl that fed the answer to the click it produced.

Start free Browse the catalogue

Free plan, no card. 100,000 events a month with every feature on.

botscope.io · last 7d

This site, classified by this product. Nothing here is a mock-up.

live
requests
4,245
human
80%
AI agents
0%
stopped
0%
verdict stream
  1. signals
    • threat_feed: datacenter — fail (listed on a subscribed feed)
    • anomaly_score: 0.25 — pass (combined disagreement across the collected signals)
  2. signals
    • threat_feed: datacenter — fail (listed on a subscribed feed)
    • anomaly_score: 0.25 — pass (combined disagreement across the collected signals)
  3. signals
    • anomaly_score: 0.40 — pass (combined disagreement across the collected signals)

botscope.io's own traffic only — never a customer's. No addresses, no query strings, and a path is shown only when it is already a public page.

In short

  • People arriving from an AI answer frequently show up as direct traffic, because the referrer is missing or stripped.
  • Botscope records both halves: the crawl that read a page and the visit that followed.
  • The pair is the useful part — a page can be read heavily and send nobody, and that is worth knowing.
  • This is measurement, not attribution modelling. There is no claim about what caused a purchase.

Updated 16 September 2026

01 · the referrer that is not there

The referrer that is not there

A person reads an answer, clicks a citation, and lands on your page. Depending on the surface and the client, your analytics may see a referrer, a stripped one, or none at all — in which case the visit is filed as direct.

Direct is where unattributable traffic accumulates. Once a channel lands there, it cannot be sized, and a channel that cannot be sized does not get worked on.

02 · connecting the two halves

Connecting the two halves

  1. 1 Record which agents read which pages, with dates.
  2. 2 Record visits whose referrer or entry pattern matches an AI surface.
  3. 3 Line the two up per page: what was read, and what came back.
  4. 4 Read the ratio per page rather than in aggregate. The aggregate hides the pages doing the work.

03 · assistants that both crawl and cite

Assistants that both crawl and cite

Bot Operator Default policy Verifiable
A360-Search Area360 Observe By user agent
AASA-Bot Apple Observe By user agent
ActiveComply ActiveComply Observe By user agent
adbeat_bot Adbeat Observe By user agent
AddThis.com Oracle Observe By user agent
AdkernelTopicCrawler AdKernel Observe By user agent
admantx Integral Ad Science Observe By user agent
AdmixerBot Admixer Observe By user agent
AdsBot-Google Google Observe By user agent
AdsBot-Google-Mobile Google Observe By user agent

Read live from the Botscope crawler catalogue. Default policy is the catalogue default; every agent can be overridden per site.

04 · what this is not

What this is not

It is not attribution in the marketing sense. There is no model here apportioning credit for a conversion across channels, and adding one would mean inventing the part that cannot be observed.

Where a client sends no referrer and shares no identifiable pattern, the visit stays unattributed. It is reported as unattributed rather than assigned to the likeliest source.

Questions

Why does AI traffic show as direct?

Some surfaces send no referrer, some strip it, and some clients open links in a context that carries none. Nothing is misconfigured on your side.

Can you tell me which prompt produced a visit?

No. The prompt is not in the request and cannot be recovered from it. Anything reporting prompts is simulating them separately, which is a different measurement.

What is a crawl-to-refer ratio?

How many visits came back per crawl of a page. It is a comparison between your own pages, not a benchmark against anyone else.

Do I need to change my analytics setup?

No. This is recorded at your origin and read in Botscope alongside whatever analytics you already run.

See which of these reach your site

Free plan, no card: 100,000 events a month with every feature on. Nothing is blocked until you turn enforcement on.

Start free Browse the catalogue

Related