meta-externalagent: robots token, verification and how to allow or disallow it
meta-externalagent is an AI crawler operated by Meta. Its robots.txt token is meta-externalagent, and the vendor documentation we fetched on 2026-09-06 is the source for every statement on this page.
| Robots token | meta-externalagent |
|---|---|
| Vendor | Meta |
| Purpose | training corpus, search index |
| Documented verification | none published |
| Vendor documentation last verified | 2026-09-06 |
| Share of read domains disallowing it for / | 16.4% of 128 |
| Last verified |
Identity
| Robots token | meta-externalagent |
|---|---|
| Matched as | meta-externalagent |
| Vendor | Meta |
| Purpose | training corpus, search index |
| Documentation | https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/ |
| Documented verification | none published |
The vendor page fetched on 2026-09-06 carries the exact snippet 'User-agent: meta-externalagent Allow: / # Allow everything Disallow: /private/ # Disallow a specific directory', asks for up to 24 hours for a robots.txt change to take effect, and notes that its integrity and security checks may not follow robots.txt.
Allow or disallow it
User-agent: meta-externalagent Allow: /
User-agent: meta-externalagent Disallow: /
A robots.txt rule is a request that a well behaved crawler honours. It is not an access control, and this page does not tell anyone what to choose.
Questions
Does meta-externalagent obey robots.txt?
The vendor documentation at https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/ states that meta-externalagent respects robots.txt. We fetched that page and it answered our checker on 2026-09-06. This records what the vendor documents, not what any individual request did.
How do I allow meta-externalagent in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: meta-externalagent Allow: /. The token is matched case insensitively as a substring of the user agent by RFC 9309, and the longest matching rule wins.
How do I disallow meta-externalagent in robots.txt?
Add this group to the robots.txt at the root of the host: User-agent: meta-externalagent Disallow: /. A robots.txt rule is a request that a well behaved crawler honours; it is not an access control.
How do I verify a request really came from meta-externalagent?
We have not found a documented verification method for meta-externalagent: the vendor publishes neither an IP range file nor a reverse DNS convention that we could fetch. Without one, a user agent string is not evidence of origin.
What we measure
Of the 128 seeded domains whose robots.txt we have read, 21 disallow meta-externalagent for / and 107 allow it, which is 16.4% disallowed, week 2026-W37. Counts only: no domain is named.
The weekly AI crawler access index
Sources
| Source | Type | HTTP | Verified | Note |
|---|---|---|---|---|
| https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/ | vendor | 200 | 2026-09-06 | served as text/markdown; 5 occurrences of meta-externalagent |
| https://darkvisitors.com/agents/meta-externalagent | aggregator | 200 | 2026-09-06 | corroboration only; volatile source: identical byte count but a different content hash on every fetch (verified twice on 2026-09-06), so the refresher compares byte counts for it, not hashes |
Free data
Check a domain against every token
AEO Watch is an independent, factual monitor. It is not affiliated with, endorsed by or speaking for any crawler vendor. Every statement is an observation with the date it was made and the raw evidence behind it: a robots.txt line, an HTTP status code, a header. There are no scores, no grades and no verdicts here, and nothing on this page is advice. A site opts out at any time and the opt out is honoured automatically and permanently.