og:image is missing
Your page has no og:image tag, so shared links render as a bare text row instead of a card. Here is what each platform does without it, and how to add one correctly.
What you are seeing: Your link shows as a plain text row — title and URL only, no picture — on Facebook, LinkedIn, Slack, Discord and WhatsApp.
What og:image does
og:image is the single meta tag that tells social platforms which picture to show when someone shares your page. It is read from the raw HTML by a crawler that never sees your rendered layout, so nothing else on the page can stand in for it.
Without the tag, every platform falls back to its own guesswork. Some scan for the largest inline image and pick something arbitrary. Some show only the favicon. Most show nothing at all and collapse the card to a single line of text. None of those outcomes is under your control.
Why it costs more than the other tags
A card with an image occupies several times the vertical space of a bare link in a feed or a chat window, and the image is the only part of the preview that reads at a glance while someone is scrolling. Losing it does not just make the link plainer — it removes the part of the share that does the work.
This is also the most common Open Graph mistake by a wide margin, which means the bar to clear is low. A single branded fallback image on every page already puts you ahead of most of the web.
How to fix it
Add one meta tag inside the <head> of your HTML. The URL must be absolute and served over HTTPS — a relative path like /og.png will be ignored, because the crawler has no page context to resolve it against.
Use 1200 × 630 pixels. Declaring og:image:width and og:image:height alongside it lets platforms reserve the right space before the image finishes downloading, which avoids a flash of collapsed card on slow connections.
After you add it
Every platform caches link metadata independently, and most cache aggressively. Adding the tag does not retroactively fix links that have already been shared. Re-run this checker to confirm the tag is live, then use each platform's own debugger to force a fresh scrape before you share the URL again.
Add to your <head>
<meta property="og:image" content="https://example.com/og.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Short description of the image" />Frequently asked
Will Facebook pick an image from my page if og:image is missing?
Sometimes, but you cannot rely on it and you cannot control which image it picks. Facebook's crawler may choose the largest image it finds in the HTML, which is often a logo, a tracking pixel, or a decorative background. Setting og:image explicitly is the only way to decide what people see.
Can I use the same og:image on every page?
Yes. A single branded default is far better than no image, and it is the right starting point for most sites. Per-page images are worth generating once the default is in place, particularly for articles and product pages where the specific content is the reason someone is sharing the link.
Check your page
Run your URL through the checker to confirm the fix is live and see how the card renders on every platform.
Test a URL
ZippyStarter