October 29, 2026:

Meta is facing extreme criticism over updated business terms that could authorize the company to use automated tools to access websites operated by businesses with Facebook accounts.
Following objections from publishers, industry groups, and lawmakers, the company says it may postpone implementation again while it consults with industry representatives.
The proposed Meta website scraping policy has raised questions about content ownership, website access restrictions, and the protection of subscription-based journalism. Although Meta says it wants to address industry concerns before proceeding, the disputed contractual language remains in place.

The dispute centers on updated terms that give Meta permission to use automated software to access business websites for purposes related to its advertising and business products.
The language specifically refers to tools such as web scrapers, bots, robots, spiders, crawlers, and user agents.
According to the updated provisions, these tools may be used to access websites to provide, develop, improve, research, and maintain Meta’s advertising and business products.
Publishers are concerned that the wording could grant the company broad access to online content, including material protected by paywalls, registration requirements, or digital subscriber restrictions.
The concern extends beyond news organizations. Subscription-based creators and other businesses that rely on restricted content to generate revenue could also be affected by how the policy is interpreted and enforced.
For publishers, the central issue is whether maintaining a Facebook presence could expose their websites to automated access without a sufficiently clear way to refuse it.
Meta originally planned to introduce the updated terms on October 30. Following an initial wave of criticism, the company postponed implementation until November 20.
However, spokesperson Andy Stone subsequently indicated that the date could change again if consultations with publishers and industry representatives continue beyond the scheduled deadline.
Stone said Meta did not intend to make policy changes without a full consultation with industry groups and leaders. He also stated that the company would delay implementation if those discussions extended beyond November 20, adding that the existing terms would remain in effect in the meantime.
Despite that statement, the company’s published information still listed November 20 as the implementation date at the time described in the source material.
A possible postponement does not mean the proposed terms have been withdrawn. Nor does it establish that Meta has agreed to narrow the scope of its website scraping provisions.
As a result, publishers continue to face uncertainty about the policy’s final wording and when the changes might take effect.
According to Engadget, the proposed Meta scraping rules have drawn particularly strong objections from organizations representing publishers and digital content businesses.
One industry group described the change as “outrageous and probably illegal,” reflecting concerns that the updated provisions could weaken existing protections for online material. A group of Norway-based media outlets has also filed a lawsuit against Meta over the new terms.
A major point of contention is the potential treatment of paywalls and other technical restrictions. These measures allow publishers to limit access to paying subscribers, registered users, or authorized visitors.
California Senator Adam Schiff raised similar concerns in a letter addressed to Meta CEO Mark Zuckerberg. He argued that the updated provisions were unusually broad and could allow Meta to bypass technical measures that protect the economic interests of news organizations and subscription-based creators.
Schiff also criticized the lack of an explicit opt-out mechanism for businesses that want to retain their Facebook accounts while preventing the company from scraping their websites.
The dispute therefore involves more than automated data collection. It also concerns the balance between platform participation, publisher independence, and the ability of content owners to control access to their material.
Meta has said that its updated terms are not intended to target news websites and that it will respect website owners’ robots.txt preferences.
The robots.txt file is a widely used website instruction mechanism that tells automated crawlers which parts of a site they should or should not access. Website operators commonly use it to communicate their preferences to search engines and other automated services.
However, robots.txt is not the same as a technical access restriction or a legally enforceable contract. Its effectiveness depends partly on whether a crawler chooses to follow the instructions, while the legal implications of disregarding them depend on the circumstances and applicable law.
Schiff argued that the updated contractual terms should explicitly incorporate Meta’s commitment to respecting robots.txt signals. Without such language, he said, businesses would lack a reliable contractual safeguard for their online content.
The absence of an explicit reference to robots.txt in the disputed terms has therefore left publishers questioning whether Meta’s public assurances offer sufficient protection.
Although Meta has acknowledged the backlash and discussed further consultation, the company has not made substantial changes to the disputed terms in the account provided.
Earlier in the month, Meta removed the word “train” and added a reference to advertising and business products. These changes did not eliminate the provisions authorizing automated website access.
That distinction matters because the disagreement concerns both the purpose of data collection and the breadth of the permission being granted.
Even if Meta maintains that the policy is intended to support its advertising and business services rather than target news publishers, the contractual wording remains a major concern for organizations seeking clearer boundaries.
Meta had not immediately responded to questions about whether additional revisions were planned, according to the source material.
Meta’s next steps depend partly on the outcome of its promised consultation with publishers and industry representatives.
A further delay would provide additional time for discussions, but it would not necessarily resolve the underlying disagreement. Publishers are seeking clearer contractual protections, while Meta has said it wants to consult industry stakeholders before implementing the changes.
The key developments to watch are whether Meta formally changes the implementation date, revises the website scraping provisions, explicitly addresses robots.txt, or introduces a mechanism allowing businesses to reject website scraping without losing their Facebook accounts.
The outcome could influence how businesses evaluate their relationship with social platforms and how publishers protect subscription-based content in an increasingly automated online environment.
Meta’s proposed business terms authorize the use of automated tools, including web scrapers and crawlers, to access business websites for purposes related to providing, developing, improving, researching, and maintaining its advertising and business products.
Publishers are concerned that the broad wording could affect their control over online content, including material protected by paywalls, registration requirements, and subscriber-only access restrictions. They also want a clear way to opt out while maintaining their Facebook accounts.
The original October 30 implementation date was postponed to November 20. Meta spokesperson Andy Stone indicated that implementation could be delayed again if industry consultations continued beyond November 20. The possibility of another delay was not confirmation of a revised date.
Robots.txt is a file website operators use to communicate instructions to automated crawlers. Publishers want Meta’s commitment to respecting these instructions explicitly included in its contractual terms, rather than relying solely on public assurances.
The reported changes included removing the word “train” and adding a reference to advertising and business products. The central provisions authorizing automated website access remained in place in the source material, and further changes had not been confirmed.