No, WhatsApp Did Not Choose That Blank Box: Why Your Website's Link Preview Looks Broken

You have probably assumed that when you paste your website link into WhatsApp, or drop it into a Facebook post, and it shows a blank grey box or the wrong photo, that is simply how the app decided to display it. It is not. That little preview card, the image, the headline, the line of text underneath, is built from instructions sitting on your own website. Which means it is yours to fix.

I had a version of this conversation on a call this week. A business owner had shared their brand new site into a customers' WhatsApp group and it came up as a plain grey rectangle with the domain name and nothing else. They assumed WhatsApp was broken. WhatsApp was doing precisely what it was told. The problem was that nobody had told it anything.

Let me take the myth apart, because once you see how the card is actually built, fixing it takes about ten minutes.

The card is built from your website, not the app

When you share a link, the app does not look at your page the way a customer does. It sends a small crawler to read a handful of hidden tags in your page's code. Those tags are called Open Graph tags, and they were originally created at Facebook as a shared standard for exactly this job. WhatsApp reads them. Facebook reads them. LinkedIn reads them. Slack, iMessage, and most others read the same tags.

There are four that matter: a title, a type, an image, and the canonical web address. Meta's own developer documentation is blunt about why they exist. You mark up your website with Open Graph tags, it says, to take control over how your content appears. Take control. That is the phrase. The preview is not a decision the app makes about you. It is a decision you make about yourself, and the app just reads it back.

So what does that mean for you as an owner? It means the first thing a potential customer sees, before they have visited your site at all, is a card you are either controlling or leaving to chance. A shared link is often the very first impression, and first impressions online are decided in about three seconds. People judge the card before they judge the click.

Why yours is blank, or wrong

Look at the mechanism behind the grey box. When those tags are missing, the app does not give up politely. It guesses. Meta's documentation says it plainly: without the markup, the crawler uses internal heuristics to make a best guess about what to show.

A best guess is exactly as reliable as it sounds. Sometimes it grabs the first image it finds in your code, which might be a tiny logo, a payment icon, or a stock placeholder from your theme. Occasionally it finds no usable image and shows nothing at all. Other times it pulls a stray line of text from a menu instead of your actual headline. None of it is malice. It is a machine filling a gap you left open.

Now the visceral bit. Imagine a wedding florist in Carlow posting her new website into a local suppliers' group on Facebook, hoping for referrals. Her link lands as a blank box. Two posts down, a rival's link shows a styled bouquet, a clean business name, and a one-line pitch. Same group, same audience, same three seconds of attention. One card says open me. The other says I am not sure this is finished. She did nothing wrong. She just never knew the card existed.

The caching trap that makes people give up

This is the part that catches everyone, so I want you to know it before it happens to you.

You add the correct tags, then share the link again. And the preview is still wrong. At that point most people conclude the fix did not work and walk away. It did work. The app is showing you an old copy.

Every one of these platforms caches the preview the first time it sees your link, and it holds onto that copy. Meta states that images are cached based on the URL and will not update unless the URL changes. So changing the tag alone does nothing to a link the platform has already stored. You have to force it to look again.

The tools to do that are free and official. Facebook's Sharing Debugger has a Scrape Again button that tells it to re-read your page. LinkedIn's Post Inspector does the same for LinkedIn. You paste your address in, you trigger the re-scrape, and the fresh card appears. WhatsApp usually follows once Facebook's copy updates, though it can lag by a day.

One honest limit here, and it matters. On LinkedIn, refreshing the cache only affects new shares. A post you already published keeps its original preview permanently, blank box and all. You cannot retroactively fix a card that is already sitting in someone's feed. Verify the preview before you share it widely, not after. That order is the whole game.

The image rules that actually decide whether it shows

Assuming the tags are present, the image itself has to clear a few practical bars or the app quietly drops it.

The reliable size is 1200 by 630 pixels, an aspect ratio of roughly 1.91 to 1. That is the shape almost every platform designs its card around, so an image at those dimensions displays cleanly on Facebook, LinkedIn, and WhatsApp without awkward cropping. Go much smaller and some apps refuse to show it as a large card at all.

A few more details trip businesses up, drawn from Meta's WhatsApp documentation:

