CrawlPact

Meta · Agent / action crawler

Meta-ExternalFetcher

Fetches individual links at a user's request to support agentic AI capabilities in Meta products.

Verified against the operator's documentationQuestions and verification details checked

Questions about Meta-ExternalFetcher

Does Meta-ExternalFetcher follow robots.txt?

Meta says this crawler may bypass robots.txt rules, because it performs fetches a user requested. A Disallow rule for it is a published preference, not a reliable block.

Meta documents Meta-ExternalFetcher as a crawler that “fetches individual links at a user’s request” to support “evaluating and improving agentic AI capabilities — including helping AI navigate websites to complete tasks for users.” This is a user-directed, single-page fetch rather than a bulk crawl.

A note on the token

Meta’s own documentation writes the literal user-agent string in lowercase, meta-externalfetcher/1.1. robots.txt user-agent matching is case-insensitive (RFC 9309 §2.2.1), so this does not change how a Disallow rule applies.

A robots.txt limitation worth knowing

Meta’s own documentation states that this crawler “may bypass robots.txt because it performs fetches that were requested by the user.” A Disallow rule aimed at Meta-ExternalFetcher is therefore not a reliable way to prevent a specific page from being fetched on a person’s behalf — this is Meta’s documented position (wording checked against its crawler page on 2026-09-19), not a CrawlPact-observed workaround. See /limitations for what a robots.txt rule can and cannot guarantee more generally.

Site-owner controls

A robots.txt rule for Meta-ExternalFetcher may not be honoured, per Meta’s own documentation above — a single-page, user-directed retrieval, not a bulk crawl. It does not affect Meta-ExternalAgent (bulk AI-training crawling), Meta-WebIndexer (search), or Meta-ExternalAds (advertising validation), each of which Meta documents as a separate token.

Example robots.txt configuration

To disallow Meta-ExternalFetcher specifically, without affecting any other crawler:

User-agent: Meta-ExternalFetcher
Disallow: /

If no dedicated User-agent: Meta-ExternalFetcher group exists in a domain'srobots.txt, this crawler falls back to whatever the wildcard User-agent: * group says (RFC 9309) — see robots.txt syntax basics for how group selection works. A robots.txt rule is a published instruction; it does not technically prevent access.

Official source

https://developers.facebook.com/docs/sharing/webmasters/web-crawlers/

Verified against the source above as of 24 July 2026 — see how CrawlPact verifies crawler information.

Related guides

Other Meta crawlers

Other agent / action crawlers

See how this applies to your own site

Run a free audit to check your declared AI crawler policy against your own domain, or use the AI crawler checker to see how your robots.txt treats Meta-ExternalFetcher and every other documented crawler.

Analytics preferences

CrawlPact uses optional Google Analytics and Microsoft Clarity on public pages to learn which content is useful. Clarity records clicks and scrolling (session replay), with anything you type masked. Neither runs in the app or admin areas, and CrawlPact works the same whether you accept or decline. See the privacy policy.