InfoGap Data China cities Slices Algorithms

AI referrers to our own site

Everyone publishes what AI crawlers take from a site. Almost nobody publishes whether an AI answer ever sends anyone back, because that number lives in the referrer field of the site owner's own log. We hold that log. The number is zero, so we are publishing the zero.

0 of 112,827 parsed request lines arrived with a referrer from an AI answer-engine domain.

Traffic that can be identified as coming from an AI answer is not visible in this log at all. Search engines, by contrast, do show up: 117 request lines carried a referrer from a traditional search engine.

The numbers

ValueWhat it countsSource / definition
112,827request lines parsedAll lines in the nine most recent nginx access logs on the infogap.store server (current log plus eight rotated files), as of 2026-10-09 06:30 Asia/Shanghai. Source: this site's own logs.
0referrers from AI answer-engine domainsRequest lines whose referrer host matches one of the AI answer-engine domains we track. None matched. This counts what the log says, not what is true.
117referrers from traditional search enginesBaidu (116 lines: www.baidu.com 116, m.baidu.com 19 are counted as one family in the dataset), Google (64), Bing (2), 360 (m.so.com, 2), DuckDuckGo (1). See the dataset for the exact per-host counts.
6,388referrer lines from our own two hosts96.8% of the 6,598 lines covered by the 18 referrer hosts we list. Our own properties point at each other; this is internal navigation, not audience.
18distinct referrer hosts seenAggregated by referrer host. A host here is not a person: one line is one request, not one visitor.

What one record is

One record is one request line in our nginx access log that carried a Referer header, grouped by the host of that header. Records with no referrer header, and requests from our own hosts, are counted separately and are not evidence of outside audience.

Records

  1. Zero, and we are not going to round it up. No referrer in the window points at an AI answer-engine domain. Whatever an answer engine may have taken from this site, nothing in this log shows a reader arriving from one.
  2. Most of what looks like referrer traffic is us. Our own two hosts account for 6,388 of the 6,598 lines in the host list we publish. Internal links between our own pages dominate every other source combined. Any dashboard that summed referrer lines without separating internal traffic would report roughly a hundred times the external reality.
  3. Search engines do refer, and they are small. Baidu and Google together account for 180 lines, Bing, 360 and DuckDuckGo for 5 more. A site that exists to answer questions is currently being found mainly by people who already knew where to look.
  4. This page pairs with the crawler-side count. AI crawler hits on our own site counts what crawlers took; this page counts what came back. The two are counted over different windows on purpose — see the note below — so they must never be divided into a "conversion rate".

What this cannot tell you

Data & methods

Where to go next