Meta-ExternalFetcher
Meta · Live retrieval · robots.txt token meta-externalfetcher
2% of 30,177 measured domains disallow meta-externalfetcher in robots.txt at the site root. Separately, and independently of robots.txt, 17.4% of 30,187 reachable domains refuse an AI crawler user agent at the network edge on two consecutive probes from different locations - a refusal the site's own robots.txt does not declare and its owner often has not chosen.
Measured 2026-10-06 by direct request to every domain in the corpus. Method: how this is measured. Reuse under CC BY 4.0 with attribution.
Cite as: Crawl Census, "Meta-ExternalFetcher blocking rate", measured 2026-10-06. https://crawlcensus.com/bot/meta-externalfetcher
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.
- 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
meta-externalfetcher/1.1 (+https://developers.facebook.com/docs/sharing/webmasters/web-crawlers)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
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.
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.
Sites that block it 60 shown
See every measured domain that blocks Meta-ExternalFetcher
This list is served from a cache rebuilt just now. It is discarded the moment a rescan records a policy change for this agent, so a site that has just changed its robots.txt will drop off it within one scan rather than waiting for the cache to expire.
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.