AI crawler · registry

Meta-ExternalFetcher

Meta · Live retrieval · robots.txt token meta-externalfetcher

ignores robotsMeasured across 3,958 sites with a robots.txt policy record for this agent, out of 7,068 on record.
4%
of measured sites block it
154
sites blocking
3,804
sites allowing
no
honors robots.txt

What it is definition

Fetches individual links for agentic AI tasks; Meta documents that it may bypass robots.txt.

Meta-ExternalFetcher is operated by Meta and classified here as live retrieval. These agents fetch a single URL because a user asked about it. Disallowing one means the assistant answers from an older copy or from someone else's summary instead of the live page. Several are documented as not bound by robots.txt, because the request is user-initiated rather than a crawl.

Disallowing meta-externalfetcher stops the fetch that happens when a user asks Meta AI about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

Meta documents that this agent may fetch pages regardless of robots.txt. A disallow is recorded here because it states intent, but it is not the control.
robots.txt token
meta-externalfetcher
Operator
Meta
Purpose
Live retrieval
Honors robots.txt
no
Documentation
https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/

Identity on the wire exact string

User-agent string
meta-externalfetcher/1.1 (+https://developers.facebook.com/docs/sharing/webmasters/web-crawlers)
Verify your own edge is not refusing it
curl -A 'meta-externalfetcher/1.1 (+https://developers.facebook.com/docs/sharing/webmasters/web-crawlers)' https://example.com/

Replace the host with your own. A 403, a challenge page or an empty body means the edge is blocking the agent whatever robots.txt says.

How to allow it, how to block it robots.txt

Allow it
User-agent: meta-externalfetcher
Allow: /

Absent any rule, the agent is already allowed, so this group only matters when your * group disallows something. Naming the agent replaces the * group for it entirely, so repeat here every disallow you still want to apply to it.

Block it
User-agent: meta-externalfetcher
Disallow: /

Disallowing meta-externalfetcher stops the fetch that happens when a user asks Meta AI about one of your URLs. The answer still gets written, from an older copy or from a third party's description of the page, and you no longer control what it says.

robots.txt is not sufficient for this agent. Block by ASN at the edge. Meta's fetchers originate from AS32934, so one ASN deny rule covers the agent whatever user-agent string it sends, which a header match cannot.

Sites that block it 60 shown

DomainAI access scoreRank
amazon.com 33 26
msn.com 34 62
amazonvideo.com 55 121
snapchat.com 63 125
nytimes.com 67 157
launchpad.net 49 260
amazon.co.uk 33 318
washingtonpost.com 41 353
bloomberg.com 53 358
amazon.de 33 377
amazon.co.jp 33 494
ft.com 52 519
wired.com 74 533
usatoday.com 55 552
uol.com.br 74 571
telegraph.co.uk 45 580
amazon.fr 33 609
amazon.co.za 33 623
dailymail.co.uk 63 627
amazon.ca 33 635
amazon.in 34 659
cnet.com 75 662
dailymail.com 63 681
primevideo.com 55 682
amazon.it 33 706
amazon.es 33 725
people.com 38 801
amazon.com.au 33 812
theverge.com 68 815
amazon.com.br 33 833
investopedia.com 38 913
genius.com 60 926
repubblica.it 77 942
theatlantic.com 68 980
theconversation.com 52 1,019
huffpost.com 82 1,027
amazon.com.mx 33 1,032
bfmtv.com 71 1,073
flashscore.com 67 1,074
nypost.com 73 1,083
pimpbunny.com 56 1,177
ad.nl 47 1,190
nu.nl 47 1,191
furaffinity.net 41 1,223
hln.be 47 1,251
huffingtonpost.com 82 1,275
actu.fr 76 1,286
f95zone.to 49 1,300
dw.com 37 1,305
iltalehti.fi 50 1,409
buzzfeed.com 58 1,442
ekstrabladet.dk 60 1,446
eenadu.net 73 1,456
artfight.net 39 1,550
flashscore.mobi 63 1,624
flashscore.fr 64 1,640
livescore.cz 63 1,676
newyorker.com 71 1,793
zdnet.com 61 1,831
wikihow.com 72 1,835

Compare Meta

Meta runs 6 agents in this registry, and they do different jobs. Blocking one says nothing about the others.

Common questions answered

Does blocking Meta-ExternalFetcher remove me from Meta AI?

Partly. Meta-ExternalFetcher fetches a page only when a user asks about it, so disallowing it does not delist you from Meta AI. It does mean the answer is composed without your live page, from a stale copy or a third-party summary. Meta documents this agent as not bound by robots.txt, so the disallow is a request rather than a control; see the blocking section for the edge rule that is.

How do I verify Meta-ExternalFetcher requests are genuine?

Meta's crawlers originate from AS32934, and Meta documents querying that ASN to obtain the current ranges. Map the source address to its ASN and check for AS32934. There is no published reverse DNS name.

Check your own site free

See whether your robots.txt admits Meta-ExternalFetcher today, and whether your edge agrees with it.