WhatsApp preview user agent
When a link is shared in WhatsApp, the app fetches the URL to build the rich link preview from Open Graph metadata. The fetch is identified by a user agent containing the WhatsApp token. It is a preview-generation request, not a human visit.
What this means
When someone pastes a link into a WhatsApp chat, the app fetches the URL to render the rich preview — a thumbnail, title, and description — using the page's Open Graph metadata.
The preview reflects the metadata that was read, not a human reading the page. The fetch typically carries a user agent containing the WhatsApp token, sometimes alongside a browser-like prefix.
How the preview fetch identifies itself
The preview request includes a user agent containing the WhatsApp token. Match on that token substring rather than assuming a fixed full string, since the exact format is not formally published as a stable token the way some crawlers document theirs.
The user agent is a claim and can be copied. The fetch reads server-rendered Open Graph tags; JavaScript-injected tags are typically not seen.
- User agent contains the WhatsApp token
- Reads Open Graph meta tags for the preview
- Exact UA format is not formally documented as a stable token
Debugging a missing preview
If a WhatsApp link shows no rich preview, confirm the page returns 200 with valid Open Graph tags (especially og:image with an accessible image) in the initial HTML, and that nothing redirects or blocks the fetch.
Finding the WhatsApp token in your logs for the shared URL confirms the preview fetch reached your server.
How it appears in analytics and logs
A request whose user agent contains the WhatsApp token is the messaging client fetching a URL to build a chat preview. It is triggered by sharing and is bot-like preview traffic, not an audience visit.
Diagnostic use case
Confirm whether WhatsApp's preview fetch reached a shared page, debug a missing WhatsApp preview, and keep these requests out of human analytics.
What WebmasterID can help detect
WebmasterID classifies WhatsApp preview fetches server-side as social-preview activity and surfaces them on the bot-intelligence view, so they do not inflate human page views.
Common mistakes
- Counting WhatsApp preview fetches as human visits or referrals.
- Relying on JavaScript-injected Open Graph tags the fetch does not execute.
- Assuming a fixed WhatsApp UA string instead of matching the token substring.
Privacy and accuracy notes
Detection uses only the user agent. No human identity is attached to the preview fetch. WebmasterID records it as a social-preview bot event, separate from human analytics.
Frequently asked questions
- Why does my WhatsApp link have no thumbnail?
- The preview fetch could not read a valid og:image, or the image is too large or inaccessible. Confirm an accessible image in og:image and a 200 response with Open Graph tags in the initial HTML.
Related pages
- TelegramBot user agent
TelegramBot is the crawler Telegram uses to fetch a URL shared in a chat so it can render the link preview from Open Graph and standard page metadata. It is a preview-generation bot, not a human visit, and identifies itself with a documented TelegramBot user-agent token.
- facebookexternalhit user agent
facebookexternalhit is the user-agent token used by Meta's crawler when it fetches a shared URL to read Open Graph metadata and render a link preview on Facebook and Messenger. It is a preview-generation bot, not a human visit, and is documented in Meta's sharing tooling.
- Social preview bot user agents
When someone pastes your link into a social or messaging app, a preview bot fetches the page to build a card from your Open Graph and Twitter Card tags. Bots like facebookexternalhit, Twitterbot, Slackbot, Discordbot, and LinkedInBot identify themselves by token. This page covers what they are and why they hit you.
- Bot intelligence
Server-side classification of preview and unfurl traffic.
Sources and verification notes
- Meta — Sharing webmaster guide (Open Graph for previews)WhatsApp is a Meta product; previews are built from Open Graph metadata. Exact UA token format not formally published.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.