Meta blinked — a little. On October 23, 2026, the company told Reuters it would push the effective date of its updated Commercial Terms and Self-Serve Ad Terms from October 30 to November 20, 2026, giving itself more time “to explain to our partners and stakeholders what’s changing and what’s not.” Here is what the delay does not do: it changes none of the wording. The crawling clause that publishers spent two weeks objecting to is still in the terms, still scheduled to take effect, and still does not mention robots.txt. If you run a website and a Facebook Page, an Instagram business account, or ads on Meta’s platforms, you now have 25 days — from today, October 26 — to decide what you will do about it. This article gives you the timeline, the version-by-version comparison, and the checklist, so November 20 does not catch you unprepared.
The short version: what changed, and what did not
What changed: the date. The updated Commercial Terms and Self-Serve Ad Terms now take effect November 20, 2026 instead of October 30.
What did not change: the crawling language. Meta’s October 16 revision — which removed the word “train” and narrowed the stated purpose to “advertising and business products” — stands as the current text. The delay announcement said nothing about withdrawing the crawling clause or rewriting it again.
What Meta says the extra time is for: explaining its crawler practices and how content owners can use robots.txt to signal their preferences. Meta spokesperson Daniel Roberts told The Verge the delay would let the company lay out “how Meta uses web crawlers and the fact that content owners will still be able to use robots.txt to signal preferences.”
What publishers say is still missing: a contractual commitment. The News/Media Alliance, which says it represents more than 2,000 US publishers, wrote to CEO Mark Zuckerberg on October 22 asking Meta to withdraw the terms, and later told PPC Land that the terms do not explicitly require Meta to honor robots.txt signals. The Alliance also asked Meta to respond publicly by October 26 — today — so watch for that response as this story develops.
How we got here: the timeline
| Date | What happened |
|---|---|
| October 15, 2026 | Nieman Lab reports a new paragraph in Meta’s Commercial Terms authorizing automated software and test credentials to crawl domains associated with a business’s products or services, and to use that content to “provide, develop, improve, research, train, and maintain” Meta products. Legal experts call it a remarkable provision that could cover news publishers’ sites. |
| October 16, 2026 | Meta revises the language: the word “train” is removed and the stated purpose narrows to “advertising and business products.” Legal experts tell Nieman Lab the revision still permits broad scraping. |
| October 17, 2026 | TechCrunch reports the revision, quoting Meta’s statement that the crawling terms “only applied to our ads and business products” and that the change “does not change how Meta uses web crawlers.” |
| October 22, 2026 | The News/Media Alliance writes to Zuckerberg demanding the terms be revised, warning of severe harm to publishers. EU and UK publishers complain to antitrust authorities. |
| October 23, 2026 | Reuters reports Meta will delay the effective date from October 30 to November 20. The European Commission welcomes the delay; the European Publishers Council wants the terms suspended pending investigation. |
| October 26, 2026 | The News/Media Alliance’s requested deadline for a public Meta response. Today. |
| November 20, 2026 | The updated terms take effect, unless Meta changes them again. |
The pattern matters more than any single date. Meta has moved twice so far — once on wording, once on timing — and both moves came after public pressure. Neither move withdrew the clause. That is the frame for everything you do in the next 25 days: prepare as if the terms take effect as written on November 20, and treat any further Meta concession as a bonus, not a plan.
The three versions, side by side
This is the comparison most coverage skips, and it is the one that should drive your decision. Read the “what it means for you” column, not just the wording column.
| Version | What the text says | What it means for a site owner |
|---|---|---|
| Previous terms (effective March 6, 2024) | No crawling clause at all, according to PPC Land’s October 16 comparison. | Nothing in the old terms granted Meta crawling rights over your site. This is the baseline publishers keep pointing to. |
| Original October 2026 draft | Meta may use automated tools and test credentials to crawl domains, pages, or URLs associated with a business’s products or services, and use that content to “provide, develop, improve, research, train, and maintain” Meta products. | The broadest version. “Train” is explicit, the scope covers any associated domain, and the only opt-out is to stop using Meta’s business products entirely. |
| Revised October 16 version (current) | The word “train” is removed; the stated purpose is “advertising and business products.” The crawling permission itself — automated access to associated sites, including with test credentials — remains. | Narrower on paper, still broad in practice. Legal experts argue “develop” and “improve” can still cover AI-related uses, and the contract still does not mention robots.txt. |
| Delay announcement (October 23) | Effective date moves from October 30 to November 20. No text change. | You gain 21 extra days. You gain no new rights, no opt-out, and no contractual promise about robots.txt. |
The honest reading: the October 16 edit removed the most alarming word, not the mechanism. A site owner who reads only Meta’s statement — “this isn’t about scraping news sites” — and a site owner who reads only the contract text will reach different conclusions, and the contract is the document that would matter in a dispute. That gap between statement and text is exactly what the News/Media Alliance is asking Meta to close.
Robots.txt: what it can and cannot do for you
Robots.txt is the practical lever Meta itself named, so let us be precise about it. A robots.txt file sits at the root of your site and tells automated crawlers which paths they may visit. It is a widely followed convention, not a law, and its power depends on the crawler choosing to honor it.
What robots.txt can do: signal your preferences to well-behaved crawlers, including Meta’s crawlers if Meta honors the signal. It costs nothing, takes five minutes to write, and is reversible at any time. For most small sites, it is the right first step regardless of what else you decide.
What robots.txt cannot do: override a contract you accepted. This is the publishers’ central objection. Legal experts quoted in the Nieman Lab reporting argue that Meta could treat a signed commercial agreement as overriding a robots.txt signal — the terms grant the crawling right, and the terms say nothing about robots.txt. The Alliance’s letter makes the same point in plainer language: its members’ presence on Meta’s platforms “does not and cannot grant Meta the right to scrape, access, or use their owned content,” and the terms do not explicitly require Meta to honor robots.txt, registration walls, or paywalls.
What that means in practice: use robots.txt as a signal, not as a shield. If blocking Meta’s crawlers matters to you, robots.txt is where you start — but understand that the contract question is unresolved, and a robots.txt file alone does not settle it. Meta has also declined to say whether the test-credentials clause could reach content behind paywalls or login walls, which is another reason publishers are pressing for written answers rather than verbal assurances.
The decision tree: three options, honestly weighed
Every site owner with a Meta business presence faces the same three options. None of them is free, and pretending otherwise is how people make panicked decisions on November 19.
Option A: Keep your Meta presence and accept the terms
This is what most small businesses will do, and it is a defensible choice — if it is a choice, not a default. Meta’s platforms drive real traffic and real sales for millions of small businesses, and walking away from Facebook, Instagram, and WhatsApp over a terms clause is a bigger business decision than most coverage admits. If you choose this option, do it deliberately: note the date the terms take effect, keep your robots.txt signals in place, and keep records of what Meta said publicly about its crawler practices. If Meta later changes its crawler behavior, a dated record of its statements is worth more than a vague memory.
Choose this option if: Meta drives a meaningful share of your traffic or sales, your content is mostly public marketing material rather than licensed or paywalled journalism, and you have no contractual obligations to anyone else about where your content may appear.
Option B: Block Meta’s crawlers in robots.txt
Add Meta’s crawlers to your robots.txt and keep your Meta presence otherwise unchanged. This is the middle path: you keep the traffic channel while signaling that your site content is not open for automated collection. The honest limitations: robots.txt is a signal, not a contractual opt-out; it does not change the terms; and it may affect how Meta’s tools preview or fetch your links, so test your link sharing after you change it.
Choose this option if: you want a visible, reversible record of your preference, you are uncomfortable with the crawling clause but cannot afford to leave Meta’s platforms, or you publish original content you license to others and want to avoid any appearance of granting Meta free access to it.
Option C: Leave Meta’s business products
The terms’ own logic points here: businesses that object “may stop all access or use” of Meta’s products for business purposes. For a publisher whose entire catalog could fall under the clause, that is the clean legal exit. For most small businesses, it is also a severe one — it means closing the Page, stopping ads, and losing the messaging channel customers use. Do not choose this option in a panic, and do not choose it without a replacement plan for the traffic and customer contact you would lose.
Choose this option if: your content is your core licensed asset, your contracts with licensors or subscribers restrict third-party access, or your legal counsel advises that accepting the terms creates a conflict you cannot accept.
There is no fourth option in the current text — no checkbox, no per-site opt-out form, no “crawl my product pages but not my articles” setting. The Alliance’s letter asks Meta to create exactly that kind of separate opt-in, unbundled from business-account access. Until Meta offers one, the decision tree above is the real menu.
Copy-paste robots.txt: the middle path, done properly
If you pick Option B, here is what to add. Put this in the robots.txt file at the root of your domain (for example, https://yoursite.com/robots.txt). Keep your existing rules; add these lines at the end. The snippet below covers the widely documented Meta crawler names — check Meta’s current crawler documentation before November 20, because crawler names are the kind of detail that quietly changes.
User-agent: meta-externalagent
Disallow: /
User-agent: facebookexternalhit
Disallow: /
Two cautions. First, facebookexternalhit is also the crawler that fetches link previews when someone shares your URL on Facebook or Instagram — blocking it can break or degrade how your links display when shared. If link previews matter to your traffic, test a share after adding the block and decide whether the trade-off is worth it for you. Second, after editing robots.txt, verify the file loads at your domain root and that you have not accidentally disallowed everything for every crawler — a single misplaced Disallow: / under User-agent: * will block Google too, and that is a self-inflicted wound no terms clause can match.
Your 25-day checklist: October 26 to November 20
Work through this in order. It is deliberately front-loaded with the free, reversible steps, so the hard decisions come last and with full information.
This week (October 26 – November 1):
- Watch for Meta’s response to the News/Media Alliance’s October 26 deadline. If Meta answers publicly, read the actual text, not the headline summary.
- Find out which Meta business products you actually use — Page, Instagram business account, ads, WhatsApp Business, Threads. The terms cover commercial use across Meta’s products, so an account you forgot about still counts.
- Check your current robots.txt file. Most WordPress sites either have a minimal one or none at all. Know what yours says today before you change it.
- Read the current terms text yourself, or at least the crawling paragraph. Second-hand summaries — including this article — are no substitute when the dispute is about wording.
Week two (November 2 – 8):
- Decide between Options A, B, and C above, and write the decision down with the date. A dated note turns a drifted default into a deliberate choice you can revisit.
- If you chose Option B, add the robots.txt rules and test link sharing on Facebook and Instagram afterward.
- If you run ads, check whether your ad account notices mention the new terms and whether any acceptance click is required. Do not click an acceptance you have not read.
- If you license content to others or publish behind a paywall, flag the terms to whoever handles your licensing — this is the group with the most at stake, and they may need legal advice you cannot give yourself.
Week three (November 9 – 15):
- Re-check Meta’s crawler documentation and any new statements. Meta promised explanations during the delay window; this is when they should arrive.
- If you chose Option C, start the exit now — not on November 19. Export your Page data, save your ad history, and tell customers where else to find you.
- Revisit the decision if Meta publishes new wording. A further revision resets the analysis; do not let an October decision ride on November text.
Final days (November 16 – 20):
- Confirm your robots.txt is live and correct, or confirm your acceptance decision, and record it.
- On November 20, note whether the terms took effect as written or changed again. If they changed, the checklist starts over — that is the nature of platform terms now.
What to watch after November 20
Three things will tell you whether this delay was a pause or a turning point. First, whether the European Commission or UK regulators open a formal process — the European Publishers Council has already asked for suspension pending investigation, and a regulator’s timetable moves slower than a news cycle but further than a press statement. Second, whether Meta puts its robots.txt assurances into the contract text itself, which is the specific change the Alliance asked for and the one that would actually settle the signal-versus-contract question. Third, whether other platforms follow Meta’s template — a crawling clause bundled into business terms, accepted by continued use, is a pattern that only needs one successful precedent to spread.
I have written about Meta’s terms twice before on this site — first when the crawling language surfaced, then when Meta softened it — and the lesson of both pieces is the same one this delay teaches: platform terms are no longer background paperwork. They are product decisions, made on a schedule you do not control, with consequences for content you created. The 25 days Meta just gave you are not a reprieve to ignore. They are the window in which a small site owner can still make a deliberate choice instead of an accidental one.
For the earlier chapters of this story, see our coverage of Meta’s original crawling terms and the October revision that removed the word “train”. Read them together with this piece and you have the full record: what Meta first proposed, what it changed under pressure, and what the delay leaves unresolved.
Frequently Asked Questions
When do Meta’s new Commercial Terms take effect?
November 20, 2026. Meta moved the date from October 30 on October 23, 2026, after publishers and advertisers complained to EU and UK regulators. The wording of the terms did not change with the delay.
What do the terms actually allow Meta to crawl?
Under the current (October 16) revision, Meta’s terms permit automated crawling of domains, pages, or URLs associated with a business’s products or services, for use in “advertising and business products.” The original draft also included the word “train”; that word was removed, but legal experts argue the remaining language is still broad.
Does robots.txt block Meta under the new terms?
Not contractually, according to the publishers objecting to the terms. Robots.txt signals your crawling preferences, and Meta says content owners can still use it to signal preferences — but the terms themselves do not mention robots.txt and do not explicitly require Meta to honor the signal. Treat robots.txt as a signal, not a guaranteed opt-out.
Can I opt out of the crawling clause while keeping my Facebook Page?
No, under the current text there is no per-site opt-out. The terms’ position is that businesses that disagree may stop using Meta’s products for business purposes. The News/Media Alliance has asked Meta to create a separate opt-in for scraping, unbundled from business-account access, but Meta has not offered one.
What should a small business do before November 20?
Decide deliberately among three options: keep your Meta presence and accept the terms, add Meta’s crawlers to your robots.txt while keeping your presence, or leave Meta’s business products. Work through the checklist in this article, record your decision with the date, and re-check Meta’s statements in the final week before the deadline.
Does this affect personal Facebook or Instagram accounts?
The contested terms are Meta’s Commercial Terms and Self-Serve Ad Terms, which cover business use of Meta’s products — Pages, business accounts, and advertising. Personal, non-commercial use is not the focus of the publisher objections, but if you use a business account, the terms apply to you.