Meta · Other AI
meta-externalads
One sentence is the entire published description: crawling “for use cases such as improving advertising and other business-related products and services.” There is no trigger, no cadence, no named product and no stated relationship to anything a user does, so what can be said with confidence is negative: it is not the link-preview path, not the Meta AI citation index, and not the model-training sweep. It arrived alongside meta-webindexer in the doc expansion that took Meta's published lineup from two crawlers to five between January 2025 and January 2026. Do not read it as Microsoft's AdIdxBot wearing a different badge: that token has a documented quality-control purpose, this one has a sentence.
- Operated by
- Meta
- Purpose
- Other AI
- robots.txt token
- meta-externalads
- Verification
- Network origin only
AI-adjacent traffic that does not fit the three purposes above.
How to verify meta-externalads
We hold no list of IP addresses that Meta publishes itself for meta-externalads. What we hold instead is 574 prefixes that a third party (a public routing record, not Meta) reports Meta's network announcing. A request from inside one of those tells you where it came from, not who sent it: anything else on that network can send the same packet, and nothing we hold ties meta-externalads to those addresses beyond the network they sit on. A request from OUTSIDE them is not thereby a fake either: this describes one network's announcements, not every address Meta can crawl from. Corroboration, not proof.
We hold no range list Meta publishes itself for meta-externalads, so there is no such fetch to confirm. This entry was last reviewed against Meta's own documentation on .
User agent
Meta publishes this user agent for meta-externalads. Match on the meta-externalads product token rather than the whole string: vendors revise the surrounding version and URL fragments without notice.
meta-externalads/1.1 (+/documentation/sharing/webmasters/web-crawlers)robots.txt for meta-externalads
Yes. No exception is claimed for this token: only meta-externalfetcher and facebookexternalhit carry bypass language on Meta's page.
Block
User-agent: meta-externalads
Disallow: /Allow
User-agent: meta-externalads
Allow: /robots.txt is a request, not an enforcement mechanism. It is honoured by convention, and a crawler that ignores it is stopped at your edge, not in a text file.
What blocking meta-externalads costs you
Cheapest of the Meta set, and honestly so, because Meta names no surface that degrades. If you buy Meta ads pointing at your own site, the plausible loss is ad-quality and landing-page signals derived from crawling that destination: plausible, and nowhere documented by Meta. Without a Meta advertising relationship there is no identified downside at all, and no way to audit what you turned away either: the geofeed at `facebook.com/peering/geofeed` is an RFC 8805-style geolocation file published for CDN routing, and it identifies no crawler.