meta-externalads

Meta · Training claims robots compliance checked — limited vendor docs

What it does

meta-externalads is Meta's training crawler. Content is copied into datasets used to train foundation models. Blocking costs you nothing in traffic today; allowing is a donation of your content to model weights with no citation or referral in return.

Meta's docs: 'crawls the web for use cases such as improving advertising and other business-related products.' Product-improvement crawl, not foundation-model training — filed under training as the closest bucket (same reasoning as Amazonbot). New on the vendor roster since our 2026-07-19 snapshot.

Full UA: not captured in our July 2026 roster review — match log hits on the token meta-externalads (case-insensitive substring) and verify by IP before acting.

How to verify a hit is really meta-externalads

Verification method (July 2026): Meta ASN 32934 (RDAP/whois); no published IP list. Docs fetched live 2026-08-22

No per-crawler IP list is published; the practical check is network ownership — look up the hit's source IP via RDAP/whois and confirm it announces from the vendor's network (ASN) rather than a residential proxy or cloud range.

User-agent strings are freely spoofed, so a UA match alone proves nothing. Full step-by-step method: verify by IP.

Allow or block in robots.txt

Match the exact token meta-externalads in robots.txt:

# Block meta-externalads site-wide
User-agent: meta-externalads
Disallow: /
# Explicitly allow meta-externalads
User-agent: meta-externalads
Allow: /
Compliance is claimed, not independently confirmed. Meta states this bot respects robots.txt; treat the directive as the first line of defense and watch your logs after deploying it.

For the allow-search-block-training combined pattern (and the Allow-directive gotcha that silently kills carve-outs), see the robots.txt guide. robots.txt governs whether meta-externalads may fetch; llms.txt is the separate, curated map AI assistants read once allowed in.

Vendor documentation: https://developers.facebook.com/docs/sharing/webmasters/web-crawlers

The Meta family

Meta operates 4 distinct tokens in this roster, and they do not block each other: a robots.txt line for meta-externalads does nothing to its siblings — each needs its own User-agent: entry (the robots.txt guide has combined patterns).

TokenRolerobots.txt
meta-externalagentTrainingclaims robots compliance
meta-externalfetcherUser actionignores robots.txt
meta-webindexerAI searchclaims robots compliance

Frequently asked questions

What is meta-externalads?

meta-externalads is Meta's training crawler. Content is copied into datasets used to train foundation models. Blocking costs you nothing in traffic today; allowing is a donation of your content to model weights with no citation or referral in return.

Does meta-externalads respect robots.txt?

Meta claims meta-externalads respects robots.txt, but compliance is not independently confirmed.

How do I block meta-externalads?

Add 'User-agent: meta-externalads' followed by 'Disallow: /' to your robots.txt. Use the exact token — substring variants of other tokens will not match.

How do I verify meta-externalads traffic by IP?

No per-crawler IP list is published; look up the source IP via RDAP/whois and confirm it announces from Meta's network before trusting the user agent.

Related bots

Same vendor, then other training crawlers — the full directory profiles all 34.

AnswerFootprint crawler analytics — bot roster compiled July 2026 from vendor crawler docs and published IP lists (25/34 vendor-doc verified). The analyzer runs 100% client-side — your logs never leave this browser. User-agent strings can be spoofed; treat UA matches as a first pass and verify by IP before acting. Errors in the bot data: report them.