← All guides · Published November 14, 2026 · Reviewed November 14, 2026 · By the Ingenious AI team · 6 min read
Why Should You Never Block facebookexternalhit?
The short answer: because it is the agent that builds link previews. facebookexternalhit fetches your page when someone shares the link on Facebook or WhatsApp, to assemble the card — image, title, description — that everyone else sees. It is a verified utility-class entry in AgentBlock's database and the one agent the default policy allows. Block it and your shared links render as bare, broken cards, usually discovered weeks later from a screenshot someone sends you.
Build my block kit — free · Test a policy in the simulator first
What is facebookexternalhit?
Meta's link-preview fetcher, a verified utility-class entry in AgentBlock's database — explicitly not an AI bot. It retrieves a page's Open Graph data when a link is shared on Facebook or WhatsApp. AgentBlock's default policy allows it, and its class default of allow exists because blocking breaks a feature, not a crawl.
The share card is a fetched product
When a customer pastes your product link into WhatsApp, the rich card that appears — photograph, headline, price line — is not magic and not cached goodwill. A fetcher visited your page at that moment, read its Open Graph tags, and built the preview. That fetcher is facebookexternalhit. Every block rule that sweeps it up converts your best organic marketing surface into a grey box with a naked URL.
The damage is silent and asymmetric. Your analytics do not report 'previews broken'; your block log, if you read it, shows a blocked agent you may not recognise; and the people who see the broken cards are prospects in the act of being referred by a happy customer — the highest-trust traffic a small business gets.
How it gets blocked by accident
Three routes account for nearly every case. A hand-written 'block Meta' rule that matches the facebook portion of the name. A scorched-earth policy that blocks every agent in a database view without reading the class column. And an imported block list copied from a forum post, assembled by someone whose site did not depend on social sharing. All three share a shape: a decision made about a family or a feeling, applied to an agent nobody examined individually.
AgentBlock's defaults are built against exactly this. The utility class default is allow, the builder shows facebookexternalhit with its note — 'NOT an AI bot — link-preview fetcher; blocking it breaks link previews' — and the default policy's single allowed agent is this one, out of 21 verified entries. The exception is deliberate and labelled.
The allowlist seatbelt
Policies also carry a plain allowlist: user-agent substrings that are stripped out of the blocked set even if a decision or an imported rule puts them there. facebookexternalhit is the canonical allowlist entry — the seatbelt that keeps a future policy edit, made in a hurry by someone who does not know this history, from re-breaking previews. Adding it costs nothing and survives regenerations, because the allowlist is part of the policy the kit is generated from.
The same mechanism protects any agent your business depends on — a partner's monitoring fetcher, a marketplace's preview bot — but facebookexternalhit is the one to set on day one, before the first incident teaches the lesson at retail price.
Testing your previews like you mean it
Verification for this agent is pleasingly concrete: share your own links. After any policy deploy, paste your homepage and two product or article pages into a WhatsApp chat and a Facebook post draft and look at the cards. Rich image and title: the fetcher is getting through. Bare link: something in the chain — edge rule, plugin, robots drift — is refusing it, and the enforcement-gap audit plus the block log will find which.
Do the test on the pages people actually share, not only the homepage. Path rules are the subtle failure: a wildcard written for admin protection that happens to cover a shared landing path will refuse the fetcher there and nowhere else, and only a per-page share test catches it before a customer's group chat does.
Five actions to take today
- Keep facebookexternalhit allowed. It is the utility exception in the default policy — the one allowed agent among 21 verified entries.
- Add it to the allowlist. Belt and braces: the policy allowlist strips its substring from any future blocked set by construction.
- Never write family rules. 'Block Meta' is not a policy; five Meta entries with five jobs get five decisions.
- Share-test after every deploy. Paste key pages into WhatsApp and Facebook and confirm rich cards render, per page, not just the homepage.
- Check path rules for collisions. A wildcard meant for private paths must not cover the landing pages your customers share.
Worked example: the bakery whose shares went grey
Crumb Culture, a fictional bakery with a devoted WhatsApp following, adopted a forum block list during a weekend tidy-up. Orders from shared links sagged over the next three weeks — the owner later estimated a 28% drop on share-driven orders — before a regular customer sent a screenshot: the weekend-special link rendered as a plain grey box, no photo of the bake, no headline.
The block log made the diagnosis instant once someone looked: 1,940 facebookexternalhit requests refused since the tidy-up, each one a preview that never rendered. The list had matched the name under a 'Meta crawlers' heading its author had never examined.
Removing the rule and adding facebookexternalhit to the policy allowlist restored previews the same day. The bakery's share-driven orders recovered over the following fortnight, and its policy note now opens with the sentence this guide is named after.
Frequently asked questions
Is facebookexternalhit an AI crawler?
No. AgentBlock's database states it plainly: it is not an AI bot, but the link-preview fetcher for shared URLs on Facebook and WhatsApp. It sits in the database because it appears in the same logs and the same policy decisions as the AI agents — usually as the agent that must be protected from them.
What exactly breaks if it is blocked?
Link previews. Shares of your pages on Facebook and WhatsApp render without the image, title and description your Open Graph tags provide — a bare URL that gets a fraction of the clicks a rich card earns, with no error shown to you or the sharer.
Why does AgentBlock's default allow only this one agent?
Because it is the only verified entry whose blocking breaks a feature of your own site rather than declining a vendor's use of your content. Every other default is block; this one's default is allow, and the builder shows the reasoning on the entry itself.
Can I rate-cap it instead of allowing it outright?
You can, but size the cap to sharing reality — a viral post can generate preview fetches in bursts, and a capped fetcher produces the same broken cards for late sharers. For a utility agent, allow plus the allowlist seatbelt is the proportionate posture.
How do I check if it is blocked right now?
Share one of your pages in WhatsApp and look at the card, then check your kit's block log for facebookexternalhit refusals. The pair — a broken card plus refusals in the log — confirms it; a healthy card means the fetcher is getting through.
Related guides
- How to Block AI Scrapers and Bots from Your Website
- Which AI Crawlers Should You Allow?
- How Do You Block AI Bots on WordPress, Cloudflare, or Plain JS?
- Pre-deploy breakage simulator — test a policy before it ships
- Impact preview — your server log against a draft policy
- How Can You Tell a Spoofed AI Crawler from a Real One?
- Which AI Agents Cannot Be Blocked by Name?
- Why Doesn't AgentBlock Block the Reported GrokBot Token?
- What Can Robots.txt Actually Do About AI Crawlers?
- How Do You Design an Allowlist for AI Agents?
- Block evidence — parse a log, build an evidence pack
- The dated agent database — 25 entries, graded