• The image URL must be public and served over HTTPS. If it sits behind a login, or your site still runs on plain HTTP, the crawler cannot fetch it and you get nothing.
• For WhatsApp specifically, keep the file under 600KB. A giant unoptimised photo can time out before it loads.
• The page has to return a normal 200 OK response, not a chain of redirects. Redirect loops are a common silent killer of previews.

So what, in plain terms? Your share image needs to live at a stable, secure, public web address that loads quickly every single time a crawler knocks. That last requirement is not really an image problem. It is a hosting problem. A site that is slow to respond, or that serves images over an insecure connection, will drop previews no matter how perfect your tags are. This is one reason a free, automatically renewed SSL certificate is not a nice-to-have. Without HTTPS, your share image may simply refuse to appear.

Where WordPress fits, and where it leaves you exposed

There is a detail almost nobody tells small business owners. WordPress on its own does not output Open Graph tags. A stock install, with no SEO plugin and no configuration, ships your pages with none of the markup these apps are looking for. Which is exactly why so many perfectly good sites share as a grey box.

The good news is that fixing it does not require a developer. A proper solution looks like this: the site outputs complete Open Graph tags on every page, you can set a default share image for your brand, you can override it per page for a specific product or offer, and the whole thing runs on hosting that serves those images fast and over HTTPS. That is the standard to hold any platform to.

A full WordPress site meets that standard, because the entire plugin ecosystem is open to you and a well-built site includes this from the start. This is where being on real WordPress, rather than a locked-down builder, pays off: you own the tags, the image, and the control. If you would rather not assemble that yourself, you can describe your business and have a complete, properly built WordPress site put together in under a minute, share image and metadata included, then adjust anything you like from there.

The domain in that card matters too. The web address shown on the preview is part of the impression, which is one more reason to build on a domain you actually own rather than a borrowed subdomain.

Fix Your Link Preview in Five Steps

You can run this whole check in under ten minutes.

1. Verify what shows today. Paste your homepage address into Facebook's Sharing Debugger and read the card it returns, along with any warnings.
2. Set your tags. Make sure your page outputs an Open Graph title, description, and image, either through your SEO plugin or your platform's settings.
3. Deploy a proper share image. Create or upload a 1200 by 630 image, kept under 600KB, served over HTTPS.
4. Force a re-scrape. Use the Sharing Debugger's Scrape Again and LinkedIn's Post Inspector to clear the old cached card.
5. Verify before you share. Confirm the new preview looks right in the debugger, then send the link out.

The upshot

That blank box was never WhatsApp punishing you. It was a set of instructions nobody had filled in, doing what empty instructions always do. The card that appears when someone shares your link is a small thing that does a large job, because it is often the first and sometimes the only thing a customer sees before deciding whether you are worth a click.

Ten minutes of setup, once, and every future share of your link works for you instead of against you. Check yours today, before the next person passes it on.

Frequently Asked Questions

Why does my website link show no image when I share it on WhatsApp or Facebook?

Almost always because your page is missing Open Graph tags, particularly og:image, so the app cannot find a picture to show. WordPress does not add these tags on its own. Add them through an SEO plugin or a platform that includes them, make sure the image is public and served over HTTPS, then force the app to re-read your page.

How do I change the image that appears when my link is shared?

Set the og:image tag on the page to the image you want, ideally 1200 by 630 pixels. Then use Facebook's Sharing Debugger and LinkedIn's Post Inspector to trigger a re-scrape, because the platforms cache the old image and will not update it until you tell them to look again.

I fixed the tags but the old preview still shows. Why?

The platform is showing a cached copy from the first time it saw your link. Meta caches previews by URL and will not refresh them automatically. Paste your address into the relevant debugger and trigger a re-scrape to force an update. Note that on LinkedIn, posts you already published keep their original preview permanently.

What size should my social share image be?

1200 by 630 pixels, an aspect ratio of about 1.91 to 1, is the safe universal size that displays cleanly across Facebook, LinkedIn, and WhatsApp. For WhatsApp, keep the file under 600KB so it loads before the crawler times out.

Do I need Open Graph tags if I never share my own links?

Less urgently, but you rarely control who shares them. A customer recommending you in a WhatsApp group, or a supplier posting your link, triggers the same preview. If the tags are missing, their recommendation shows up as a blank box rather than a branded card. It is worth setting once.

Sources