Social Image Missing

Element Code: IM-006

What "social image missing" means

The Open Graph protocol lets you control how a page appears when it is shared on Facebook, LinkedIn, Slack, Discord, and most other platforms that "unfurl" links into a preview card. The image half of that card comes from the og:image meta tag in your page head, something like:

<meta property="og:image" content="https://example.com/images/page-share.jpg">

When this tag is absent entirely, most platforms fall back to one of a few bad options: no image at all, rendering a plain text link card, a generic site-wide logo pulled from elsewhere, or in some cases they will grab the first <img> tag found in the page body, which is often unrelated, poorly cropped, or an icon that looks broken at preview size. None of these outcomes is something you would choose deliberately.

This is a distinct issue from "Social Image Wrong Size," where a tag exists but the dimensions are off. Here, the tag itself is not present in the page's markup at all.

Why this matters

Like image sizing, this is not a Google ranking factor, it is a click-through and brand-perception issue on the traffic you get from social sharing and messaging apps. But the effect is well documented in general web practice and worth taking seriously:

• Visual previews substantially outperform text-only links in social feeds, since an image-backed card is bigger, more eye-catching, and gives the scrolling user a reason to stop and read the headline.
• A blank or broken-looking preview reads as untrustworthy. Users increasingly treat a missing preview image as a signal that a link might be spam, outdated, or low effort, especially in messaging apps like Slack or Discord where colleagues are judging whether to click.
• You lose control of the narrative. Without an explicit og:image, some platforms will fall back to scraping a random image from the page, which might be a decorative icon, an ad creative, or nothing usable at all, meaning your brand has zero say in how the link looks when shared.
• It compounds across every share. This is not a one-time cost. Every single person who shares that URL, forever, gets the degraded preview until the tag is fixed and caches are refreshed.

How to detect it

The fastest single-page check is Facebook's Sharing Debugger at developers.facebook.com/tools/debug, paste the URL and it will tell you directly whether an og:image was found, and show you what actually renders.

For a site-wide sweep, crawl with Screaming Frog and check its built-in "Social" or custom extraction report for pages returning a blank og:image field. Cross-reference against your page templates, if it is missing on one blog post it is worth checking whether the whole template lacks the tag or whether it is a one-off content gap. Sitebulb has an equivalent Social audit that flags missing Open Graph tags automatically across a full crawl.

You can also just view source (or use a browser extension like "Meta SEO Inspector") on a sample of pages across each content type: homepage, blog post, product page, category page, since it is common for a site to have the tag on some templates and not others.

How to fix it, step by step

1. Add the og:image tag to the page template. This needs to happen at the template level, not page by page, or you will just recreate the same gap on the next new page. In WordPress, this typically lives in your SEO plugin (Yoast, Rank Math) or theme header, in custom-built sites it is a template variable in the head partial.
2. Set a sensible fallback image. For content types with no natural hero image, i.e. a plain text page, default to a branded fallback image rather than leaving the tag empty. Never let the template render an og:image tag with a blank or broken content attribute.
3. Use the right size and format. Follow the 1200x630px, 1.91:1 standard, JPEG or PNG, under 5MB, ideally well under 1MB for fast loading in the unfurl process.
4. Add a twitter:image tag too, or confirm the fallback works. X will use og:image automatically if twitter:image is absent, but if you are setting a twitter:card of summary_large_image, verify explicitly rather than assuming inheritance always works cleanly.
5. Set width and height meta tags. og:image:width and og:image:height let platforms render the preview without fetching and measuring the image first, which speeds up and improves the reliability of the unfurl.
6. Force a cache refresh on already-shared URLs. Once the tag is live, re-scrape any URLs that were previously shared with the broken preview using Sharing Debugger's "Scrape Again" and LinkedIn's Post Inspector, since old previews can be cached for days otherwise.

What good looks like

Every indexable page template, without exception, renders a complete og:image tag pointing at a real, correctly-sized, on-brand image, with width and height declared, and a Sharing Debugger check on a representative sample from each template comes back with a clean image preview rather than a blank card.

no image Text-only card, low CTR

1200x630 image Full image card, higher CTR

Where the og:image tag needs to live

FAQ