Meta Delays New Business Terms to November 20 Amid Scraping Dispute
Meta will not enforce its new business terms until November 20, a spokesperson told The Verge, pushing back a start date that had been set for October 30. The company says the extra time is needed to explain the changes to partners and stakeholders.
Daniel Roberts, Meta's spokesperson, said the delay gives the company time to explain how it uses web crawlers, the automated bots that fetch pages from websites. He also said content owners can still use robots.txt, a plain-text file at a site's root that lists the paths a crawler should avoid, to signal their preferences. Robots.txt is a voluntary convention, not an enforcement mechanism, so its effect depends on whether a crawler chooses to honor it.
The terms have drawn fire since Nieman Lab first reported the AI-centric commercial update on October 15. As that report described it, starting October 30, business accounts would consent to Meta scraping their websites simply by continuing to use Facebook, Instagram, or WhatsApp. Legal experts told Nieman Lab the new terms would allow the scraping of news sites.
Two days later, Meta removed language from its commercial terms that had raised scraping and AI-training concerns. The changes did not end the pressure. The News/Media Alliance sent a letter to Meta CEO Mark Zuckerberg demanding that the company revise its business terms, citing severe harm to publishers.
The pressure moved to regulators on October 22. Digital advertisers and publishers in the European Union and the United Kingdom lobbied antitrust regulators to suspend Meta Platforms' new commercial terms, and urged those regulators to force the company to halt them. The delay now gives the EU and UK authorities time to weigh that request before the terms take effect.
The mechanism is what makes this difficult for publishers and their technical teams. Consent triggered by continued use of a platform is a different instrument from an opt-in, and a site operator who never signed a new agreement may still find its content covered. Robots.txt gives site owners a way to state their preferences, but the terms as reported would make that signal the main lever.
Engineers who manage crawl policies will want the specifics of Meta's user agents and how they are documented before deciding what to block.
In my view, the November 20 date matters less as a deadline than as a window. Meta has been given time to explain what is changing and what is not, and publishers, advertisers and regulators have the same time to test those explanations against the actual language. Whether the company's clarifications narrow the consent mechanism, or leave it intact with better documentation, will determine whether the dispute ends in a revised contract, a regulatory intervention, or a narrower set of crawl controls that site operators can rely on.
