resulthack

All AI crawlers /

Meta-ExternalAgent

Meta · Training · robots.txt: Yes

Crawls the web for uses such as training Meta's foundation AI models or improving Meta products by indexing content directly.

Block Meta-ExternalAgent

User-agent: Meta-ExternalAgent
Disallow: /

Unconfirmed by the operator Meta's documentation we checked does not say what blocking Meta-ExternalAgent changes beyond the crawler itself.

Allow Meta-ExternalAgent

User-agent: Meta-ExternalAgent
Allow: /

An allow group only changes anything if a broader rule would block Meta-ExternalAgent. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.

Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.

Block or allow it at the server

robots.txt asks; a server rule refuses. Every rule here matches meta-externalagent, spelled as in the User-Agent Meta documents (“meta-externalagent/1.1”), and matches it case-sensitively. The server answers 403.

What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user. (Apache HTTP Server 2.4 documentation). A fake Meta-ExternalAgent is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Meta's published addresses.

Your server

To block it: refuse every request that says Meta-ExternalAgent

In the server block (or a location)

if ($http_user_agent ~ meta-externalagent) {
    return 403;
}

The geo and map blocks go at http level; nginx's docs give Context: http for both, and for if Context: server, location. By default, the address is taken from the $remote_addr variable (nginx documentation).

To block it: refuse every request that says Meta-ExternalAgent

In the virtual host, a <Directory> block or .htaccess

<If "%{HTTP_USER_AGENT} =~ /meta-externalagent/">
    Require all denied
</If>

Apache httpd 2.4. Syntax: <If expression> ... </If> Context: server config, virtual host, directory, .htaccess (Apache HTTP Server 2.4 documentation). Several Require ip lines in one block: When multiple Require directives are used in a single configuration section and are not contained in another authorization directive like <RequireAll>, they are implicitly contained within a <RequireAny> directive. (Apache HTTP Server 2.4 documentation)

To block it: refuse every request that says Meta-ExternalAgent

Inside the site block

@meta-externalagent header User-Agent *meta-externalagent*
respond @meta-externalagent 403

Like directives, named matcher definitions must go inside the site blocks that use them. (Caddy documentation) On client_ip: This matcher is best used when the trusted_proxies global option is configured, otherwise it acts identically to the remote_ip matcher. (Caddy documentation)

To block it: refuse every request that says Meta-ExternalAgent

Expression of a custom rule; action Block

(http.user_agent contains "meta-externalagent")

Each expression is one custom rule with the action Block (Cloudflare's own example: Expression: (cf.bot_management.score lt 2 and http.user_agent contains "App_Name 2.0") Action: Block).

No “only the real one” rule: Meta publishes no IP list file this site holds for Meta-ExternalAgent.

The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.

Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.

Who blocks it

Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 66 block Meta-ExternalAgent from the whole site by name, 29 block it through their User-agent: * group, and 16 name it with partial rules (some paths closed, the home page open). 1 more name it only to let it in.

66

block it by name 13.0%

29

block it through * 5.7%

16

name it, partial rules 3.1%

Percentages are of the 508 files we could read, not of all 1,000 sites.

Highest-ranked sites that block Meta-ExternalAgent by name

  1. twitter.com rank 16
  2. amazon.com rank 27
  3. x.com rank 48
  4. tiktok.com rank 58
  5. msn.com rank 72
  6. amazonvideo.com rank 111
  7. snapchat.com rank 134
  8. tumblr.com rank 156
  9. nytimes.com rank 157
  10. t-online.de rank 201

Each links to the site's live robots.txt, which may have changed since 2026-10-09.

robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.

Facts

Operator
Meta
Purpose
Model training

Meta's wording is a mix: "training foundation AI models or improving products by indexing content directly".

Obeys robots.txt
Yes. Meta says to block its crawlers with a Disallow for the relevant crawler in robots.txt, and that robots.txt may be cached for up to 24 hours. Meta's own example writes the token in lower case (meta-externalagent).
In your server logs
The user-agent string contains "meta-externalagent/1.1".
How to verify it
Unconfirmed by the operator Meta's documentation we checked gives no IP list or DNS check for this crawler, so a request claiming to be Meta-ExternalAgent cannot be verified against the operator.

What Meta says

Quoted word for word from the operator's documentation.

“The Meta-ExternalAgent crawler crawls the web for use cases such as training foundation AI models or improving products by indexing content directly.”

“In order to block these crawlers, add a disallow for the relevant crawler to robots.txt.”

“Please allow up to 24 hours for changes to `robots.txt` to take effect because crawlers may cache the contents of `robots.txt` for up to 24 hours.”

“User-agent: meta-externalagent”

“`meta-externalagent/1.1`”

Sources

Other crawlers from Meta

Same purpose, other operators

← All 49 AI crawlers

Made with AI tools. · Privacy