What your site shows when someone shares its link. Show your best plumage

· Founder of Magpie AI

Published · 7 min read

In short

A shared link's card is drawn from your page's Open Graph tags (og:title, og:description, og:image and og:url, plus twitter:card for X). Each app fetches your page itself without running its scripts, so the tags must be in the HTML your server sends. One 1200 by 630 image under 600KB suits every big platform, and a new image address gets past an old cached picture.

Contents

Paste a link into LinkedIn, Slack or a WhatsApp chat and a second later a card appears under it, with a picture, a title and a line or two of grey text. Your site didn't send that card. The app went off and fetched your page, read a handful of tags in its head and drew the card from those, and when it finds nothing it can use, you get a bare blue link or an empty grey box.

Often it isn't you sharing it, either. It's a colleague dropping you into a Slack channel, or someone chirping about you in a group chat, and the card is all anyone sees of you before they decide whether to tap.

Every platform here reads the same few Open Graph tags in your page's <head>. The Open Graph protocol (opens in a new tab) asks for four on every page (og:title, og:type, og:image and og:url) and offers og:description for "a one to two sentence description". LinkedIn's help page names title, image, description and url as the ones it needs. Here's the set I'd put on brewlog.example, a made-up stock app for small coffee roasters:

<meta property="og:title" content="Know what's in the roastery, bag by bag" />
<meta
  property="og:description"
  content="Stock, roast dates and reorders for small coffee roasters. Free for one roaster."
/>
<meta property="og:image" content="https://brewlog.example/share/brewlog-v2.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta
  property="og:image:alt"
  content="Brewlog's stock screen, four coffees listed with their roast dates"
/>
<meta property="og:url" content="https://brewlog.example/" />
<meta property="og:type" content="website" />
<meta name="twitter:card" content="summary_large_image" />

X has its own twitter: tags, but in its markup reference each one falls back to its Open Graph twin, so twitter:image borrows og:image and twitter:title borrows og:title. The one you can't leave out is twitter:card. Without it, X says a small summary card "may be rendered" in place of the big picture, which is why summary_large_image sits at the bottom of that block.

Slack reads "oEmbed and Twitter Card / Open Graph tags". Apple's 2017 talk on rich links says Messages uses og:title in place of your <title>, takes og:image for the picture, and keeps your site's icon (the link rel="icon" one) as a fallback for when the connection is poor. If two plugins both write an og:image, ogp.me says the first one from the top wins, and that's often not the one you meant.

The picture size each platform asks for#

