Skip to main content
Contact

Open Graph in 2026: Why Shared Links Often Look Broken

5 min readPublished on April 12, 2026Updated on September 09, 2026

This article was written with AI assistance and editorially reviewed.

Contents

A link with no og:image lands in WhatsApp, LinkedIn or Slack as a grey box with no image, sometimes with a random snippet of the page as a preview instead. To the person receiving it, that does not look like a missing meta tag - it looks like a broken website. That is the impression a surprising number of business websites leave, even though the fix is a single line of code.

In short

Open Graph and Twitter Cards determine how a shared link looks on WhatsApp, LinkedIn, X and Slack. Missing og:image makes every shared link look unprofessional, regardless of how good the page behind it actually is.

The preview generated when a link is shared is not designed by the person sharing it - it comes from the meta tags in the target page's <head>. If they are missing, the platform decides for itself what to show, often an arbitrarily chosen image from the page, sometimes nothing at all. The effect is the same as a broken business card: the substance behind it might be fine, but the first impression says nobody bothered to tidy up. When a link lands in a WhatsApp message or a LinkedIn note as part of a pitch, that first impression is often the only one a prospect gets before deciding whether to click at all.

The mandatory tags at a glance

Six tags in every page's <head> are enough for a clean preview on virtually any platform:

TagPurposeNote
og:titleTitle shown in the previewShort and self-contained, does not need to match the SEO title exactly
og:descriptionShort description under the titleSome platforms truncate it, so lead with the most important point
og:imagePreview imageAbsolute URL, not a relative path
og:urlThe page's canonical URLPrevents duplicate previews from URL parameters
og:typeContent typeUsually website or article
twitter:cardRendering on XUsually summary_large_image for a large image

The most common mistake is a relative rather than an absolute URL for og:image - a path like /images/preview.jpg works fine in a browser, but not as the value of this tag, because the platform fetching it has no base context to resolve the path against.

The image format that works everywhere

1200 by 630 pixels has become the practical standard, rendering without awkward cropping on most major platforms. More important than the exact pixel count is readability at small size: many feeds show the image only as a thumbnail, and a title that stops being legible at that size defeats the purpose. A generic stock illustration with no obvious connection to the content adds little - an image with a clearly readable page title and a small, unobtrusive brand mark reliably beats the interchangeable alternative in practice.

Why caches outlast the fix

A corrected og:image does not show up automatically the next time a link is shared. Most platforms fetch a URL only the first time it is shared and cache the result from then on, regardless of what changes on the page afterwards. Seeing a new preview requires forcing a re-fetch through that platform's own debugging tool:

  • Facebook Sharing Debugger for Facebook, Instagram and partly WhatsApp - use the Scrape Again function
  • LinkedIn Post Inspector, run once before any important campaign
  • X Card Validator to check rendering on X

Reloading your own website after a change shows the update immediately - on the platform itself, it stays invisible until the cache has been actively refreshed. That gap is why a fix that already works still looks broken in tests days later.

Dynamic images instead of manual upkeep per article

For a website with many individual pages - a blog, for instance - a manually designed image per article rarely makes sense. Next.js offers the ImageResponse function from next/og to generate an og:image per page automatically from React components: title and branding are produced at build or request time from the same data driving the rest of the page. That prevents the preview from ever being forgotten for new content, because it is no longer a manual extra step but something that comes into being automatically alongside the page itself.

Concrete steps for the next 90 days

  • Days 1-30: check and add og:title, og:description, og:image, og:url, og:type and twitter:card on your most important pages
  • Days 31-60: decide on an og:image strategy, introducing dynamic generation instead of manual images if you run many pages
  • Days 61-90: test previews with the major platforms' debugging tools and refresh the caches of any URLs already shared

Conclusion

Send yourself a link to your most important page over WhatsApp, and one over LinkedIn. What you see there is what everyone recommending your site sees too, every day, without you ever finding out. The fix usually takes longer to discuss than to implement. How this visibility complements clean schema markup is covered in our article on Schema.org for local businesses. What role loading speed plays once someone actually clicks is covered in our article on Core Web Vitals 2026. What a technical SEO audit including a meta tag review costs is covered in our article on SEO costs. For a no-obligation review of your current previews, feel free to get in touch.

Want to know how your links look on WhatsApp and LinkedIn?
Get in touch

Frequently asked questions

What resolution should your og:image be?

1200 by 630 pixels is the established standard that renders cleanly on most platforms. More important than the exact resolution is that title and branding stay readable even as a small thumbnail, not only at full size.

Do you need twitter:card if og:image is already set?

Recommended, yes. X does fall back to Open Graph tags if twitter:card is missing, but a dedicated twitter:card tag set to summary_large_image gives you more control over how the preview renders in the app and the web client.

Why does a platform still show the old preview after you changed the image?

Most platforms fetch a URL only the first time it is shared and cache the result afterwards. An updated preview appears only after you force a re-fetch through that platform's own debugging tool - it does not refresh automatically the next time the link is shared.

Does Open Graph also have an SEO effect?

Indirectly, yes. A compelling preview raises the click-through rate on shared links, which means more traffic. Some search engines, Bing in particular, also use og tags as a source for snippet generation when dedicated meta tags are missing.

Related service

You might also like

Get it for free

Enter your email address. You'll immediately receive a confirmation link - after clicking it the checklist is available right away.

Required field

Let's talk about your project

Message us on WhatsApp