Patreon stops asking AI bots not to scrape — and starts blocking them

Patreon, the membership platform for creators, is moving beyond polite requests to actively blocking AI bots that scrape content for training purposes. On Thursday, the company announced it is working with Cloudflare to directly block access to AI crawlers that harvest creators’ work without permission, using Cloudflare’s AI Crawl Control technology.

Why Patreon escalated its approach

Since 2023, Patreon had relied on robots.txt files — a standard web protocol — to ask AI crawlers not to scrape content. However, the company found that many AI training bots simply ignored those instructions. In testing, individual AI training crawlers attempted to access Patreon thousands of times per week before the new blocks were implemented; after, those attempts dropped to zero. The shift reflects a broader industry recognition that voluntary compliance from AI companies is insufficient.

How the new system works

Patreon is extending its existing partnership with Cloudflare to use the company’s AI Crawl Control tools. Unlike robots.txt, which relies on the goodwill of crawlers, Cloudflare’s system actively blocks unauthorized AI bots at the network level. The company noted that its paywall had historically kept much creator content out of reach, but newer features — such as the redesigned Home Feed and tweet-like Quips — exposed more content to potential scraping. Patreon’s product chief Drew Rowny stated, “On most of the Internet, creators have to accept AI training on their work just to reach and grow an audience. Patreon has a different vision.”

What this means for creators

For creators using Patreon, the change provides a stronger layer of protection against unauthorized use of their work in AI training datasets. The company emphasized that it will continue to allow bots that index pages and send users back to Patreon, preserving discoverability while blocking training-specific crawlers. This approach mirrors a growing trend among publishers and platforms seeking to reclaim control over how their content is used by AI companies.

Industry context and implications

Patreon’s move comes amid a broader reckoning across the publishing and creative industries over AI training data practices. Cloudflare recently introduced a “Pay Per Crawl” marketplace that lets websites charge AI bots for scraping, and changed its policies to block “mixed-use” crawlers — those that both index and train — by default on ad-supported pages. Patreon’s decision to actively block rather than request reflects a hardening stance that may influence other platforms. The company’s blog post made the position clear: “Consent shouldn’t depend on whether a scraper chooses to behave.”

Conclusion

Patreon’s enforcement shift from passive requests to active blocking represents a meaningful step in protecting creator content from unauthorized AI training. By leveraging Cloudflare’s infrastructure, the platform is implementing a technical solution that goes beyond industry norms, signaling that voluntary compliance from AI companies is no longer considered sufficient. The move underscores the growing tension between AI development and creator rights, and may set a precedent for other membership and content platforms.

FAQs

Q1: How does Patreon’s new AI blocking differ from robots.txt?
Robots.txt is a text file that asks crawlers to follow certain rules, but it is not enforceable. Patreon’s new system uses Cloudflare’s AI Crawl Control to actively block unauthorized AI bots at the network level, preventing access regardless of whether the bot respects robots.txt.

Q2: Will this affect legitimate search engines like Google?
No. Patreon stated it will allow bots that index pages and organize information to send users back to Patreon. The blocks target only AI training crawlers, not standard search engine indexing bots.

Q3: Why did Patreon need stronger measures now?
Patreon introduced new discovery features such as a redesigned Home Feed and Quips, which exposed more creator content to potential scraping. Additionally, AI training bots had become more sophisticated and were ignoring Patreon’s existing robots.txt instructions, necessitating a technical enforcement approach.