Meta's new commercial terms were due on 30 October 2026. Meta has paused them. What a multi-brand group checks anyway

On 30 October 2026, Meta's new Commercial Terms were due to take effect, with one sentence giving Meta permission to crawl the websites associated with your business.

They did not take effect.

Meta moved the date to 20 November, then paused the whole update. On 6 November 2026 the live terms page still showed the version effective 6 March 2024, and I found no crawling clause in it.

I first read the preview on 21 October 2026. It was the third version of that sentence I had seen quoted in five days.

That is the complication. The clause everyone argued about moved while they argued, then the date moved, and a group that runs several brands still cannot answer "does this touch us" with one yes or no.

VALORAE runs three ventures and one upcoming line on separate domains. So the real question is narrower: which of our sites sit behind a Meta account used for business, and what would that account authorise if these terms come back.

This is how I worked it out.

Step 1: read the dates, not the headlines

Here is the sequence, each item with where I read it.

On 16 October 2026, Meta's communications lead Andy Stone posted on X that reports of a new crawling power were false, per PPC Land's write-up of 18 October 2026.

On 17 October 2026, The Verge reported that the training sentence "no longer appears" on the commercial terms page, again as PPC Land summarised it.

On 18 October 2026, PPC Land said a capture of Meta's preview still carried the sentence.

On 21 October 2026, the English preview I loaded at facebook.com/legal/commercial_terms_preview said Meta may use the content "to provide, develop, improve, research and maintain" its products. I searched it for the word train and found nothing.

On 23 October 2026, PPC Land reported that a Meta spokesperson told Reuters the effective date was moving to 20 November.

And on 5 November 2026, 404 Media quoted Meta's business help page: "These updates are now paused and will not take effect on November 20, 2026." The same report quotes Meta saying its existing terms remain in effect.

Regulators and courts are in this too. Social Media Today reported on 2 November 2026 that a competition regulator had opened an investigation, and 404 Media reported a temporary court injunction. I have not read either document myself.

So the version you read depends on the day you read it. That is the whole reason this post carries dates on every line.

Step 2: find the clause that stayed put

The training word moved. The crawling permission did not.

In the 21 October preview, a business authorises Meta to use "automated software (such as web scrapers, bots, robots, spiders, crawlers and user agents)" on "the domains, web pages or URLs (and any content available through them) that are associated with your products or services."

That is the part a group should plan around if these terms return.

PPC Land reported on 23 October that the stated purpose had been narrowed to "advertising and business products". Nieman Lab reported on 26 October that no version of the terms included language about respecting robots.txt, though Meta says publishers can still block its crawler that way.

Crawling a site you link from your Page is not shocking on its own. Link previews and product catalogues have always needed it. But "associated with" is wide, and the preview did not list which domains count.

I would rather assume every domain an account points at is in scope than guess which ones Meta would skip.

Step 3: check whether you are doing "business use" at all

The preview only reached you if you use Meta for business or commercial purposes. It listed them.

Ads or marketing messages. Selling or listing products. Developing apps. Creating or using a product catalogue. Managing a Page. Managing a group for business purposes. Using any business product, such as Ads Manager or Meta Business Suite. Using measurement services.

"Managing a Page" is the one most small operators miss. You would not need to run a single ad to be inside these terms.

So I went down the official VALORAE footprint, the one published on the official profiles page, and asked one question per venture.

Step 4: map each venture to the accounts that point at it

VALORAE Arc, the group's short-form clipping agency for podcasts and founders, has public profiles on X, YouTube and LinkedIn. None of them is a Meta product, so Arc's site is not tied to the group through a Meta business account on that list.

Media has no social profile of its own. It runs other people's channels, which means the Meta accounts it touches belong to clients, and the sites associated with them are the clients' sites, not valoraemedia.com.

Cast lives on Discord, with one invite, discord.gg/valoraecast. No Meta account sits in front of it.

Shop is upcoming. Nothing has dropped, there is no date, and there is no catalogue to list anywhere.

That surprised me. I expected this exercise to turn up a mess.

It did not, and I am not going to pretend that was planning. The ventures ended up off Meta for their own reasons, mostly that a dead profile looks worse than a missing one.

But the map is the point, not the result. A group that does have a Page per brand should write down which domain each Page links to now, while nothing is at stake, because that list is what Meta would have your permission to crawl if these terms return.

Step 5: separate the client's acceptance from yours

This is where a services business has to be careful.

When VALORAE Media manages a client's Instagram or Facebook presence, the client is the one using Meta for business, and the client's site is the associated domain. The client would accept the terms by continuing to use the account.

The same goes when VALORAE Arc uploads a show's clips to Reels: if the account belongs to the show, the show's owner is the business user.

An agency should not accept terms on a client's behalf by default, and it should not be the one deciding whether a client stays on Meta for business.

So the honest move, once Meta sets a new date, is a short note to each client: the date, the clause, the link to the preview, and a plain sentence saying the decision is theirs. The 21 October preview treated continued business use after notice as acceptance, and the only alternative its text offered was to stop using Meta products for business purposes.

That is also why handing an agency delegated access instead of a password matters. VALORAE Media wrote that up in Never give your agency your password, and the logic carries over: the account owner should be the person who sees the notice.

Step 6: decide what you would do if the terms come back

Paused is not withdrawn.

Per 404 Media, Meta is still consulting and says it will share an update later. Wording that moved, and a date that moved twice, can move again.

So I wrote down the decision now, while nothing is at stake. If a training clause or a wide crawling clause returns in a version that takes effect, a group Page linking a group domain would have to be weighed against that clause, brand by brand, and nobody should be guessing on the morning it changes.

I do not know which way Meta will land. Nobody outside Meta does, and the people who said they did on 16 and 17 October contradicted each other within a day.

The group keeps a dated list of the outside rule pages it leans on, in the platform rules register. Meta's commercial terms are not on it, because nothing in them has changed. This post holds the reads instead: 21 October and 6 November 2026, and the next one comes when Meta posts an update.

The short version

Check the live terms page, because the version dated 6 March 2024 was still in force on 6 November 2026. Treat 30 October and 20 November as dates that did not happen. List which brand's Page points at which site before any new date lands. Treat every domain a business account links to as in scope if the crawling clause returns. Remember that managing a Page alone would have put you inside the business terms. Let each client decide for their own account, and send them the link. Re-read the terms whenever Meta posts an update, because the wording and the date have both moved.

We keep the group's own ledger at valoraehq.com.