Social share
preview
See your link the way WhatsApp, X, LinkedIn and Facebook will show it - before you share it. Type your web address, or paste HTML / type the tags by hand. We fetch your page securely - nothing else leaves your browser.
How does your link travel?
Or paste HTML / type the tags manually
Lint - what the networks will complain about
| Tag | Status | Note |
|---|
Yetty serves Open Graph and Twitter cards on every page automatically - correct sizes, absolute URLs, no plugin.
Six rules the four
networks share
og: is the lingua franca
WhatsApp, Facebook, LinkedIn and X all read Open Graph first. Get og:title, og:description and og:image right and you are 90% done.
1200 x 630, absolute URL
One image size satisfies everyone. Relative URLs like /hero.jpg silently fail - the crawler has no idea what site you meant.
Everyone crops to 1.91:1
Tall or square images get their tops and bottoms cut. Keep faces and text in the middle band of the image.
Titles truncate differently
X shows roughly 70 characters, Facebook about 88, WhatsApp two short lines. Front-load the words that matter.
Previews are cached
Fixed your tags but the old card keeps showing? The network cached it. Use Facebook's Sharing Debugger or LinkedIn's Post Inspector to refresh, or bust the URL with ?v=2.
twitter:card unlocks the big card
X falls back to og: tags for the words, but only twitter:card = summary_large_image guarantees the full-width image layout.
People also ask
Why does my link show no image on WhatsApp?
Almost always one of three things: the og:image tag is missing, its URL is relative instead of absolute (WhatsApp cannot resolve /hero.jpg), or the image is too large - WhatsApp skips images over about 600KB. Add an absolute https URL to a reasonably sized image and re-share; WhatsApp caches previews, so test with a fresh URL or add ?v=2.
What size should an og:image be?
1200 x 630 pixels is the safe answer - the 1.91:1 ratio Facebook, LinkedIn and X all crop toward. Keep it under 5MB (under 600KB if WhatsApp matters to you) and put nothing important in the outer edges, which get trimmed on some networks.
Do I need separate twitter: tags if I already have og: tags?
Mostly no - X falls back to og:title, og:description and og:image. The one tag you do want is twitter:card set to summary_large_image; without it X may render the small square card instead of the big one.