BlogWhatsApp

WhatsApp link preview not showing for your deep links? Why, and how to fix it

· 7 min read · By the Strait team

Why a deep link shows a bare URL, the App Store's card or the wrong image in WhatsApp, how WhatsApp fetches a preview, the Open Graph tags it reads, the preview_url switch in the WhatsApp Business API, and a checklist to fix each cause.

You paste a product link into WhatsApp and wait for the card: image, title, a line of description. Instead you get a bare blue URL. Or worse, you get a card for the Google Play Store, or a generic "Open link" title that tells nobody anything. For an Indian app that sends most of its links on WhatsApp, the preview is the first thing people see, and a bad one costs taps.

Deep links are especially prone to this, because the same URL has to do two jobs: open an app for a person, and describe itself to a robot. This post explains how WhatsApp builds a preview, why deep links break it, and how to fix each cause.

When a message contains a link, WhatsApp fetches that URL and reads the page's metadata to build a card. The metadata is the Open Graph protocol, a set of <meta> tags in the page's <head>:

Code
<meta property="og:title" content="Summer sale: 40% off sneakers">
<meta property="og:description" content="Today only, in the Hilltop Shoes app.">
<meta property="og:image" content="https://cdn.hilltop.example/og/summer-sale.jpg">
<meta property="og:url" content="https://hilltop.strait.link/summer">

og:title, og:image and og:url are the basic tags the protocol asks for; og:description is optional but it's the second line of most cards.

The request that fetches the preview is not a person. The fetcher identifies itself in its user agent: WhatsApp's starts with WhatsApp/ and a version number, without the Mozilla/5.0 prefix every real browser sends. That difference matters for deep links, as we'll see. Someone who taps the link and opens it inside WhatsApp's built-in browser also has "WhatsApp" in their user agent, but after a normal Mozilla/5.0 … browser prefix. A link server has to tell the two apart: one wants a card, the other wants your app.

A normal web page serves the same HTML to everyone, so the fetcher sees the same tags a browser does. A deep link usually doesn't serve a page at all. It looks at the device and redirects: to your app, to Google Play, to the App Store or to a website. Each of those is a chance for the preview to go wrong.

Cause 1: the bot gets redirected to a store

If the link server treats WhatsApp's fetcher like a phone and redirects it to Google Play or the App Store, the fetcher follows the redirect and reads the store's tags. Your card then shows the store's page title and icon, not your sale. It is a common deep-link preview bug, and an easy one to miss because people tapping the link never see it.

Fix: the link server must recognise preview fetchers and answer them with a page of their own, never a redirect. Strait checks for link-preview robots before anything else. WhatsApp, Slack, Telegram and Discord fetchers, and the usual crawlers (Facebook's, X's, LinkedIn's and others), get a small page with your link's own tags, and they are never redirected. Requests without any user agent get the same page.

Cause 2: there are no tags to read

Some link services serve bots a blank page, or a page with a generic title. WhatsApp then has nothing useful to show and falls back to the bare URL or a plain title.

Fix: give every link you share its own title, description and image. In Strait these are the link's title, description and imageUrl fields, set in the dashboard or through the API (short links docs). They become og:title, og:description and og:image on the preview page, and og:url is the short link itself. If you leave the title empty, the page says "Open link", which is better than nothing but not by much.

Cause 3: the image can't be fetched

The card appears with a title but no image, or a grey box. The usual reasons:

  • A relative URL. og:image needs a full URL, including https://. /img/sale.jpg means nothing to a fetcher that isn't on your site.
  • The image is behind a login, a signed URL that has expired, or a firewall that blocks unknown user agents.
  • The image is very large. WhatsApp doesn't publish an image size limit that we could find, so we can't give you a number. A compressed JPEG at a normal social-card size (1200 × 630 is the common choice) avoids the question.

Fix: host the image on a public HTTPS URL and open it in a private browser window to make sure no login is needed. Strait only accepts https images for link previews.

Cause 4: bot protection blocks the fetcher

If your link domain or image host sits behind aggressive bot protection, the fetcher can get a challenge page instead of your tags. Its "title" is then something like "Just a moment…", or the fetch fails and WhatsApp shows the bare URL.

Fix: allow known preview fetchers through, or serve previews from a host that doesn't challenge them. Test by requesting the link with a preview fetcher's user agent (see the checklist below).

Cause 5: you're looking at an old preview

Chat apps may reuse a preview they fetched for the same URL earlier, so a fix doesn't always show up on the next paste. When you're testing, add a throwaway parameter (?v=2) so the URL is new. If the new URL shows the right card, your fix worked; the old card will catch up or not, but new shares will be right.

The WhatsApp Business API: preview_url

If you send messages through the WhatsApp Business Platform (Cloud API) rather than by hand, previews have a switch. Meta's documentation for text messages describes a preview_url field: set it to true and the WhatsApp client tries to render a preview of the first URL in the message body. Leave it out, or if the client can't retrieve a preview, and the message shows a plain clickable link. URLs must start with http:// or https://.

So if your API-sent order updates show bare links while hand-pasted links get cards, check preview_url first. And put the link you want previewed first in the message.

Previews and tap counts

Every preview fetch is a request to your link. If your link service counts it as a tap, your numbers are wrong: a link pasted into a group can be fetched by WhatsApp before anyone taps it, and other chat apps fetch it again. Strait never counts preview robots as taps and never bills them. They appear separately on the Usage page as preview fetches, so you can see how much robot traffic a link drew without it inflating your campaign numbers. Our post on deep link analytics explains what counts as a tap.

A checklist to fix a WhatsApp preview

  1. Check the tags the fetcher sees. Request the link with a preview fetcher's user agent and read the <head>:

    Terminal
    curl -s -A "WhatsApp/2.23.20.0" "https://hilltop.strait.link/summer" | grep -i 'og:'

    You should see your title, description, image and URL. If you see a redirect (curl -sI shows a 302 and a location: header) to a store, the server is redirecting bots: cause 1.

  2. Check the image URL in a private browser window. It must load without a login, over HTTPS.

  3. Preview the card with our free link preview checker: paste the tags and see how WhatsApp, X, LinkedIn, Facebook and Slack would show them, with what to fix.

  4. Check user-agent detection with the user agent inspector: paste a user agent and see whether the link server treats it as a bot, an in-app browser or a phone.

  5. Paste a fresh URL (?v=2) into a chat with yourself and look at the card.

  6. For API-sent messages, confirm preview_url: true and that your link is the first URL in the body.

What we haven't tested

The detection rules and the preview page in this post come from our engine's code and its unit tests. We haven't yet recorded a real-phone run that checks preview cards inside WhatsApp itself, so treat the WhatsApp-side behaviour (which URL it previews, how long it keeps a card) as described by Meta's documentation and the Open Graph protocol, not by our own measurements. Previews work the same whatever phone the person has; what happens after the tap differs, and on iPhone our deferred linking is opt-in.

Sources and how we checked

  • The Open Graph protocol: the og:title, og:image, og:url and og:description tags. Read on 5 October 2026.
  • Meta for Developers, WhatsApp Business Platform: text messages: the preview_url field, first-URL rendering, and the plain-link fallback. Read on 5 October 2026.
  • Our engine's code and unit tests: preview-fetcher detection (the WhatsApp/ user agent without a browser prefix, Slack, Telegram and Discord fetchers, common crawlers, and requests with no user agent), the preview page and its Open Graph tags, https-only images, and previews never counted or billed as taps.
  • Our short links docs: how link-preview robots are handled.