Cloudflare's Bot Blocking Is Closing AI Licensing Deals
August 17, 2026
Editorial Policy
All of our content is generated by subject matter experts with years of ad tech experience and structured by writers and educators for ease of use and digestibility. Learn more about our rigorous interview, content production and review process here.
Key Points
- Cloudflare's pay-per-crawl and pay-per-use plans are actively helping publishers convert bot-blocking into licensing revenue, according to reporting by Press Gazette.
- If your blocks aren't working, the problem may be a leaky bucket elsewhere. Content syndication to sites that allow AI crawlers is a common culprit.
- Health charities are the latest publishers to confirm traffic losses from Google AI Overviews, though donations and high-intent visits appear to be holding steady.
- AI licensing deals are becoming a real revenue channel, with Apple now reportedly in multi-year pay-per-use negotiations with publishers.
- Whatever traffic you're losing to zero-click AI answers, the traffic you still have is worth more optimized than it used to be. Don't leave yield on the table.
What Cloudflare Is Doing
Cloudflare has moved well past "here's a toggle to block GPTBot." Press Gazette reports that Cloudflare Chief Strategy Officer Stephanie Cohen is actively positioning the company's pay-per-crawl and pay-per-use products as tools that turn AI blocking into AI licensing. The logic: demonstrate you can control access to your content, then use that leverage to negotiate.
People Inc. CEO Neil Vogel vouches for the outcomes, according to the reporting. That's a meaningful data point. When publishers with real scale confirm the pipeline from blocking to AI licensing deals, this stops being a theoretical strategy and becomes an operational one worth replicating.
The Leaky Bucket Problem
At Press Gazette's AI Summit in London in June, concerns surfaced that blocking AI bots doesn't always mean the bots are blocked. There are too many vectors: user agent spoofing, residential proxies, and content that travels well beyond your own domain.
Cohen pushed back, insisting Cloudflare's blocks are sophisticated and effective. Her explanation for publishers who are still getting scraped despite active blocks: the leak isn't in the wall, it's in the syndication pipes. If you're distributing content to partner sites, aggregators, or licensing arrangements that don't enforce the same crawler restrictions, you've already handed the content over.
Publishers often treat AI blocking as a single technical decision at the domain level. It isn't. It's an end-to-end content supply chain problem.
Here's what that checklist should look like:
- Syndication agreements: Review whether partner sites allow the crawlers you've blocked on your own domain.
- Content APIs: Confirm that structured data endpoints aren't indexed or accessible to AI scrapers without authentication.
- Third-party embeds: Any content surfaced through RSS, AMP, or third-party widgets is a potential exposure point.
- Cached versions: Ensure crawler policies propagate to CDN layers, not just origin servers.
Essential Background Reading:
- What Publishers Need to Know About AI Bot Traffic in 2026: The foundational guide to understanding how AI bot traffic is reshaping publisher metrics and what to do about it.
- Cloudflare's AI Bot Controls: What Publishers Need to Know: A detailed breakdown of Cloudflare's bot control tools and how publishers can configure them effectively.
- AI Bot Traffic Is Now 40% of the Web: The scale of AI crawler activity across the web and why publishers can no longer treat it as a niche concern.
- AI Crawler Resource Center for Publishers: The full decision framework for managing AI crawlers, from blocking strategy to licensing readiness.
Health Charities Confirm What Publishers Already Feared
The Google AI Overviews traffic impact has a new victim category. Several health charities told Press Gazette that website traffic has dropped as users get answers directly from AI-generated summaries, bypassing the charities' pages entirely. This is the zero-click problem hitting organizations that can't monetize their way out of it the way a commercial publisher might.
The good news: Donations appear to be holding, and forum engagement is staying strong. Users who work through a health question via an AI Overview and then decide they need human support are still arriving at charity sites. They're just skipping the informational first step. That's a different kind of loss than the one most publishers are dealing with.
For commercial publishers, the dynamic is similar but the financial stakes look different. Informational content that used to generate high-volume, low-intent traffic is absorbing the hardest hits. High-intent traffic, whether that's a user ready to subscribe, register, or purchase, appears more durable.
Related Content:
- How AI Crawlers Are Affecting News Publisher Ad Revenue: Specific analysis of how crawler activity is hitting news publisher revenue and practical mitigation steps.
- AI Bots Are Killing Publisher Engagement: How AI bot traffic inflates session counts while depressing real engagement metrics, and what publishers can do.
- Cloudflare's Default AI Bot Block Is Killing Your Geo Strategy: Why blanket blocking settings can have unintended consequences for geographically targeted revenue.
- Block AI: Playwire's tools and framework for implementing AI crawler blocking across your content stack.
The Licensing Deal Pipeline
The broader signal from this reporting is that AI licensing is becoming a functional revenue channel, not just a negotiating aspiration. Apple is reportedly in active multi-year pay-per-use discussions with publishers to feed content into an improved Siri, according to the Wall Street Journal. Cloudflare's blocking infrastructure is helping publishers create the conditions that make those deals possible, giving them a credible answer to "prove you control your content."
The publishers most likely to close licensing deals share a few characteristics:
- Scale: AI companies want breadth of content, which means large or specialized content libraries hold more negotiating weight.
- Enforcement credibility: Publishers who can demonstrate controlled access are in a stronger position than those whose content leaks across syndication networks.
- Speed: This licensing market is forming now. Publishers who move late will negotiate against a precedent set by publishers who moved early.
Next Steps:
- AI Crawler Protection Grader: Assess how well your current crawler protections are actually working and where the gaps are.
- Reuters' AI Licensing Strategy: What Publishers Can Learn: How a major news publisher built a credible licensing position and what smaller publishers can take from that playbook.
- Agentic AI Promises Are Not a Revenue Strategy Yet: A grounded look at which AI revenue narratives are real and which are still aspirational.
- Yield Experiment Playbook: How to run structured yield experiments to improve RPS as your audience composition shifts.
- Publisher Ad Revenue Maturity Model: A framework for assessing where your monetization strategy stands and what to prioritize next.
What to Do With the Traffic You Still Have
Blocking and licensing negotiations address the supply side of the AI traffic problem. The demand side of your ad revenue equation still depends on what happens with the sessions landing on your pages.
Zero-click AI answers are compressing the top of the funnel. The users who do click through tend to be higher intent. That shift in audience composition has real implications for yield strategy. If your ad stack is optimized for volume-driven CPM targets, it may be misaligned with an audience that's increasingly weighted toward high-intent, engaged users.
RPS (revenue per session) is the metric that matters most here. A smaller, higher-intent audience can outperform a larger, lower-intent one if the monetization layer is calibrated correctly. That means price floors, format mix, and demand path optimization all need to reflect the actual audience you're serving, not the one you had two years ago.
See It In Action:
- Study Circle Case Study: How an education publisher optimized yield and grew revenue while managing a shifting traffic environment.
- Serebii Case Study: A gaming publisher's path to stronger revenue per session through full-stack monetization optimization.
How We Think About This
We work with publishers across gaming, education, news, and entertainment who are navigating this exact shift. The ones absorbing the AI traffic disruption best aren't the ones with the most aggressive blocking policies. They're the ones who've paired traffic defense with yield offense: tightening their monetization on every session while the market figures out what AI licensing pays.
If you want to check how your current crawler protections stack up, our AI Crawler Protection Grader gives you a baseline. The AI crawler resource center for publishers covers the broader decision framework, including when blocking makes sense and when it doesn't. And if you want to talk about what your current traffic is worth with the right stack behind it, that's a conversation we're ready to have.
