Meta-ExternalAgent is the specific user-agent string used by Meta's autonomous crawler to identify itself when accessing public web content. Its primary purpose is to gather data for training and improving Meta's foundation models, such as the Llama family, and to power generative AI features across its platforms. Website administrators can target this token in robots.txt to explicitly control whether their content is ingested for Meta's AI development pipelines.
Glossary
Meta-ExternalAgent

What is Meta-ExternalAgent?
Meta-ExternalAgent is the user-agent token for Meta's web crawler that accesses public websites to collect training data for its AI models, including Llama, and for use in its generative AI products.
This crawler is distinct from Meta's traditional search indexing bots. Blocking Meta-ExternalAgent via the Robots Exclusion Protocol prevents a site's data from being used in future model training runs, but it does not affect how content appears in standard search results. Properly configuring directives for this token is a critical component of an enterprise AI Training Opt-Out strategy and broader Crawl Consent Management.
Key Characteristics of Meta-ExternalAgent
Meta-ExternalAgent is the user-agent token for Meta's proprietary web crawler, designed to access publicly available internet content for training and improving its family of AI models, including Llama, and for use in its generative AI products.
User-Agent Identification
The full user-agent string is Meta-ExternalAgent/1.1 or similar versioned variants. It identifies itself in HTTP request headers, allowing web infrastructure engineers to write targeted directives in robots.txt to control its access. This token is distinct from Meta's social media scraper (facebookexternalhit), which is used for link previews on its platforms.
Primary Purpose: AI Training Data
Meta-ExternalAgent crawls the open web to collect publicly accessible text, images, and other media. This data is used to:
- Pre-train and fine-tune Meta's Llama family of large language models.
- Ground responses in Meta AI, its generative assistant integrated across Facebook, Instagram, and WhatsApp.
- Improve multimodal models by ingesting diverse content types. It does not access content behind logins or paywalls.
Robots.txt Control
You can block Meta-ExternalAgent from your entire site or specific paths using the standard Robots Exclusion Protocol. Add the following to your robots.txt:
codeUser-agent: Meta-ExternalAgent Disallow: /
For partial access, specify allowed or disallowed directories. Meta respects these directives and will cease crawling disallowed paths after re-processing your robots.txt file.
IP Range and Verification
Meta-ExternalAgent crawls from a published set of IP ranges. You can verify legitimate Meta traffic by performing a reverse DNS lookup on the connecting IP, which should resolve to a *.fbsv.net hostname, and a corresponding forward DNS lookup that matches the original IP. Always verify against Meta's official documentation for the current IP list to prevent user-agent spoofing.
Crawl Behavior and Frequency
The crawler is designed to be polite and rate-limited. It respects the Crawl-Delay directive in robots.txt if specified. Meta-ExternalAgent fetches robots.txt periodically and caches it. Changes to your directives may not take effect immediately. It supports HTTP/1.1 and HTTP/2, and typically crawls with a moderate, distributed frequency to avoid overwhelming origin servers.
Opt-Out and Data Rights
Blocking Meta-ExternalAgent via robots.txt is the primary technical mechanism for opting out of having your public content used for Meta's AI training. Meta has also introduced a data subject rights form for users in certain jurisdictions to object to their personal data being used for AI training. This is separate from the crawler-level block and addresses data already ingested.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Essential technical answers about Meta's AI training crawler, its behavior, and how to control its access to your web content.
Meta-ExternalAgent is the official user-agent token for Meta's web crawler that systematically accesses public web content to collect training data for its AI models, including the Llama family of large language models, and to power generative AI features across Meta's products. The crawler operates by sending HTTP requests to publicly accessible URLs, downloading page content, and processing the text, images, and structured data for ingestion into Meta's training pipelines. It respects standard robots.txt directives and identifies itself with the Meta-ExternalAgent user-agent string in its request headers. Website operators can verify its identity by cross-referencing its IP ranges, which Meta publishes, against their server logs to distinguish legitimate Meta crawling from spoofed traffic.
Related Terms
Understanding Meta-ExternalAgent requires context within the broader landscape of AI crawler directives and the specific agents they control.
AI Crawler Agent
An autonomous web crawler, identified by a specific user-agent token, deployed by an AI company to collect training data or ground generative responses from the public web. Meta-ExternalAgent is a specific instance of this broader category.
- Purpose: Training foundation models like Llama.
- Identification: Uses the
Meta-ExternalAgenttoken inrobots.txt. - Function: Systematically browses the web to download publicly accessible content.
Robots Exclusion Protocol
The standard protocol (robots.txt) used by websites to communicate with web crawlers and specify which parts of the site should not be accessed. This is the primary mechanism for controlling Meta-ExternalAgent.
- Directive:
User-agent: Meta-ExternalAgent - Action:
Disallow: /to block completely. - Granularity: Can block specific directories while allowing others.
AI Training Opt-Out
The technical and policy mechanisms that allow website owners to signal their preference that their content not be used for training foundation models. Blocking Meta-ExternalAgent via robots.txt is the standard opt-out method.
- Mechanism:
robots.txtdisallow rule. - Scope: Prevents future training data ingestion.
- Limitation: Does not remove data already scraped.
GPTBot
OpenAI's specific web crawler user-agent token, functionally equivalent to Meta-ExternalAgent but for OpenAI's ecosystem. Both are managed through identical robots.txt directives.
- Token:
GPTBot - Owner: OpenAI
- Purpose: Training models like GPT-4 and ChatGPT.
Google-Extended
A standalone product token used in robots.txt to specifically control whether Google's crawlers can use a site's content for training its generative AI models, including Bard and Vertex AI.
- Token:
Google-Extended - Difference: Separate from the main
Googlebotsearch indexer. - Control: Allows search indexing while blocking AI training.
Crawl Transparency Report
A public or private document detailing a website's interactions with AI crawlers like Meta-ExternalAgent, including access frequency, data ingested, and compliance with directives.
- Purpose: Auditing and governance.
- Contents: Crawl frequency, bytes downloaded,
robots.txtcompliance. - Value: Verifies that opt-out directives are being respected.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us