Free · Safe server-side scan
Social Preview Checker
Paste a page URL. We inspect its Open Graph and Twitter/X metadata, verify the selected image, and build six practical previews before your launch post discovers interpretive dance.
At a glance
- Extract Open Graph, Twitter/X, title, description, and canonical metadata without executing page scripts.
- Preview Facebook, X, LinkedIn, Discord, Telegram, and WhatsApp-style cards in one pass.
- Verify the selected image safely, flag missing or awkward metadata, and copy an implementation checklist.
Before you publish
A polished card starts in the page head
Social platforms usually read Open Graph tags, while X also understands its own card tags. Explicit values are more reliable than fallbacks — particularly for ecommerce pages where a collection image sneaking into a product campaign is considered suboptimal.
Which tags matter most?
Start with og:title, og:description, og:image, og:url, and og:type. Add twitter:card=summary_large_image; Twitter/X can usually fall back to Open Graph for title, description, and image, though explicit Twitter tags give you finer control.
What image should I use?
A 1200×630 image is a dependable general-purpose choice. Keep the focal subject and text away from the edges because platforms crop differently, serve it from a stable public HTTPS URL, return an accurate image content type, and keep it comfortably below 5 MB.
Why does the live platform still show an old preview?
Cached scrapes. Use Meta Sharing Debugger or LinkedIn Post Inspector to request a new scrape. Other apps may refresh on their own schedule; a harmless version query can provide a new cache key for urgent tests.
Are these exact platform screenshots?
No. They are close, useful approximations built from the metadata fetched now. Platforms change layouts, truncate copy, crop images, apply policy, and cache independently. Always test the final URL on the platform that matters most to the campaign.
Are checked URLs stored?
No. Public HTML and image response headers are processed in memory because browser CORS rules usually prevent a direct check. Private-network destinations are blocked and requests have DNS, timeout, redirect, and response-size protections.