See how your page looks before you share it
Enter your page details and preview exactly how the link card renders on Facebook, X, LinkedIn, and Google — then copy the meta tags straight into your site.
Why It’s Worth Checking Before You Share
A page can be perfectly written and still fall flat when it’s shared — if there’s no image, a blank description, or a truncated title, the link card that shows up on Facebook or X does more to discourage a click than encourage one.
Most of this comes down to a handful of meta tags in your page’s <head> that most site owners never actually check — this tool shows you exactly what a visitor sees before you find out the hard way, after sharing.
How This Tool Works
Getting an accurate preview takes three steps.
Enter Your Page Details
Title, description, image URL, and page URL — the same fields that map directly to Open Graph tags.
Check Every Platform
See live previews for Facebook, X, LinkedIn, and Google side by side, styled to match each platform.
Copy the Meta Tags
Grab the generated Open Graph and Twitter Card tags and paste them straight into your page’s head.
What Each Platform Actually Shows
Facebook / Meta
Reads Open Graph tags specifically — og:title, og:description, and og:image — and caches the result, which is why old previews sometimes linger after you’ve updated a page.
X (Twitter)
Prefers its own Twitter Card tags but falls back to Open Graph tags if they’re missing — the card type you choose determines whether the image displays large or is dropped entirely.
Also reads Open Graph tags, but truncates descriptions more aggressively than Facebook, which is why a description that looks fine elsewhere can cut off awkwardly here.
Google Search
Doesn’t use Open Graph tags at all for its own snippet — it reads your actual page title tag and meta description separately, which is why this preview is included alongside the social cards.
Common Social Preview Mistakes
- Never leave the image tag empty. A card with no image gets far less engagement than one with a clear, relevant visual.
- Keep titles under roughly 60 characters. Longer titles get cut off differently across platforms, so shorter is safer everywhere.
- Write a real description, not a copy-pasted first sentence. The meta description is a chance to sell the click, not just summarize.
- Remember Facebook caches previews. If you update a page’s meta tags, use Facebook’s Sharing Debugger to force a re-scrape — the old card can otherwise persist for a while.
- Use a large image for X unless there’s a reason not to. The “summary_large_image” card type consistently outperforms the small summary card visually.
Frequently Asked Questions
Why does my page still show an old preview after I updated it?
Facebook and other platforms cache link previews. Updating your meta tags doesn’t automatically clear that cache — you typically need to use the platform’s own debugging tool to force a re-scrape.
Does this tool scan my live page automatically?
No — browsers can’t read another site’s raw HTML from client-side code, so this tool works by you entering your page details directly, not by scanning a URL automatically.
What image size should I use for social sharing?
A 1200×630px image is the most widely recommended size, matching the 1.91:1 aspect ratio most platforms expect for large image cards.
Do I need separate tags for Google and social platforms?
Yes — Google reads your standard title tag and meta description, while social platforms read separate Open Graph and Twitter Card tags. This tool previews both so you can check all of them at once.
What’s the difference between the two Twitter card types?
“Summary large image” displays a big image above the text; “summary” shows a small square image beside the text. Large image cards generally get more visual attention in the feed.
Is this tool free to use?
Yes — there’s no sign-up or account required. Enter your details, preview every platform, and copy the meta tags directly.
The WPOptimizers Social Share Preview tool renders live, accurate mockups — always verify your actual live page once published, since caching can delay how quickly platforms reflect changes.