You paste your launch link into X, LinkedIn or Slack, and it shows up as a plain grey box. No picture, sometimes the wrong title. On launch day that costs clicks, because people scroll past links without an image.
Here are the six causes I see most often, and a quick way to test each one.
1. There is no og:image tag at all
Social sites do not guess. They read one tag:
<meta property="og:image" content="https://yourproduct.com/og.png">
Test: view the page source (Ctrl+U) and search for og:image. If it is missing, add it in the <head>.
2. The image URL is relative
content="/og.png" works in a browser but many crawlers ignore it. Use the full address with https://.
3. The image is behind a login or blocked
If the file needs a cookie, sits on a staging domain, or your robots.txt blocks the folder, the crawler gets an error page instead of a picture. Open the image URL in a private window. If you cannot see it there, neither can X.
4. The tag is added by JavaScript
Single-page apps often set meta tags after the page loads. Most link crawlers do not run JavaScript, so they never see them. Put the tags in the HTML the server sends, or pre-render the page.
5. Wrong size or too heavy
Use 1200 x 630 pixels (about 1.91:1), PNG or JPG, under 5 MB. Very small images get shown as a tiny thumbnail or not at all. Keep text away from the edges, because some apps crop. Adding og:image:width and og:image:height next to og:image also helps the first share render, because the crawler does not have to download the image to learn its size.
6. The old version is cached
You fixed it, but the preview still looks broken. Social sites cache the first version they saw. LinkedIn has a Post Inspector, and Facebook has a Sharing Debugger, that re-fetch the page. For others, adding a harmless query string (?v=2) to the link usually forces a fresh read. Better still, give the image itself a new file name (for example og-v2.png): previews are often cached by the image URL, so a new image URL is what gets picked up. If the image still lags, re-fetch a second time a minute later. (Thanks to mcgram in the comments for both tips.)
A five-minute check before launch
- View source and confirm
og:title,og:descriptionandog:imageare there, with full URLs. - Open the image URL in a private window.
- Paste the link into a private Slack or Discord message to yourself and look at it.
- If anything is off, fix it, then re-fetch with the platform's debugger.
If you want to see all of it at once, I made a free meta tag and share preview checker that shows the Google result and the share card and lists what to fix. No account needed.
What else has broken a link preview for you? I am collecting the weird cases.
Top comments (2)
Really useful checklist — the private-window test for cause 3 is the one I would run first, since a login or robots block is easy to miss when you are signed in.
Two small additions that have helped me: adding og:image:width and og:image:height alongside og:image can help the first share render, because the crawler does not have to fetch the image first to know its size. And when you replace a broken image, change the image URL itself rather than only the page link — the preview cache is keyed to the image URL, so a new filename or version on the image is what gets the new one picked up. Your 1200 x 630 size lines up with Meta's guidance for best display, with 600 x 315 as the point where smaller images drop to a thumbnail.
One question: in your experience, do the debuggers reliably clear the cache on the first re-fetch, or do you usually need a second pass after changing the image?
Thanks, both are great additions. Setting og:image:width and og:image:height is a cheap win, and you are right about the cache: giving the image a new file name (og-v2.png) is more reliable than only adding ?v=2 to the page link. I will add both to the post.
On your question: not always on the first pass. The re-fetch tends to pick up the new title and description first, and the image can lag behind, so a second re-fetch a minute or two later is worth doing. Changing the image URL the way you describe avoids most of that.