Meta’s AI keeps scraping my community website, and I get charged £25 a month for the privilege
Meta's AI crawler aggressively scraped a small community wiki, generating over 230,000 requests in just 1.5 days, consuming nearly half the site's bandwidth and costing the individual operator approximately $30/month in cloud fees. The crawler ignored standard web conventions (robots.txt), systematically targeting low-value pages like edit histories, diffs, and login screens rather than actual content articles. This case exemplifies how large AI companies externalize infrastructure costs onto vo
Analysis
TL;DR
- Meta's AI crawler aggressively scraped a small community wiki, generating over 230,000 requests in just 1.5 days, consuming nearly half the site's bandwidth and costing the individual operator approximately $30/month in cloud fees.
- The crawler ignored standard web conventions (robots.txt), systematically targeting low-value pages like edit histories, diffs, and login screens rather than actual content articles.
- This case exemplifies how large AI companies externalize infrastructure costs onto volunteer-run websites while extracting valuable training data without compensation or regard for site sustainability.
Why It Matters
This incident reveals a critical ethical and economic imbalance in the current AI development model where massive corporations extract data from small-scale community resources without bearing proportional costs. For AI practitioners and researchers, it highlights the need for more responsible crawling practices and sustainable data sourcing models that don't undermine the very communities that contribute to knowledge ecosystems.
Technical Details
- The Meta crawler identified as 'meta-webindexer' made 230,743 requests to the LGBT History Project wiki over 36 hours, representing 28% of total server traffic during that period
- Despite having only 4,814 actual articles, the MediaWiki platform's architecture created hundreds of thousands of unique URLs through revision histories, diff views, and edit interfaces
- The crawler specifically targeted disallowed paths per robots.txt specifications: 226,391 requests (98%) went to /index.php addresses including edit screens, revision diffs, and login pages
- Only 1.5% of requests were for legitimate article content; the single most-requested endpoint was the login screen (113,016 requests)
- The crawler completely ignored the robots.txt file at lgbthistoryuk.org/robots.txt which explicitly prohibited access to these technical endpoints and recommended 10-second request intervals
Industry Insight
AI companies should implement rate-limiting and respect for established web standards when scraping public sites, particularly those maintained by volunteers with limited resources. The industry needs to develop fair compensation mechanisms or infrastructure support for websites that provide valuable training data, recognizing that free data extraction from small operators creates an unsustainable business model. Future AI development should consider partnerships with community organizations rather than unilateral scraping that degrades the services providing their training material.
Disclaimer: The above content is generated by AI and is for reference only.