FacebookBot
Operator unconfirmed · Unconfirmed Not in Meta’s docs · robots.txt: Unconfirmed
Not in Meta’s current crawler documentation (checked 2026-09-24). A robots.txt line naming FacebookBot may do nothing: robots.txt only works through the names a crawler answers to, and Meta does not document this one.
Meta's current tokens: FacebookExternalHit, Meta-WebIndexer, Meta-ExternalAds, Meta-ExternalAgent and Meta-ExternalFetcher. Each one’s page says what it does and whether it follows robots.txt. Keeping the old line next to them costs nothing.
Every fact below is unconfirmed by the operator: Meta's documentation does not mention this token, so this page states nothing about what it does. The robots.txt lines below are still correct syntax for it.
Block FacebookBot
User-agent: FacebookBot
Disallow: /
Unconfirmed by the operator No operator documentation says whether FacebookBot reads robots.txt at all, so these lines are a request it may or may not honour.
Allow FacebookBot
User-agent: FacebookBot
Allow: /
An allow group only changes anything if a broader rule would block FacebookBot. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.
Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.
Already have a robots.txt? Paste it into the robots.txt checker to see whether it blocks FacebookBot on a given path, and which line decides.
Block or allow it at the server
No server rule for FacebookBot. No operator documentation we found gives the User-Agent string it sends, so there is no documented pattern to match. A rule written from a guessed string could miss it, or refuse something else.
Who blocks it
Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 44 block FacebookBot from the whole site by name, 31 block it through their User-agent: * group, and 9 name it with partial rules (some paths closed, the home page open). 2 more name it only to let it in.
44
block it by name 8.7%
31
block it through * 6.1%
9
name it, partial rules 1.8%
Percentages are of the 508 files we could read, not of all 1,000 sites.
Highest-ranked sites that block FacebookBot by name
- twitter.com rank 16
- x.com rank 48
- yahoo.com rank 61
- msn.com rank 72
- vimeo.com rank 85
- chatgpt.com rank 87
- snapchat.com rank 134
- gravatar.com rank 154
- tumblr.com rank 156
- nytimes.com rank 157
Each links to the site's live robots.txt, which may have changed since 2026-10-09.
robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.
Facts
- Operator
- Unconfirmed by the operator Meta's current crawler documentation does not list this token.
- Purpose
- Unconfirmed by the operator
- Obeys robots.txt
- Unconfirmed by the operator
- In your server logs
- Unconfirmed by the operator The documentation we checked does not give its user-agent string.
- How to verify it
- Unconfirmed by the operator The documentation we checked gives no IP list or DNS check for this crawler, so a request claiming to be FacebookBot cannot be verified against the operator.
What Meta says
Quoted word for word from the operator's documentation.
“This page provides guidance on how to configure your robots.txt file so that our crawlers interact properly with your site.”
Sources
- Meta for Developers: Meta Web Crawlers — fetched and checked 2026-09-24
Where we looked
- developers.facebook.com/documentation/sharing/webmasters/web-crawlers — 2026-09-24: Loaded; lists FacebookExternalHit, Meta-WebIndexer, Meta-ExternalAds, Meta-ExternalAgent and Meta-ExternalFetcher. No mention of FacebookBot.