Overview
Vercel Favicon Bot is a link preview bot from Vercel used for link unfurling, rich-card generation, social previews, messaging previews, and page metadata fetching.
Its primary user-agent pattern is vercel-favicon-bot; related patterns include Vercel Favicon Bot.
Vercel Favicon Bot is Verified from current authoritative identity documentation reviewed on 2026-08-07. The identity type is Official Documented.
Robots.txt behavior is not currently confirmed.
Vercel Favicon Bot can usually be allowed after confirming the source and monitoring request volume.
Identity
- User-Agent Pattern
-
vercel-favicon-bot - Aliases
- Vercel Favicon Bot
- HTTP Agent Examples
-
vercel-favicon-bot - Robots Token
- vercel-favicon-bot
- Identity Type
- Officially documented
- Evidence Method
- Match `vercel-favicon-bot` to the current operator documentation and corroborate the request with operator-controlled verification signals where available; User-Agent strings alone can be spoofed.
Classification
- Type
- Preview
- Kind
- Preview
- Family
- Vercel
- Purpose
- Preview
Behavior and handling
- Common Use
- Vercel Favicon Bot is used for link unfurling, rich-card generation, social previews, messaging previews, and page metadata fetching.
- Detection Notes
- Vercel Favicon Bot traffic is primarily detected by the `vercel-favicon-bot` user-agent pattern; related patterns include `Vercel Favicon Bot`. Compare source IPs, reverse DNS, request paths, and crawl cadence with Vercel infrastructure before trusting the traffic.
- Respects robots.txt
- Unknown
- Spoofing Risk
- Vercel Favicon Bot has medium spoofing risk because user-agent strings can be copied; pair the match with DNS, IP, behavior, or operator evidence.
- Risk
- Safe
- Recommended Handling
- Depends
Rules and controls
- Robots.txt Snippet
-
# robots.txt behavior is unconfirmed. Do not rely on this rule without verification.
Relationships
- Operator
- Vercel Checked 2026-08-07
Relationships without an Evidence link are normalized from the canonical directory record. They should not be interpreted as independent proof of physical presence or request origin.