Cloudflare draws a line: AI crawlers must separate from search bots or face default blocking
The CDN giant is giving AI companies until September 15 to split training and agent crawlers from search crawlers, or risk being blocked by default across a huge swath of publisher sites.
What matters
- Cloudflare is requiring AI companies to separate search crawlers from AI training/agent crawlers by September 15 or face default blocking on publisher sites.
- New web domains on Cloudflare will be asked at signup whether to allow or block AI crawlers, giving publishers explicit control.
- A new 'pay per crawl' model lets publishers charge AI crawlers for content access.
- Roughly 16% of global internet traffic flows through Cloudflare's CDN, giving the policy broad reach.
- Automated agents and bots now account for more than half of all web requests, per Cloudflare's own data.
What happened
On July 1, 2026, Cloudflare announced a sweeping new policy aimed at reshaping how AI companies access web content. The company is giving AI firms until September 15 to separate their web crawlers into distinct categories—one for traditional search indexing and another for AI training and agentic use. If AI companies fail to make that distinction, they risk being blocked by default on many publisher sites that use Cloudflare's services.
The announcement, detailed in a Cloudflare press release titled "Your Content, Your Rules," introduces new crawler classifications, enhanced analytics, and commercial partnerships designed to help site owners and transparent AI companies collaborate. Every new web domain that signs up for Cloudflare will now be asked whether they want to allow or block AI crawlers, giving publishers granular control over who scrapes their content and for what purpose.
Cloudflare is also introducing a "pay per crawl" model that allows publishers to charge AI crawlers for access to their content. CEO Matthew Prince framed the move as a rebalancing act: "AI crawlers have been scraping content without limits. Our goal is to put the power back in the hands of creators, while still helping AI companies innovate."
Why it matters
Cloudflare is not a niche player. The company estimates that roughly 16% of global internet traffic flows through its content delivery network, making it one of the largest infrastructure gatekeepers on the web. When Cloudflare changes its default crawler policy, the ripple effects touch a substantial portion of the internet.
The policy shift comes at a moment when the fundamental nature of web traffic has changed. According to Cloudflare, automated agents and bots now drive more than half of all web requests. AI is becoming a primary interface for accessing information and conducting commerce, which means the old assumptions about how content is discovered and monetized no longer hold.
For publishers—especially those reliant on advertising or subscriptions—uncompensated AI training on their content is an existential threat. Cloudflare's new framework attempts to create a structured market where publishers can opt in to AI discovery while still being compensated for training use. For AI companies, the September 15 deadline creates real pressure to comply or lose access to a significant portion of the web.
One lawyer told CNBC the move could "hinder AI chatbots' ability to harvest data for training and search purposes," signaling that the legal and competitive implications are still being assessed.
What to watch
- September 15 deadline: Whether major AI companies—OpenAI, Google, Anthropic, Meta, and others—comply by separating their crawlers or push back against the requirement.
- Pay per crawl adoption: How many publishers enable the monetization model and what pricing structures emerge.
- Competitive response: Whether other CDNs and infrastructure providers follow Cloudflare's lead or position themselves as more AI-friendly alternatives.
- Legal challenges: Whether AI companies challenge the policy on grounds related to access, fair use, or antitrust considerations.
- Impact on AI model quality: If a meaningful portion of training data becomes gated or paid, how that affects the next generation of AI models.
What to do next
Developers
Audit your organization's web crawlers and ensure search-indexing bots and AI-training bots are clearly separated with distinct user agents and identifiable endpoints before September 15.
Cloudflare's policy will block non-compliant crawlers by default, so technical separation is essential to maintain access to publisher content.
Founders
Evaluate whether your AI product's data pipeline depends on scraped web content and explore licensed data partnerships or the pay-per-crawl model as alternatives.
If your product relies on broad web scraping, the new default-blocking policy could cut off a significant portion of content sources routed through Cloudflare.
PMs
Map which features in your product depend on real-time web content retrieval versus model training, and prioritize compliance for the most critical crawlers.
The policy distinguishes between search and training use cases, so PMs need to understand which crawlers serve which product functions to avoid unnecessary blocking.
Investors
Assess portfolio companies' exposure to Cloudflare's policy—particularly those dependent on web-scraped training data—and monitor whether the pay-per-crawl model creates a new content-licensing market.
Companies with heavy reliance on free web scraping face potential cost increases or data access restrictions, while content owners may unlock new revenue streams.
Operators
If you manage websites through Cloudflare, review the new AI crawler opt-in settings and decide whether to enable blocking, allowlisting, or pay-per-crawl for your domains.
Cloudflare is surfacing these choices at domain signup, so operators need to make deliberate policy decisions rather than accepting defaults.
How to test
- 1Log in to your Cloudflare dashboard and navigate to the new AI crawler settings section for your domain.
- 2Review the new crawler classifications to see how Cloudflare distinguishes search crawlers from AI training and agent crawlers.
- 3Choose whether to allow, block, or enable pay-per-crawl for AI crawlers on your domain.
- 4Monitor the enhanced analytics dashboard to see which crawlers are attempting to access your site and how they are classified.
- 5If you operate crawlers, test whether your bots are correctly identified under the new classification system.
Caveats
- The policy is new and classification accuracy may improve over time—monitor for false positives where legitimate search crawlers are misclassified.
- Pay-per-crawl pricing structures may not be fully established yet, so early adopters should track terms carefully.
- Blocking AI crawlers could reduce your content's visibility in AI-powered search and assistant products.