TL;DR: Patreon is partnering with Cloudflare to block AI training crawlers across every post on the platform at the network layer, with search crawlers still allowed so creators keep discoverability. The deployment uses Cloudflare's Crawl Control product, the same infrastructure Cloudflare rolled out to newsletter platform beehiiv on June 23, and the same default-block taxonomy it announced on July 1 for its second annual Content Independence Day [1][2][4]. The surveillance angle: the consent question for AI training is moving from a robots.txt honor system to a network-level enforcement question, and Cloudflare's own data says AI training crawlers now account for 52 percent of crawler requests, up from 22 percent in spring 2025 [3].
What Was Announced
On July 9, 2026, Patreon founder and CEO Jack Conte published a video and Instagram post confirming the platform-wide deployment of Cloudflare's Crawl Control across all posts published on Patreon [1]. The mechanism blocks known AI training crawlers at the network edge, while leaving search crawlers permitted so creators can still be discovered through Google and Bing. AI-generated content is not banned on Patreon, and the existing AI content policy (last updated in 2025) remains in place.
Conte framed the move in the language of consent. "Creators deserve credit, compensation, and consent," Conte said. "If that's not on the table, the crawlers can stay the fuck off Patreon." He added, in a separate post on his Patreon page, that "consent" means "do I get to opt out of my work being used by these models as training data" [1].
Drew Rowny, Patreon's senior vice president of product, gave 404 Media the operational read: "On most of the Internet, creators have to accept AI training on their work just to reach and grow an audience." The Crawl Control deployment reframes that default: creators get to grow an audience through search without also feeding the training pipeline by default [1].
How Crawl Control Works
Cloudflare's taxonomy now classifies bots into three AI use cases: Search (crawlers indexing content to answer later queries), Agent (real-time automation acting on a human's behalf), and Training (crawlers absorbing data into model architecture). The list also covers Transact, Data Collection, Security Testing, SEO, Ads Verification, Social/Link Preview, Feed Fetching, and Monitoring and Operations [2].
Beginning September 15, 2026, all new Cloudflare domains will block Training and Agent bots by default on pages that display ads. Search bots remain allowed by default. Multi-purpose crawlers such as Googlebot, Applebot, and BingBot are now evaluated by all the behaviors they exhibit, not just by the bot name on the wire [2]. Cloudflare also updated the meaning of "Verified": bots that reproduce content in full can no longer hold Verified status, and Verified bots are now allowed only within their declared category.
The Patreon deployment sits on top of this taxonomy and turns the default on for the entire creator base. The control is one switch from the platform's side, not a per-creator robots.txt file or a manual firewall rule. The same architecture was offered to newsletter platform beehiiv on June 23, 2026, when Cloudflare and beehiiv jointly introduced AI Crawl Controls for independent publishers [4][5].
The Traffic Data Behind the Switch
Cloudflare's own agentic Internet bot report, published July 1, 2026, frames the timing. The report found that AI training crawlers now account for 52 percent of crawler requests across Cloudflare's network, up from 22 percent in spring 2025. Mixed-use crawlers account for over 36 percent of requests. Pure search crawling is a small and declining share. Over 50 percent of all internet traffic is now non-human, a threshold crossed for the first time in the report's measurement [3].
The report also notes that Google accounts for approximately 88 percent of referral traffic, and that heavily crawled categories saw human traffic decline "as much as 40 percent in less than one year." The phrase publishers are using for the worst-case scenario is "Google Zero," a world with little to no search referral traffic. More than 50 publisher-AI agreements have been signed since 2023, but the underlying traffic mix has continued to tilt toward AI crawlers [3].
Cloudflare serves over 20 percent of the web, 36 percent of the most-visited sites, and 40 percent of the Fortune 500. Nearly 80 percent of leading AI companies sit behind Cloudflare's network. A default-block policy decision made at Cloudflare is, in practice, a policy decision for a meaningful slice of the open web [3].
Why This Matters
The old consent regime was robots.txt. A robots.txt file is a request, not a command. Crawler operators that respect it leave it alone; crawler operators that do not respect it scrape anyway. The enforcement question has been litigated in court for years and is the same underlying fact pattern in the existing AI training data copyright scraping lawsuits, where the dispute is whether scraping a public web page is a license to feed it into a model.
Crawl Control moves the question from application-layer honor system to network-layer enforcement. A platform that opts in does not have to detect a bad bot, file a takedown request, or chase the operator through a courtroom. The bot never reaches the page. The default flips, and the burden of opting in shifts to the operators who want the data.
That is the surveillance primitive worth naming. Today the data that gets scraped is the data a creator chose to publish. Tomorrow, the data that gets scraped is the data an operator could reach. A network-level default-deny narrows the reach from "what is public" to "what is reachable by a bot the network permits." The two are not the same set, and the gap between them is the place where the consent question will live for the rest of the decade.
What to Watch
September 15, 2026 default flip. New Cloudflare domains block Training and Agent bots on ad-displaying pages by default. Existing customers will need to opt in to keep the old behavior. The first round of opt-in and opt-out telemetry will be the natural read on how many publishers actually want the crawl [2].
The beehiiv and Patreon follow-through. Beehiiv opened Crawl Control in beta to all users on June 23, with full blocking available to beehiiv Max customers. Patreon flipped it on platform-wide by default. Watch for other major creator platforms and hosted newsletter services to ship matching defaults, or to face the question of why they did not [4].
Agent traffic. Cloudflare's report puts non-human traffic past 50 percent. The Training vs Agent split is the next boundary. A user-initiated Agent bot acting on a human's behalf has a different legal posture from a training crawler running overnight. Watch for the courtroom test that distinguishes the two [3].
Cloudflare CEO Matthew Prince's framing. Prince called the beehiiv partnership "the next logical step" in Cloudflare's mission. The September default flip is the test of whether the policy survives contact with paying customers who want the opposite. If any major publisher publicly opts back in to training crawlers, the "default" debate moves from architecture to marketing [4].
Sources
- 404 Media, Samantha Cole: “Patreon Blocks Crawlers From Stealing Creators' Work for AI Training” (July 9, 2026)
- Cloudflare blog, Jin-Hee Lee and Bryan Becker: “Your site, your rules: new AI traffic options for all customers” (July 1, 2026)
- Cloudflare blog: “Content Independence Day, one year on: building the business model for the agentic Internet” (July 1, 2026)
- Cloudflare press release: “Cloudflare and beehiiv Introduce AI Crawl Controls to Help Independent Publishers Navigate the AI Era” (June 23, 2026)
- Nieman Lab: “Beehiiv's new Cloudflare partnership gives indie journalists a new level of control over AI crawlers” (June 25, 2026)