Units and metrics
AI-referrer traffic
Last updated by The PanelCompare editorial team
Why does ai-referrer traffic matter to a buyer?
It is the clearest leading indicator of where this market moves next. Several panels now sell it at roughly $1.00 per thousand visits (PanelCompare domain research, 2026-09-06), and the demand behind it is not consumer demand: it is agencies and in-house teams justifying spend on generative-engine optimisation by producing referral rows in a client’s analytics. The product is a number in a report.
The self-harm is unusually complete. Faked referrals do not just fail to help; they corrupt the exact measurement the buyer commissioned them to demonstrate, making it impossible to tell afterwards whether any real AI referrals arrived. It also travels: analytics feeds ad-platform audiences, so the fabrication propagates into targeting models that then spend real budget.
How does ai-referrer traffic show up in a price list?
It sits inside the website-traffic category as a referrer variant, named for the engine, and is ordered through the same Web Traffic order type with a referring_url parameter.
The honest version of the thing it imitates is measurable directly: server logs show whether AI crawlers fetched a page and whether referrals arrived with those referrers, and neither requires buying anything.
Think this definition is wrong?
Terminology in this market is set by the panels that use it, and it moves. If a panel uses ai-referrer traffic to mean something other than what is written here, send us the listing and we will either correct the definition or record the variant. The process is on the about page.