Social Share Debugger

A social share debugger (sometimes called a social share checker or link preview tester) reads Open Graph and Twitter Card tags from a page, then builds approximate previews for common sharing platforms. Each platform can crop, cache, or render the final share differently.

X may keep an older copy of your page metadata. This debugger can confirm which image URL is present in the fetched HTML, but it cannot clear X's cache. Check that the image URL is public, uses HTTPS, and returns an image response.

Facebook may keep older Open Graph metadata after a page changes. Use Facebook's Sharing Debugger and select "Scrape Again" to request a new fetch. This tool can inspect the current HTML, but it cannot clear Facebook's cache.

The essential OG tags are og:title, og:description, og:image, and og:url. For better results, also include og:type (usually "website" or "article"), og:image:width, og:image:height, and og:site_name. Twitter also uses twitter:card, twitter:title, and twitter:image for Twitter Cards.

Each platform has its own cache, image crop, and rendering rules. These previews are useful comparisons, but the final share can differ. Slack provides a URL debugger at api.slack.com/tools/debug/url.

"summary" renders a small square thumbnail next to your title and description. "summary_large_image" renders a full-width banner image above the text, using the same 1.91:1 aspect ratio as Facebook and LinkedIn. Set twitter:card explicitly; if it's missing, Twitter defaults to "summary", which is why an image that looks right on Facebook can appear cropped to a small square on Twitter/X. This debugger switches its preview layout based on your page's actual twitter:card value.

Social platform crawlers don't execute JavaScript; they only read the HTML your server returns on first request. If og:image or og:title are set client-side only (an SPA with ssr: false, or a composable that runs after mount), crawlers see an empty or default tag even though the tag appears correctly once the page hydrates in a browser. In Nuxt, set meta with useSeoMeta or useHead during setup with SSR enabled so the tags are present in the initial HTML. This debugger fetches your page's raw HTML the same way, without running any JavaScript, so what it shows is what most social crawlers see.

Close, but not identical. This debugger fetches your page with a standard bot user agent and reads the raw HTML, the same rendering path real social crawlers use since they also skip JavaScript. It won't catch server logic that serves different content specifically to facebookexternalhit or Twitterbot user agents, so if your previews still look wrong here, that mismatch is the most likely cause.