What is FacebookExternalHit, and why is it visiting my website?

FacebookExternalHit is Meta's crawler for generating link previews across Facebook, Messenger, Instagram, and other Meta products. It retrieves webpage metadata such as Open Graph tags, titles, descriptions, images, and structured data so that shared links can display rich previews. Requests are typically triggered when a user shares, posts, or pastes a URL on a Meta platform, or when Meta refreshes preview information. For publicly accessible websites that are shared on Meta services, this bot traffic is expected and usually low in volume.

Is FacebookExternalHit a legitimate bot, or is it commonly spoofed?

FacebookExternalHit is a legitimate crawler operated by Meta. Like many well-known bots, its User-Agent string can be spoofed by scrapers, scanners, or malicious actors attempting to disguise automated traffic. Attackers may impersonate FacebookExternalHit because websites sometimes allow social preview crawlers broader access than unknown bots. User-Agent strings alone cannot verify authenticity and should not be relied upon as the sole verification method. You can use Meta's recommended methods mentioned below to verify a legitimate visit, or use RobotSense.io API to easily verify FacebookExternalHit bot visits.

How can I verify that a request is really coming from FacebookExternalHit?

You can use Meta's recommended official methods to verify FacebookExternalHit bot visits, these include: - IP range checks Do not use User-Agent based detection as that can be easily spoofed. Alternatively, you can use RobotSense.io API to easily verify FacebookExternalHit bot and all other bots from Meta.

Should I allow or block FacebookExternalHit on my website?

For most public websites, allowing FacebookExternalHit is beneficial because it enables accurate link previews when content is shared on Meta platforms. Rich previews often improve how shared content appears to users by displaying the correct title, description, and image. Blocking may be appropriate when: - Content is private or restricted. - Internal applications or APIs should not be previewed. - Sensitive resources should not be fetched by external services. - Access policies require strict crawler restrictions. For websites that depend on social sharing, allowing the crawler is generally recommended.

How can I control or block FacebookExternalHit using robots.txt or other methods?

You can add a rule in your robots.txt, as given above to control (crawl-delay) or disallow FacebookExternalHit bot. The FacebookExternalHit bot honors it's own specific robots.txt directives, but does not honor global directives. Also, you can use further controls in your WAF, or in RobotSense enforcement settings to manage the bot behavior.

How often does FacebookExternalHit crawl websites, and can it impact server performance?

FacebookExternalHit primarily performs event-driven fetching. Requests are commonly generated when users share URLs, when previews need to be generated, or when metadata is refreshed for previously shared content. For most websites, the impact is minimal because: - Requests are targeted to specific URLs. - Bandwidth usage is generally low. - Crawl activity is not site-wide. High-traffic websites with frequently shared content may see more requests, but the overall load is typically much lower than that of search engine crawlers.

What happens if I block FacebookExternalHit? SEO, visibility, and feature impact explained.

Blocking FacebookExternalHit does not affect search engine rankings because it is not a search indexing crawler. Potential impacts include: - Missing or incomplete link previews on Facebook, Messenger, Instagram, and related Meta products. - Missing preview images, titles, or descriptions. - Reduced quality of shared content presentation. - Metadata refreshes may fail or become outdated. Blocking does not directly affect: - Google indexing. - Bing indexing. - Organic search rankings. - Traditional SEO databases.

Does FacebookExternalHit collect, scrape, or use my content for training or reuse?

FacebookExternalHit retrieves webpage content and metadata needed to generate and maintain link previews. This commonly includes page titles, descriptions, Open Graph tags, structured data, and preview images. Documented uses include: - Link preview generation. - Metadata extraction. - Preview validation and refreshes. - Content enrichment for shared URLs. There is no public documentation indicating that FacebookExternalHit is used for general web indexing, SEO datasets, or AI model training. Its documented purpose is focused on social sharing and preview generation rather than large-scale content collection.

FacebookExternalHit

Name: FacebookExternalHit
Author: Meta / Facebook

Others

Operated by Meta / FacebookOthers

Visit Bot Homepage

Verify FacebookExternalHit IP Address

Verify if an IP address truly belongs to Meta / Facebook, using official verification methods. Enter both IP address and User-Agent from your logs for the most accurate bot verification.

FacebookExternalHit is Facebook’s (Meta’s) crawler used to fetch webpage content for link previews across Facebook, Messenger, Instagram, and other Meta surfaces. It retrieves metadata such as Open Graph tags, titles, descriptions, images, and structured data. These requests are user-triggered, occurring when someone shares or pastes a URL on a Meta platform. The bot does not index or rank websites and has no connection to search algorithms. Blocking it may prevent accurate link previews. Crawl activity is lightweight and focused on fetching just enough content to generate rich social previews. It ignores the global user agent (*) rule. RobotSense.io verifies FacebookExternalHit using Meta’s official validation methods, ensuring only genuine FacebookExternalHit traffic is identified.

This bot does not honor Crawl-Delay rule.

User Agent Examples

