Open Graph Preview — See How Your Link Looks on Social Media
Enter a URL and see the exact card Facebook, LinkedIn, X and Slack will show, every tag found, and what is missing.
Only the page's tags are fetched, by our server, on your request; nothing about you is stored. Social cards are one visible symptom of a site's technical SEO. Ask us for a full audit.
Found a problem, or something that could be better? We read every message and we fix things quickly.
This free Open Graph preview tool fetches any public page and shows the link card that Facebook, LinkedIn, X and Slack will build from its tags, the way they build it: title, description, image, site name, cropped and truncated as each platform does. It lists every og: and twitter: tag it found, measures the share image, and scores the page with a specific fix for each failure.
Link previews are decided entirely by a handful of meta tags, and they fail silently: a missing og:image turns a shared article into a bare grey link, an image under 600 px wide becomes a thumbnail, a title over 70 characters is cut mid-word. Checking here before you share, or after a deploy, takes ten seconds and catches all of it. Because the fetch is done by our server on your request, it also shows what a crawler sees rather than what your logged-in browser sees.
How to use
- Paste the page URL and press Preview. The page must be publicly reachable; localhost and password-protected staging sites cannot be fetched.
- Look at the three cards. If they show a bare title or no image, the tags are missing or the image is not loading.
- Read the checks. Each failed line says what to add or change; the meta tag generator produces the missing tags.
- Fix, deploy, then Re-check. If Facebook or LinkedIn still show the old card, they cached it: re-scrape in Facebook's Sharing Debugger or LinkedIn's Post Inspector.
Frequently asked questions
Why does the preview differ from what LinkedIn or Facebook shows?
Caching. Both platforms store the first version of a link's card they see, sometimes for weeks. This tool always fetches the live tags. To refresh a platform's cache, use Facebook's Sharing Debugger (which also updates Instagram and WhatsApp) or LinkedIn's Post Inspector. X refreshes on its own within a day or so.
What size should og:image be?
1200 × 630 pixels, ratio 1.91:1, under about 5 MB, served over HTTPS at an absolute URL. That produces the large card everywhere. Images narrower than 600 px fall back to a small thumbnail on Facebook and LinkedIn. Square images are cropped; keep the subject centred.
Which tags do I need at minimum?
og:title, og:description, og:image and og:url. Add og:site_name and og:type, and twitter:card set to summary_large_image so X uses the big image. X reads og: tags as a fallback for anything twitter: does not specify.
The tool says the page redirected. Is that a problem?
Usually not: http to https and non-www to www redirects are normal, and the tool follows them. It becomes a problem when a share link redirects through a tracking domain that serves no tags, or when a redirect chain is slow enough that a platform's crawler gives up. Share the final URL directly when you can.
Can it preview a page behind a login or on localhost?
No. The fetch is made from our server, so it only sees what any anonymous visitor sees, which is also what social crawlers see. For a local page, deploy to a preview URL first. Requests to private network addresses are refused by design.
Is anything stored?
The URL is fetched on request, the tags are returned to your browser and nothing is kept. Only the page's head tags are read, up to 1 MB.
How each platform builds the card
Facebook and LinkedIn read og:* and show image, title and domain (LinkedIn omits the description in feeds). X reads twitter:* first and og:* as fallback, and chooses the large or small layout from twitter:card. Slack, Discord and iMessage read og:* and show site name, title, description and the image, in that order. WhatsApp shows a thumbnail from og:image and the title. None of them execute JavaScript, so tags injected client-side are invisible to them; render the tags on the server.
Common causes of a broken preview
• og:image is a relative path or an http URL on an https site.
• The image is blocked by robots.txt or requires a login.
• A CDN or bot-protection layer serves a challenge page to crawlers.
• The page sets the tags in JavaScript after load.
• og:url points at a different page, so the platform previews that one instead.
Related free tools
- Meta Tag Generator — Fill in a page's title, description and social card details; get a complete, correctly escaped <head> block with live length counters.
- SERP Snippet Preview — Preview how your page title and meta description will look in Google — with live character-count checks.
- UTM Link Builder — Build clean, consistent UTM tracking links so you know exactly which campaigns bring you customers.