Safe Reported Social Bots

Facebook Crawler

Q: What user-agent string does Facebook Crawler use?

Facebook Crawler is reported to identify itself with FacebookBot . Evidence that the spelling is in real use comes from our own robots.txt study: 395 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), not from Meta, which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.

Q: Is Facebook Crawler safe?

Facebook Crawler is rated Safe in this directory, meaning there are no credible public reports of abusive crawling under this name. It is a Reported token: Meta has not published documentation for it, so its purpose, crawl rate and robots.txt behaviour are not confirmed by the operator, and anyone can send the same user-agent string. Allow or block it on its stated purpose, and back the robots.txt rule with a firewall rule if the traffic matters to you.

Q: Will blocking Facebook Crawler hurt my SEO?

🔶 AI Visibility Trade-off - Blocking Facebook Crawler will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.

Q: How do I block Facebook Crawler in robots.txt?

Add the following lines to your /robots.txt file: User-agent: FacebookBot Disallow: / This instructs Facebook Crawler not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/ ).

Q: How do I verify if Facebook Crawler is crawling my site?

Search your access logs for FacebookBot (for example grep -i "FacebookBot" /var/log/nginx/access.log ). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that Meta sent it.

Operated by Meta

Scout's quick take

Facebook Crawler fetches your page to build the preview card when someone shares a link. Blocking it leaves shared links without a title or image. This profile is built from reported sightings, not vendor documentation.

# Block only if you really mean to
User-agent: FacebookBot
Disallow: /

Check my website crawlability Build a full robots.txt

Quick Facts

User-Agent:: FacebookBot
Category:: Social Bots
Operator:: Meta
Safety:: Safe
Blocking Impact:: Low - No SEO ranking impact
SEO Impact Score:: 2/10
Official docs:: None published by Meta
Evidence:: Verified by AI Crawler Check: in 395 top-10k robots.txt files

Reported, not operator documented

Meta has not published a crawler page that names FacebookBot. It is listed here on our own evidence. Verified by AI Crawler Check: 395 of the 5,583 valid robots.txt files in the Tranco top 10,000 carry a rule for FacebookBot, so site owners treat it as a real crawler name (how we measure this). That proves the spelling is in use, not who sends it. Historic Meta token. Meta's current crawler page no longer lists it; many robots.txt files still do.

What that means for you: the FacebookBot rule on this page is the best available spelling, but Meta has made no statement of purpose, crawl rate or robots.txt compliance. Treat a FacebookBot request in your logs as a clue, not proof of who sent it, and add a firewall rule if that traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.

What is Facebook Crawler?

Facebook Crawler is an AI crawler operated by Meta. It uses the user-agent string FacebookBot and follows the Robots Exclusion Protocol.

Facebook Crawler is an AI crawler operated by Meta. It uses the user-agent string FacebookBot and follows the Robots Exclusion Protocol.
Facebook Crawler uses the user-agent token FacebookBot. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Facebook Crawler?

🔶 AI Visibility Trade-off - Blocking Facebook Crawler will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.

Generally safe to allow; provides legitimate crawling value.

How to block Facebook Crawler with robots.txt

<code>User-agent: FacebookBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)

User-agent: FacebookBot
Disallow: /

Allow all (robots.txt)

User-agent: FacebookBot
Allow: /

Block private only (robots.txt)

User-agent: FacebookBot
Disallow: /private/
Disallow: /api/
Disallow: /admin/
Allow: /

Nginx server block

# Nginx: Hard-block Facebook Crawler
if ($http_user_agent ~* "FacebookBot") {
    return 403 "Bot blocked";
}

Apache .htaccess

# Apache: Hard-block Facebook Crawler
SetEnvIfNoCase User-Agent "FacebookBot" bad_bot
Order Allow,Deny
Allow from all
Deny from env=bad_bot

Meta robots tag

X-Robots-Tag header

X-Robots-Tag: noindex, nofollow

Is Facebook Crawler safe to allow?

Facebook Crawler is rated Safe in this directory, meaning there are no credible public reports of abusive crawling under this name. It is a Reported token: Meta has not published documentation for it, so its purpose, crawl rate and robots.txt behaviour are not confirmed by the operator, and anyone can send the same user-agent string. Allow or block it on its stated purpose, and back the robots.txt rule with a firewall rule if the traffic matters to you.

Meta publishes no IP ranges or reverse-DNS pattern for Facebook Crawler, so the user-agent string cannot be verified. Rate-limit unusual volume instead of trusting the name.

What does Facebook Crawler do?

Understanding Facebook Crawler's purpose helps you decide whether to allow or block it.

Indexes web pages for AI-powered search answers
Surfaces your content as citations inside AI search results
Builds a knowledge index used to answer user questions
Allowing it can increase visibility in AI search
robots.txt behaviour not documented by the operator

Facebook Crawler in context

Facebook Crawler is a utility crawler operated by Meta. In plain terms, it fetches a page to build a link preview when someone shares it. Our database files it under social preview bots and ranks it Tier 5, low-priority crawlers with limited upside for most sites. 8 of the 9 social preview bots in our database share this tier.

Its safety rating is safe and its blocking impact is not documented. So the decision about Facebook Crawler rests on what you want from Meta, not on its behaviour. How we rate safety and impact.

