Open Graph Social Preview — Check Link Cards Before You Share

Share cards fail silently — until you post

You publish a blog, paste the URL into Slack, LinkedIn, or X… and get a blank image, a wrong title, or the site name only. Open Graph and Twitter meta tags control those previews. If they are missing or inconsistent, the platform improvises — usually poorly.

An OG / social preview tool fetches the public page, reads the tags, and shows an approximate card so you can fix issues before a campaign launch.

Fah Swe Tools includes OG / Social Preview with SSRF-safe fetching.

Preview a URL at https://tools.fahswe.com/seo/og-preview.

Tags that drive most link previews

Prioritize:

• og:title / twitter:title
• og:description / twitter:description
• og:image (absolute HTTPS URL, adequate dimensions)
• og:url and canonical consistency
• og:type (often website or article)

Platforms crop differently. Treat any online preview as guidance, not a pixel-perfect Facebook simulator — but missing fields are still obvious.

How to preview social cards online

1. Deploy or stage a publicly reachable HTTPS page.
2. Open OG / Social Preview.
3. Paste the URL and run the check.
4. Confirm title, description, and image appear.
5. Fix template or CMS fields, purge CDN/cache if needed.
6. Re-check, then use platform debuggers for a final cache refresh when required.

Private hosts, localhost, and internal IPs are blocked for security — as they should be.

Common OG mistakes that kill click-through

• Relative image paths (/img/share.png) instead of absolute URLs
• Images under ~600px wide that look soft when cropped
• Title truncated because the CMS injects a huge site suffix
• Description empty because a plugin only filled Twitter tags
• Staging noindex pages accidentally shared in outreach

After OG fixes, validate basics with Meta Tag Checker and sketch SERP copy with SERP Preview. For multilanguage sites, run Canonical & hreflang Checker.

Workflow for marketers and developers

1. Writer drafts title + excerpt
2. Designer exports a 1200×630 share image
3. Dev wires meta tags in the layout
4. QA runs OG preview on production URL
5. Social posts go out only after the card looks right

This five-step loop prevents “we’ll fix it after the blast” disasters.

FAQ

Will this match Facebook exactly?

No preview can guarantee identical crops forever — platforms experiment. Use it to catch missing or broken tags early.

Can I preview password-protected pages?

Not via public fetch. Temporarily publish a review URL or test on an open staging host.

Is fetching archived?

No — checks are ephemeral and rate-limited.

Is OG / Social Preview free?

Yes at tools.fahswe.com.

Image specs that usually survive crops

Aim for roughly 1200×630 JPEG/PNG under a few hundred KB when possible. Keep critical text inside a safe center region; platforms crop differently on mobile. Avoid embedding tiny logos in corners that disappear after crop.

Cache busting social cards

After fixing tags, Facebook/LinkedIn may still show stale cards until their debugger refreshes. Change the og:image URL (version query) when the image itself changed but the path stayed identical.

Content ops checklist

• Writer owns title/description length
• Designer owns share image
• Developer owns meta injection
• Marketer owns final preview before boost spend

Document this RACI once; it prevents launch-day chaos.

Campaign war-room routine

Thirty minutes before a product launch blast:

1. Freeze copy and share image.
2. Deploy.
3. Run OG / Social Preview on the canonical URL.
4. Run platform native debuggers if you rely on Facebook/LinkedIn caches.
5. Only then schedule posts and ads.

Skipping step 3 is how “wrong thumbnail” screenshots end up in post-mortems.

Multi-locale share cards

Each language version needs its own titles, descriptions, and often localized imagery. After wiring templates, check an English and a secondary locale URL. Confirm og:locale / alternate locales if you set them, and keep Canonical & hreflang Checker in the same QA lane.

Design system for share images

Create a Figma component at 1200×630 with safe margins, a large headline area, and a small logo. Export JPG for photos and PNG for flat graphics. Store finalized share images next to the post slug so content ops can find them a year later when refreshing the article.

Social previews are part of SEO-adjacent UX: they influence click-through from chats and social feeds even when Google ignores og:image.

Deep dive: social cards as a conversion surface

A share card is a miniature landing page. Title, description, and image must sell the click in under three seconds. Product marketers who A/B test ad creative often forget to A/B test OG images for organic and employee advocacy posts — leaving easy engagement on the table.

Template variants

Maintain three Figma frames: announcement, article, and hiring. Each has locked logo placement and a content slot. Export, upload, wire meta, then verify with OG / Social Preview. Consistency trains your audience to recognize posts from your domain in crowded feeds.

UTM and canonical discipline

UTMs belong on the shared URL, not necessarily inside og:url. Keep canonical and og:url clean to the preferred path; append UTMs when posting. Confirm with Meta Tag Checker that you did not accidentally canonicalize to a UTM’d URL.

Crisis communications

When you must update a live statement, change both body content and the share image URL (version bump). Otherwise platforms keep showing yesterday’s optimistic headline beside today’s sober update.

Run every high-stakes URL through https://tools.fahswe.com/seo/og-preview before executives amplify it.

CTA

Check the next URL before you paste it into a campaign. Open OG / Social Preview or https://tools.fahswe.com/seo/og-preview and explore more SEO & Web tools.