All posts
2 min readby Romiel Inolino

Meta removed a terms clause that let it use content from business websites for training. Check what your clients' ad accounts agree to

MetaAI policydigital marketingrobots.txtclient operations

If your clients run ads on Meta, their business account just agreed to new terms. Someone should read them.

What happened

Meta consolidated its commercial terms for business accounts that promote content across Facebook, Instagram, WhatsApp and Messenger, with the new terms taking effect on October 30, according to The Verge. The text authorized Meta to use automated software, and to create test credentials, to crawl the domains and pages associated with a business's products or services, and to periodically pull updates. One sentence went further: Meta "may use any content from such domains, web pages, or URLs to provide, develop, improve, research, train" its products.

Legal experts quoted by Nieman Lab, as reported by The Verge and Ars Technica, read that as permission to train AI on business and publisher websites, possibly overriding robots.txt. Ars reported there was no opt out: businesses that do not agree may have to stop using Meta's products commercially. Meta's Andy Stone said the change was meant to pull accurate product information from third party sites for ad and content recommendations.

After the backlash, The Verge reports Meta removed the "may use any content" sentence. Meta's statement says the crawling terms only apply to its ads and business products, that it does not change how Meta uses web crawlers, and that content owners can use robots.txt to signal their preferences.

My take

Most small businesses never read platform terms. Their marketing contractor clicks accept. If you manage ad accounts or websites for clients, you are the closest thing they have to a terms reviewer.

A practical routine:

  1. Know which client domains are attached to Meta business accounts. Those are the sites the crawling language covers.
  2. Review robots.txt on those sites. Meta points to it as the control, so make sure it says what the client actually wants.
  3. Keep anything private behind real login, not just an unlinked URL.
  4. Log vendor terms changes. A simple automation that watches the terms pages of the platforms in a client's stack and alerts you on change is cheap to build.

The clause is gone, but the pattern will repeat with other platforms. Have the check in place before the next one.

More posts