Skip to content
Primetra
All agents

Agent reference · User-triggered fetcher

meta-externalfetcher

Meta AI fetching a link for a person. Meta publishes no IP list, so we can name it but never prove it.

Vendor
Meta
Agent type
User-triggered fetcherFetch a page at the moment a person asks an assistant about it.
Can be verified by
Can't be verifiedThe vendor publishes nothing a visit can be checked against. A visitor using this name can be named, never proven.
How sure we are
DocumentedThe vendor's own documentation describes this agent.
Last reviewed
Vendor documentation
developers.facebook.com (opens in a new tab)

Tokens to look for

User-Agent tokens

Appear in the User-Agent header of its requests.

  • meta-externalfetcher

robots.txt tokens

No robots.txt token is documented for it.

Check a visitor claiming to be meta-externalfetcher

We've filled in its token. Paste the full User-Agent from your logs and the address it came from for a real answer.

Paste the full User-Agent header from your logs. A single token such as GPTBot works too.

Optional

IPv4 or IPv6, as your logs show it. Used only for this check and never stored. Without it, a claim can only come back as can't be verified.

What this means for your site

meta-externalfetcher arrives because a person asked about you, right now. A blocked or broken page here is a lost answer to a real question.

See whether AI agents can find your product, use it and, soon, pay for it.

Run the free agent-readiness check