Why Social Link Previews Look Wrong—and How to Fix Them

Learn why shared links show old titles, missing images, or inconsistent cards, then use a simple evidence-first process to fix the live page.

SharePost on XShare on LinkedIn
Watercolor illustration of stale social preview layers being peeled away to reveal one correct link card

The short answer

Wrong link previews usually come from missing or conflicting metadata, an inaccessible image, redirects, or a platform cache. Inspect what the live URL exposes first, fix the public page, and then ask the platform to fetch it again where a refresh tool is available.

Overhyped Social Link Preview showing live metadata and a Facebook card for the Overhyped homepage
Live metadata preview captured 30 August 2026. Social platforms may apply their own crop, truncation, or cached values.

You publish a page, paste the link into a post, and the card shows an old title—or no image at all. The first instinct is often to edit the post. The real problem is usually in the page metadata or a platform cache.

We built the Social Link Preview for this small but frustrating moment: see what the live page exposes before the announcement goes out.

Many social and messaging products fetch the shared URL and read Open Graph tags from the page head. Common values include og:title, og:description, og:image, og:url, and og:type. X also recognises Twitter Card tags and can use Open Graph values as fallbacks.

The platform then creates its own card. It can crop an image, shorten text, ignore unsupported markup, or reuse cached values.

Why the wrong title or description appears

The Open Graph value may be missing, empty, duplicated, or still produced by an old template. In that case, a platform may fall back to the HTML title or meta description. A client-side script may also add tags too late for a crawler that reads only the original server HTML.

Inspect the live fetched page, not only the CMS form where you entered the text.

Why an image is missing

The image URL should normally be a complete public HTTPS URL. Relative paths, authentication, crawler blocks, redirects, incorrect content types, and very slow files can prevent a fetch. An image can also be technically available but unreadable after a platform crops it.

Use a purpose-built social image with important words and faces away from the edges. Test it at a small size.

Why an old card remains after a fix

Platforms cache link metadata so they do not fetch the page on every share. Correcting the live tags does not always clear that cache immediately. Some platforms provide sharing debuggers that request a refresh; others update on their own schedule.

This creates two separate questions:

  • What does the live page expose now?
  • What has this platform cached from an earlier fetch?

A preview checker answers the first. The platform controls the second.

A practical fix sequence

  1. Fetch the final public URL and note any redirects.
  2. Inspect the Open Graph and Twitter Card values in the live HTML.
  3. Confirm that the image URL opens without a login.
  4. Fix the template or page fields, then deploy.
  5. Fetch the live URL again.
  6. Use the platform’s official debugger when a stale cache remains.

Do not keep changing good metadata because one network has not refreshed its cache yet.

The Open Graph protocol documents the core properties. X publishes its own card markup guidance and explains its fallbacks.

Preview before you post

Use the free Social Link Preview to inspect the fetched title, description, and image across several representative card layouts. It is a preview, not a guarantee that every product will render the same crop.

Method note: the tool reads live public metadata. Platform rendering and caches remain outside its control. Last reviewed 16 August 2026.

Continue learning

Keep moving with a closely related topic and a free tool you can use immediately.

Watercolor illustration of repeated webpage labels becoming distinct after a shared template is repaired

How to Fix Duplicate Title Tags and Meta Descriptions

Diagnose repeated metadata across URLs, competing tags in one page, and matching H1/title wording with a worked example and a safe template repair workflow.

Watercolor illustration of a cobalt link path meeting one coral break while other paths fade behind cream mist

How to Fix Broken Links Without Removing Useful References

Learn how to fix broken links with a worked example, internal-link repair choices, and checks that separate missing pages from redirects or unavailable responses.

Watercolor illustration of cobalt content cards connected by clear coral paths across textured cream paper

What a Useful Internal Link Tells People and Search Engines

Review crawlable internal links, descriptive anchor text, destination intent, and page-level evidence without pretending one page reveals a whole site architecture.