Story
Oct 23, 2026

Meta Delays Its AI Terms, but Publishers Still See a Scraping Loophole

Meta has postponed new business terms until November 20 after publishers, legal experts and Sen. Marsha Blackburn warned the policy could enable broad AI-related scraping. Meta insists website owners retain control through robots.txt.

Meta’s proposed business terms were initially due to take effect on October 30, and appeared to permit the company to use content from websites connected to Facebook and Instagram business accounts to “develop, research” and “train” its products.

That wording triggered a sharp response from publishers, who feared Meta could use commercial terms to reach beyond the platform and harvest reporting for AI systems. The News/Media Alliance wrote to CEO Mark Zuckerberg, warning of “severe harm” to publishers, while advertisers and publishers in the EU and UK urged regulators to intervene.

Meta then removed the explicit reference to training, but critics said the edit did not settle the central question. Cornell digital-law professor James Grimmelmann argued that the remaining phrase covering content “associated with your products or services” could still let Meta scrape “entire sites.” Media and intellectual-property lawyer Matt Topic made the same practical point: permission to “develop” undefined “business product[s]” could encompass AI training.

The political backlash widened when Sen. Marsha Blackburn, the Tennessee Republican, said the revised terms suggested Meta was trying to “exploit American creators and businesses” by granting itself sweeping authority over websites tied to its business accounts.

Facing that pressure, Meta pushed enforcement to November 20. Spokesperson Daniel Roberts said the pause would give the company time to explain what is changing and stressed that content owners can use robots.txt to signal their preferences. Meta also says the update “is not about scraping news sites” and does not create rights that override those preferences.

For publishers, however, robots.txt is not the issue. Their concern is whether Meta’s contract language could become an end run around it—a question the delay has postponed, rather than answered.