One picture of 1200 by 630 pixels, saved as a PNG or JPEG under 600KB, fits every size these platforms publish (X's 2:1 near enough). Here's what each says, as of 17 November 2026.

WhereSize and shapeFile size
FacebookAt least 1200 by 630, close to 1.91:1 (200 by 200 at the very least)8MB at most
LinkedInAt least 1200 by 627, 1.91:1; under 401 wide shows as a thumbnail5MB at most
X2:1, from 300 by 157 up to 4096 by 4096; JPG, PNG, WEBP or GIF, no SVGUnder 5MB
WhatsAppAt least 300 wide, no wider than 4:1Under 600KB
iMessageNo size given; a picture of this page rather than your logo10MB with the icon and any video
SlackNo size givenNo limit given

Two notes on that table. X's own card pages have gone from its developer site (its new documentation has no page on cards that I could find on 17 November), so its row comes from the last copies, archived in January and February 2026. And WhatsApp's figures are from Meta's guide for its business platform, which says previews show "when the link is sent via chat or shared via status" without limiting that to business accounts.

A 1200 by 630 picture is a touch narrower than X's 2:1, so X may trim a sliver off the top or bottom. Its archived pages don't say how it trims, so I'd keep anything that matters away from the edges. Apple's advice is that "images should not include text", because rich links are drawn at so many sizes. If your card carries a headline anyway, as plenty of landing pages' cards do, keep it to a few words in type big enough to read at thumbnail size on a phone.

Add og:image:width and og:image:height too. Facebook says that without them "the first person who shares a piece of content won't see a rendered image", since its crawler has to download and process the picture first. With them, it can draw the card at once.

A blank card nearly always comes down to the app not getting your tags or not getting your picture. Here are the causes I'd check, roughly in this order, most of them named in the platforms' own documentation.

The tags are written by scripts. Apple says "JavaScript does not run when creating rich links", so the tags "need to be in the source of the page", and Slack fetches "as little of the page as it can". A single-page app that adds its tags with a head helper after loading looks fine in your browser's inspector and empty to every one of these apps, the same trap that keeps a page from being named in AI answers. View the page's source (not the inspector) and search it for og:image.

The picture's address doesn't work from outside. WhatsApp wants "an absolute URL", so /share.png on its own may give it nothing. A build that bakes in http://localhost:3000/og.png or a staging address works on the developer's machine and nowhere else. LinkedIn adds that a picture on "a protected directory or website" won't show, and X's old troubleshooting page lists a robots.txt that turns away Twitterbot. Slack, for what it's worth, doesn't read robots.txt at all.

The file is too big or the wrong kind. 600KB is WhatsApp's line, and X doesn't take SVG. WhatsApp also wants your <head> within "the first 300KB of the HTML", so a head stuffed with inlined scripts and styles can push the tags past where it stops reading.

Why it shows the wrong picture or an old one#

An old card is a cache. Each platform keeps what it fetched, and keeps the picture by its address, so changing the file on your server while keeping its name changes nothing for anyone. Facebook says images "won't be updated unless the URL changes". X's troubleshooting page said its crawler re-reads a page's tags "roughly every seven days" and caches pictures by address too. Slack holds its answer "for around 30 minutes", the shortest any of them states. LinkedIn's help says a preview "may show an old image that is cached", usually because the link was shared before.

So the card keeps showing last month's picture until you give the new one a new name. brewlog-v2.png, or the old name with ?v=2 on the end, which is the workaround X's old page suggested.

The wrong picture altogether is usually a leftover. Site builders fill in their own stock description and picture until you write yours, and a theme or SEO plugin can add a second og:image above yours. Either way a stranger has taken over your bird feeder, with the builder's logo or someone's stock photo sitting where your product should be.

How to refresh a preview#

Change the picture's address first, publish, then ask each platform to read the page again. Cards already posted keep the old picture; LinkedIn says its refresh changes the preview "for new posts that include it", and I'd assume the same of the others.

WhereHow to refresh
FacebookPaste the link into the Sharing Debugger, which "also triggers a scrape"
LinkedInPaste it into Post Inspector at linkedin.com/post-inspector
XNo current tool documented; a new image address, or wait about seven days
SlackWait about 30 minutes
WhatsApp, iMessageNo tool documented; a new image address is the best bet I know of

WhatsApp's and iMessage's rows are my reasoning, not their documentation, which says nothing about caching. A new address is what Facebook and X say works for pictures, and it costs you nothing to try.

What Magpie's free report checks#

Magpie's free report has a section called "Your link, shared" that reads your tags from the HTML your server sends, as these apps do, and draws the card your link would get on X, Slack, Facebook, LinkedIn, WhatsApp, iMessage and five more. It checks that a share picture is named and actually loads (and says so when its address points somewhere like localhost), that X is asked for the large card, that there's a share title and a description, and that none of it is a site builder's stock words or picture.

Questions people ask#

Should the share title match the page's title?#

Not word for word. The <title> is written for a Google result, with your site's name after it. The share title shows with your domain under it, so Apple suggests leaving the site's name out of og:title altogether, and X's reference gave twitter:title 70 characters at most.

Does every page need its own picture?#

The platforms would like it. X's card page asked for a picture "representing the content of the page" and not "a generic image such as your website logo", and Apple says much the same, with a logo better used as the icon. On a small site I wouldn't lose sleep over it, though. Give the home page and each main landing page a picture of the product doing its job (the same thing your first screen shows, ideally), and let blog posts draw theirs from their titles, which is what our own articles do.

Sources

  1. The Open Graph protocol (opens in a new tab)
  2. Meta for Developers, A Guide to Sharing for Webmasters (opens in a new tab)
  3. Meta for Developers, Images in Link Shares (opens in a new tab)
  4. Meta for Developers, WhatsApp Business Platform, Link Previews (opens in a new tab)
  5. LinkedIn Help, Make your website shareable on LinkedIn (opens in a new tab)
  6. LinkedIn Help, Use Post Inspector to refresh URL (opens in a new tab)
  7. X Developer Platform, Summary card with large image (archived February 2026) (opens in a new tab)
  8. X Developer Platform, Cards markup (archived February 2026) (opens in a new tab)
  9. X Developer Platform, Troubleshooting cards (archived January 2026) (opens in a new tab)
  10. Slack API, Slack's robots (opens in a new tab)
  11. Apple Developer, Ensuring Beautiful Rich Links (Tech Talk) (opens in a new tab)

About the author

· Founder of Magpie AI

Alex founded Magpie AI and writes about what turns a landing page's visitors into customers, drawing on what its audits find on real sites, from the first screen to the checkout

Related articles

Fix what loses you customers.Fix what loses you customers. Then bring more of them in

  • Free score, no sign‑upNo sign‑up
  • No credit card neededNo card needed