SEO Tools·5 min read

Debugging Open Graph Previews That Show the Wrong Card

The page is right, the markup was updated on Tuesday, and the shared link still shows last month's headline with a stretched logo where the hero image should be. Debugging Open Graph previews is frustrating because two separate systems can be at fault: the HTML your server sends, and the cached copy each platform's scraper keeps. This article shows how to tell those failures apart, force the caches to let go, and read the fallback rules that decide what appears when tags are missing.

Open the free Open Graph Checker All insights

One broken card, two possible culprits

Markup problem or cache problem? Everything follows from this.

When a link preview is wrong, either the page is serving wrong og tags right now, or the page is fine and the platform is showing a scrape from before your fix. The repairs have nothing in common: the first means editing your head, the second means forcing a re-scrape. Guessing wrong wastes an afternoon.

The Open Graph Checker settles it in one fetch. Paste the URL, click Check Open Graph, and compare the Raw tags tab against what the platform displays. Correct tags plus a stale card points at the cache. Wrong tags in the raw view point at your markup, and no amount of cache clearing will help until the HTML changes.

Debugging Open Graph previews in three passes

A repeatable order of operations.

Pass one: read the Checks tab. Each item is marked pass, warn or fail, with fails first to fix: a missing og:title, og:description or og:image, a relative image path, or an image that won't load. Warnings cover the quieter problems, such as an image under 600 pixels wide, a shape far from 1.91:1, missing alt text, a missing og:url, or no twitter:card.

Pass two: open the Raw tags tab and the Previews tab. Raw tags lists every og: and twitter: property exactly as the page serves it, which is where typos, truncated URLs and http where https should be become obvious. A preview with an empty No image box explains a text-only card at once.

Pass three: open the og:image URL in a private browser window. The checker loads the image from your browser, and scrapers fetch it anonymously. If it redirects to a login or a bot rule on your CDN blocks it, platforms can't see it even when your own browser can. Only after all three passes agree should you touch platform caches.

A worked diagnosis, from symptom to fix

Right tags, wrong card, classic cache.

Symptom: a restaurant shares https://fernandco.example/spring-menu and Facebook renders the card as Fern & Co | Home with the old winter photo. Run the same URL through the checker. Raw tags shows og:title as Spring Menu 2026, Fern & Co and og:image as a full https address to /social/spring-menu.png. The Checks tab confirms the image loads at 1200 x 630.

Diagnosis: the markup is fine, so Facebook is serving a scrape made before the page was updated. Fix: follow the Facebook Sharing Debugger link in the Checks tab, click Scrape Again, and the next share shows the spring card. It takes a few minutes, because the first fetch separated the two failure modes instead of leaving you editing markup that was never broken.

Clearing stale cards from platform caches

Each platform forgets on its own schedule.

Platforms cache the first scrape of a URL, sometimes for weeks, and each clears it differently. Facebook's Sharing Debugger has a Scrape Again button, and LinkedIn's Post Inspector fetches the page fresh on demand; the Checks tab links to both. X and WhatsApp have no public refresh tool, so changes there can take a while to show.

The blunt fallback works everywhere: share the URL with a throwaway query string like ?v=2. Platforms treat it as a new address and scrape it fresh. It splits share counts across variants, so treat it as a last resort, not a publishing habit. Changing the image file name also helps, because a new image URL is fetched fresh. And when a card must be right the first time, check before the first share, because the cheapest cache to clear is the one that never held a bad card.

What platforms show when og tags are missing

A page with no og markup still gets a card. Just not yours.

The checker's previews follow the same fallback rules the platforms use. Facebook and LinkedIn take og:title, then the page title, and og:description, then the meta description, with og:image for the picture. The X preview reads twitter:title, twitter:description and twitter:image first and falls back to the og values. When nothing supplies an image, the card is a bare text block.

Missing og:title: platforms show your SEO title, brand suffix and all, clamped to two feed lines
Missing og:description: some cards render with a bare headline, others lift stray page text
Missing og:image: no picture, or on some platforms a random image from the body, which is how a footer badge becomes your launch visual
Missing twitter:card: X falls back to a small summary card even when you have a wide image
Missing og:url: engagement splits across every tracking-parameter variant of the same page

Debugging moves that waste an afternoon

Skip these and the fix gets faster.

The most common one: editing markup to fix what was a cache problem, then deciding the edit failed because the platform still shows the old scrape. Next, testing while logged in, which hides that the page or its image sits behind an auth wall for anonymous scrapers. The checker's request arrives without cookies, just like a scraper's, so a login screen shows up as exactly the broken card your audience would get. Third, checking only Facebook and assuming X and LinkedIn agree, though each caches and falls back differently. Last, trusting your browser's developer tools on a client-rendered app. If JavaScript injects your og tags, scrapers never see them, and a checker that reads the raw HTML shows you the empty head they actually receive.

When the Open Graph Checker hands off to other tools

Diagnose here, repair over there.

The Open Graph Checker reads and renders, and its Missing tags tab drafts the tags a page lacks. When the existing tags are wrong rather than missing, build a correct block with the Open Graph Generator and redeploy. If X's layout is the problem, the Twitter (X) Card Generator sets the twitter:card type and handles. When the audit should cover the whole head, including title, canonical, viewport, lang and H1 count, the Meta Tag Analyzer scores it in one pass. It only confirms the og and twitter tags exist, though, so come back here for image size and platform previews.

Try it now

Open Open Graph Checker

The tool is one click away. No sign up, no upload, no payment.

Open Open Graph Checker

Write a review