Contains: facebookexternalhit/1.1 (+http://www.facebook.com/externalhit_uatext.php)

Contains: facebookexternalhit/1.1

Contains: facebookcatalog/1.0

Robots.txt Configuration for FacebookExternalHit

Robots.txt User-Agent:FacebookExternalHit

Use this identifier in your robots.txt User-agent directive to target FacebookExternalHit.

Recommended Configuration

Our recommended robots.txt configuration for FacebookExternalHit:

User-agent: FacebookExternalHit
Allow: /

Completely Block FacebookExternalHit

Prevent this bot from crawling your entire site:

User-agent: FacebookExternalHit
Disallow: /

Completely Allow FacebookExternalHit

Allow this bot to crawl your entire site:

User-agent: FacebookExternalHit
Allow: /

Block Specific Paths

Block this bot from specific directories or pages:

User-agent: FacebookExternalHit
Disallow: /private/
Disallow: /admin/
Disallow: /api/

Allow Only Specific Paths

Block everything but allow specific directories:

User-agent: FacebookExternalHit
Disallow: /
Allow: /public/
Allow: /blog/

Set Crawl Delay

Limit how frequently FacebookExternalHit can request pages (in seconds):

User-agent: FacebookExternalHit
Allow: /
Crawl-delay: 10

Note: This bot does not officially mention about honoring Crawl-Delay rule.

Frequently Asked Questions

What is FacebookExternalHit, and why is it visiting my website?: FacebookExternalHit is Meta's crawler for generating link previews across Facebook, Messenger, Instagram, and other Meta products. It retrieves webpage metadata such as Open Graph tags, titles, descriptions, images, and structured data so that shared links can display rich previews. Requests are typically triggered when a user shares, posts, or pastes a URL on a Meta platform, or when Meta refreshes preview information. For publicly accessible websites that are shared on Meta services, this bot traffic is expected and usually low in volume.
Is FacebookExternalHit a legitimate bot, or is it commonly spoofed?: FacebookExternalHit is a legitimate crawler operated by Meta. Like many well-known bots, its User-Agent string can be spoofed by scrapers, scanners, or malicious actors attempting to disguise automated traffic. Attackers may impersonate FacebookExternalHit because websites sometimes allow social preview crawlers broader access than unknown bots. User-Agent strings alone cannot verify authenticity and should not be relied upon as the sole verification method. You can use Meta's recommended methods mentioned below to verify a legitimate visit, or use RobotSense.io API to easily verify FacebookExternalHit bot visits.
How can I verify that a request is really coming from FacebookExternalHit?: You can use Meta's recommended official methods to verify FacebookExternalHit bot visits, these include: - IP range checks Do not use User-Agent based detection as that can be easily spoofed. Alternatively, you can use RobotSense.io API to easily verify FacebookExternalHit bot and all other bots from Meta.
Should I allow or block FacebookExternalHit on my website?: For most public websites, allowing FacebookExternalHit is beneficial because it enables accurate link previews when content is shared on Meta platforms. Rich previews often improve how shared content appears to users by displaying the correct title, description, and image. Blocking may be appropriate when: - Content is private or restricted. - Internal applications or APIs should not be previewed. - Sensitive resources should not be fetched by external services. - Access policies require strict crawler restrictions. For websites that depend on social sharing, allowing the crawler is generally recommended.
How can I control or block FacebookExternalHit using robots.txt or other methods?: You can add a rule in your robots.txt, as given above to control (crawl-delay) or disallow FacebookExternalHit bot. The FacebookExternalHit bot honors it's own specific robots.txt directives, but does not honor global directives. Also, you can use further controls in your WAF, or in RobotSense enforcement settings to manage the bot behavior.
How often does FacebookExternalHit crawl websites, and can it impact server performance?: FacebookExternalHit primarily performs event-driven fetching. Requests are commonly generated when users share URLs, when previews need to be generated, or when metadata is refreshed for previously shared content. For most websites, the impact is minimal because: - Requests are targeted to specific URLs. - Bandwidth usage is generally low. - Crawl activity is not site-wide. High-traffic websites with frequently shared content may see more requests, but the overall load is typically much lower than that of search engine crawlers.
What happens if I block FacebookExternalHit? SEO, visibility, and feature impact explained.: Blocking FacebookExternalHit does not affect search engine rankings because it is not a search indexing crawler. Potential impacts include: - Missing or incomplete link previews on Facebook, Messenger, Instagram, and related Meta products. - Missing preview images, titles, or descriptions. - Reduced quality of shared content presentation. - Metadata refreshes may fail or become outdated. Blocking does not directly affect: - Google indexing. - Bing indexing. - Organic search rankings. - Traditional SEO databases.
Does FacebookExternalHit collect, scrape, or use my content for training or reuse?: FacebookExternalHit retrieves webpage content and metadata needed to generate and maintain link previews. This commonly includes page titles, descriptions, Open Graph tags, structured data, and preview images. Documented uses include: - Link preview generation. - Metadata extraction. - Preview validation and refreshes. - Content enrichment for shared URLs. There is no public documentation indicating that FacebookExternalHit is used for general web indexing, SEO datasets, or AI model training. Its documented purpose is focused on social sharing and preview generation rather than large-scale content collection.