1. Paste a public URL
Use an article, landing page, product, offer, or campaign destination.
Cookies
Your privacy, clearly explained
We use cookies to keep LinkDirect secure, improve performance, and understand how people use the product.
Paste a public URL to inspect its Open Graph and social metadata, then compare realistic cards for Facebook, X, LinkedIn, and messaging apps before your campaign goes live.
LinkDirect requests the public page once, follows safe redirects, reads its metadata, and turns the result into visual sharing previews.
Use an article, landing page, product, offer, or campaign destination.
We check Open Graph, Twitter Card, canonical, title, description, image, and related fields.
Switch between platform cards and fix missing or weak metadata before publishing.
The checker separates what was detected from what each social card may actually display.
Review og:title, og:description, og:image, og:url, og:type, site name, locale, and image dimensions.
Verify card type, title, description, and image without digging through page source.
See the final URL after redirects and confirm whether the page declares a canonical destination.
Social networks render cards from page metadata, not from the visible hero section. Missing, stale, or conflicting tags can produce an unexpected result.
A platform may show a text-only card or choose another image when og:image is absent or inaccessible.
Long titles and descriptions are truncated differently by each platform and device.
Redirects, canonical tags, and platform caches can make the shared card differ from the URL you pasted.
No. The tool only reads the public metadata returned by the URL. It does not connect to or publish on any social account.
No checker can guarantee a pixel-perfect result because platforms change layouts, crop images, cache metadata, and run their own rules. The preview is a practical approximation based on the detected tags.
Facebook and other platforms cache link metadata. After fixing the page, use the platform’s own sharing debugger to request a fresh scrape.
The page is fetched to generate the response and enforce abuse limits. The checker does not create a saved project or public archive of the inspected page.
Create smart links that keep the destination URL intact, add browser-aware handoffs, and show what happened after the click.