How site owners treat Facebook Crawler

In our own scan of the Tranco top 10,000 (5,583 valid robots.txt files), 395 files (7.1%) name FacebookBot in a User-agent line. That shows site owners treat the token as a real crawler worth a rule. It does not, on its own, prove who operates it.

Does it follow robots.txt?

Facebook Crawler's operator does not clearly document how it treats robots.txt. Write the Facebook Crawler rule anyway, then confirm in your logs that its requests stop.

Meta crawlers and close alternatives

Facebook Crawler is one of 8 Meta crawlers in our database. A User-agent: FacebookBot group controls Facebook Crawler only; the other Meta tokens below need their own lines.

FacebookBot: this crawler (Tier 5)
facebookexternalhit: Facebook Preview, fetches a page to build a link preview when someone shares it (Tier 5)
Meta-ExternalAds: Meta Ads Crawler, checks pages for an SEO, uptime or analytics service (Tier 4)
Meta-ExternalAgent: Meta AI Training, collects pages to train AI models (Tier 1)
Meta-ExternalFetcher: Meta AI Fetcher, fetches a page when a person asks an assistant or app to open it (Tier 2)
meta-externaltest: Meta-ExternalTest, checks pages for an SEO, uptime or analytics service (Tier 4)
meta-webindexer: Meta Web Indexer, builds a search or answer index (Tier 2)
muse-: Meta Muse (personal agent), fetches a page when a person asks an assistant or app to open it (Tier 1)

To give Facebook Crawler the same answer as its siblings, stack User-agent: FacebookBot with their lines above one set of rules; to treat Facebook Crawler differently, give it its own group.

Other social preview bots that do the same job (fetches a page to build a link preview when someone shares it) include LinkedInBot from LinkedIn, Pinterestbot from Pinterest, Quora-Bot from Quora, Slackbot from Slack, Slackbot-LinkExpanding from Slack, Twitterbot from X (Twitter). Deciding about Facebook Crawler is usually a decision about the whole group, so check how your file treats these too.

We first recorded FacebookBot on March 17, 2026. We could not find a page where Meta names it, so treat the token as reported rather than documented.

Which rule Facebook Crawler actually follows

Facebook Crawler reads exactly one group in robots.txt, the most specific one that names FacebookBot, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: FacebookBot
Disallow: /drafts/

Find the group. Facebook Crawler looks for a group naming FacebookBot. One exists, so it ignores User-agent: * completely.
Apply only that group. It is refused /drafts/ and nothing else.
The surprise. /private/ is open to Facebook Crawler, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.

Test yourself: does a rule under User-agent: * apply to Facebook Crawler if the file also has a User-agent: FacebookBot group?

No. Once a group names it, Facebook Crawler reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Facebook Crawler remove your pages from AI answers?

Often, yes. Facebook Crawler is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: facebookbot the same as User-agent: FacebookBot?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Facebook Crawler? Decide by situation

Recommended setting for Facebook Crawler by type of site
If you are...	Recommended setting
You publish content and want AI answers to cite it	Low stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI training	Blocking it does not stop training, because Facebook Crawler is a utility crawler. Block the operator's training crawler instead.
You run an online shop	Allow it unless your logs show it is costly.
Your server is under load from bots	Rate-limit before blocking. It is rated safe in our database.

Check Facebook Crawler on your own site

Open /robots.txt on your domain and search for FacebookBot. If it is not named, it follows User-agent: *.
List the Disallow lines in the group Facebook Crawler follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
Look beyond the file. A firewall or bot manager can refuse Facebook Crawler even when robots.txt allows it, and that never shows in the file.
Run our free AI crawler check to see how Facebook Crawler and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Facebook Crawler

The errors we see most often with Facebook Crawler in the files and firewalls we test:

Treating Facebook Crawler as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
Relying on robots.txt alone when Facebook Crawler is rated caution or aggressive. Back the rule with a server-side block.
Blocking Facebook Crawler by IP alone. Ranges change; match the token and verify with logs.

All three hide inside a file that looks correct, so check Facebook Crawler from outside after every change.

Spotting Facebook Crawler in your logs

robots.txt says what Facebook Crawler may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "FacebookBot" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "FacebookBot" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Facebook Crawler user-agent, so confirm the source before acting on a match:

FacebookBot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Facebook Crawler request with caution.

Frequently Asked Questions

What user-agent string does Facebook Crawler use?

Facebook Crawler is reported to identify itself with FacebookBot. Evidence that the spelling is in real use comes from our own robots.txt study: 395 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), not from Meta, which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.

Is Facebook Crawler safe?

Will blocking Facebook Crawler hurt my SEO?

How do I block Facebook Crawler in robots.txt?

Add the following lines to your /robots.txt file:

User-agent: FacebookBot
Disallow: /

This instructs Facebook Crawler not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).

Does Facebook Crawler respect robots.txt?

Not documented. Meta has published no statement that Facebook Crawler reads robots.txt. A rule for FacebookBot will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.

How do I verify if Facebook Crawler is crawling my site?

Search your access logs for FacebookBot (for example grep -i "FacebookBot" /var/log/nginx/access.log). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that Meta sent it.