Signals
Back to feed
7/10 Safety & Policy 1 Jul 2026, 18:00 UTC

Cloudflare requires AI companies to separate search and AI crawlers by September 15 or face default blocking.

Cloudflare's mandate closes a critical loophole where AI scrapers masquerade as traditional search indexers to bypass robots.txt restrictions. This will severely throttle data acquisition pipelines for model builders relying on passive scraping, forcing a shift toward explicit data licensing APIs. Engineers managing web scraping infrastructure must update their user-agent strategies before the deadline or face widespread 403s across publisher sites.

What happened

Cloudflare has issued an ultimatum to AI companies: by September 15, they must explicitly separate the web crawlers used for traditional search indexing from those used for AI model training and autonomous agents. Failure to declare and separate these bots will result in unified crawlers being blocked by default across Cloudflare’s massive network of publisher sites.

Technical details

Historically, tech giants have used the same or broadly defined user agents (like `Googlebot`) for multiple purposes. Publishers generally want their content indexed for search visibility (SEO), but actively want to block scraping for LLM training unless they are financially compensated. By requiring distinct user agents (e.g., separating standard search bots from AI-specific ones like `Google-Extended` or `GPTBot`), Cloudflare allows its WAF (Web Application Firewall) customers to apply granular access controls via a simple toggle. Cloudflare's "AI Scraper Block" feature will utilize these explicit user-agent strings, combined with behavioral heuristics, TLS fingerprinting, and ASN tracking, to enforce compliance at the edge.

Why it matters

From an engineering perspective, this fundamentally alters the data acquisition landscape for foundation models. AI companies can no longer piggyback their scraping operations on the mutually beneficial "traffic-for-content" exchange of traditional search. This forces a hard unbundling of scraping infrastructure. For AI startups and data engineers, this means passive web scraping pipelines will experience a massive drop in yield as Cloudflare's edge network drops their requests. It accelerates the transition from open-web scraping to authenticated, API-driven data licensing agreements.

What to watch next

Monitor how major players adjust their crawler topologies and user-agent declarations leading up to the September deadline. Additionally, watch for an arms race in scraper evasion techniques—such as the increased use of residential proxy networks and headless browser automation—as smaller AI players attempt to bypass Cloudflare's heuristics. Long-term, expect a surge in specialized data brokers and standardized protocols for programmatic data licensing.

data-scraping cloudflare policy crawlers data-licensing