Open Graph & Social Preview Checker
See how your link looks when shared, and fix the tags that break it.
Check a page’s social tags
Fetching the page from MySmartCoPilot’s server… slow sites can take up to a minute.
Social tags
Link previews (approximate)
Drawn from the tags with simple layouts of MySmartCoPilot’s own; the networks’ real cards differ in fonts, colours and truncation, and they cache what they fetched first.
What to fix
What we found
About the Open Graph & Social Preview Checker
Enter a page address, or paste its HTML, and the checker reads its Open Graph (og:) and X Card (twitter:) tags, falls back the way the platforms do when a tag is missing, and draws an approximate link preview for Facebook, X, LinkedIn, WhatsApp, Slack and Discord. It validates the tags against the Open Graph protocol — the required og:title, og:type, og:image and og:url, absolute URLs, duplicates, name written where property belongs — and looks at the preview image itself: whether it answers, its type and file size, and its pixel size, measured in your browser.
The image is judged against the numbers the platforms publish: Meta’s 200 × 200 minimum, 1200 × 630 recommendation and 8 MB limit, LinkedIn’s 1200 × 627 and 5 MB, and X’s sizes for its summary and large-image cards. Each finding says which platform it matters to, how to fix it and where the rule comes from.
How to use it
- Enter the page address in Page URL, or switch to Paste HTML and paste the page source (View page source, select all, copy). Add the page address next to pasted HTML so relative image paths can be resolved.
- Keep Load the preview image in my browser on to read the image’s pixel size and show it in the previews, and Check the image with MySmartCoPilot’s server to see its type, file size and redirects.
- Press Check tags. The six previews appear first, each with a note on where its title, description and image came from.
- Work through What to fix: errors (such as a missing or broken image) first, then warnings, then tips. Use the platform filter to see only what matters to one network.
- Open Tags found to see every social tag with its line number. After you fix the page, ask each network to fetch it again with its own tool (Facebook’s Sharing Debugger, LinkedIn’s Post Inspector): they cache previews.
Examples
og:image → https://www.example.com/img/share.png (320 × 320 px)
Warning: The Open Graph image is 320 x 320 px (1.00:1): Facebook shows it small Warning: The Open Graph image is 320 px wide: LinkedIn shows a thumbnail Tip: The Open Graph image is 1.00:1, not close to 1.91:1
Meta shows images under 600 × 315 pixels much smaller, and LinkedIn shows images under 401 pixels wide as thumbnails. A 1200 × 630 image avoids both.
<meta name="og:title" content="Chai Lab">
Warning: 1 Open Graph tag uses name= instead of property=
The Open Graph protocol is based on RDFa, where the attribute is property. Some crawlers accept name, others ignore it; twitter: tags are the ones that use name.
Common uses
- Checking a page before it is shared, announced or sent in a newsletter, so the preview is right the first time.
- Finding out why a link shows no picture, the wrong picture or the wrong title on one network.
- Auditing a template or SEO plugin that writes the tags for every page: duplicates, relative image paths and tracking parameters in
og:urlrepeat on every page. - Comparing what the six platforms would show for the same tags, including the X summary card and the large-image card.
What each platform reads
- Facebook and Meta apps:
og:title,og:description,og:image(withog:image:widthandheightso it loads the first time),og:url(the canonical, undecorated address),og:type(website by default) andfb:app_idfor Insights. Without Open Graph tags Facebook’s crawler guesses from the page (Meta: webmaster sharing). - X:
twitter:cardpicks the layout (summary,summary_large_image,apporplayer); the title, description and image fall back toog:title,og:descriptionandog:image. X’s reference says a summary card may be rendered whenog:type,og:titleandog:descriptionexist andtwitter:cardis absent (Cards reference, archived). - LinkedIn:
og:title,og:image,og:descriptionandog:urlmust exist (LinkedIn Help). - WhatsApp, Slack and Discord: they publish no tag rules of their own and build their cards from the same Open Graph (and, for Slack and Discord, Twitter Card and oEmbed) data.
Image sizes the platforms publish
- Meta: at least 200 × 200 px, at most 8 MB; 1200 × 630 px or more for the best display and 600 × 315 px for the larger card; keep the ratio near 1.91:1 (Images in link shares).
og:image:typeis one of image/jpeg, image/gif, image/png. - LinkedIn: at most 5 MB, at least 1200 × 627 px, ratio 1.91:1; images under 401 px wide show as thumbnails.
- X: summary card 1:1 from 144 × 144 px; large-image card 2:1 from 300 × 157 px; both up to 4096 × 4096 px, under 5 MB, JPG, PNG, WEBP or GIF (no SVG);
twitter:titleup to 70 characters andtwitter:descriptionup to 200 (summary card, large-image card, archived: X’s pages are no longer at their former addresses).
A single 1200 × 630 JPEG or PNG under 300 KB satisfies all three. The checker applies these numbers exactly as published and marks anything else as a tip.
The previews are approximations
The cards are drawn with simple layouts in MySmartCoPilot’s own styles, not in the networks’ fonts or colours, and the networks change their look and truncation without notice. They show what the tags say — which title, description and image a platform would pick, and the shape of the image — not pixel-exact renders. For the real thing, use each network’s own debugger after you publish the fix.
Limitations
- The previews are approximations (see above). Slack, WhatsApp and Discord publish no limits, so nothing is checked for them beyond the shared tags and the image.
- The checker reads the
<head>as the server sends it and never runs scripts: tags added by JavaScript after load are not seen, and the same is true for most social crawlers. - A site can answer MySmartCoPilot’s server differently from Facebook’s or LinkedIn’s crawlers (bot protection, country rules, login walls). The networks also cache: after a fix, ask them to fetch the page again.
- The image check asks for the first four distinct image addresses only. The pixel size comes from your browser, which may be unable to load an image that blocks hotlinking or uses an http:// address on an https page; the server check still applies then.
- X’s Cards reference no longer exists at its former address; its figures here come from the last archived copy, which is linked.
- Each visitor can run a limited number of fetches per hour (and the whole site a limited number per day) to stay within free hosting limits.
Privacy
In Page URL mode the address is sent to MySmartCoPilot’s server, which fetches the page’s head; if the server image check is on, the preview image’s address is sent too. MySmartCoPilot does not store addresses, HTML or results; the server log records only the host name, status code and time of each request. Loading the preview image in your browser is a normal request from your device to the image’s server, which can see your IP address. Untick the option to avoid it. In Paste HTML mode the HTML stays in your browser, and image addresses are sent to MySmartCoPilot only if you tick the server check.
Frequently asked questions
Which Open Graph tags are required?
The protocol lists four: og:title, og:type, og:image and og:url. Platforms are more forgiving in practice: Facebook defaults og:type to website and guesses missing values, and X falls back to the Open Graph tags. The checker treats a missing or broken og:image as an error, because a link preview without a picture is the most visible failure, and the other missing tags as warnings or tips.
What size should an Open Graph image be?
1200 × 630 pixels (ratio 1.91:1), as JPEG or PNG, under about 300 KB. Meta recommends at least 1200 × 630 and accepts files up to 8 MB; LinkedIn wants at least 1200 × 627 and up to 5 MB. X’s large-image card prefers 2:1, for example 1200 × 600; a 1200 × 630 image works there too.
Why does the real preview differ from what this tool shows?
The previews are approximations, and the networks cache. Facebook and LinkedIn keep the title, description and image they fetched first until their crawler fetches the page again, so a fix shows only after you ask the Sharing Debugger or Post Inspector to re-scrape it. The image URL is part of the cache key: changing the file at the same address does not update old previews.
Is this a replacement for the Twitter Card validator and the Facebook debugger?
For checking tags, image sizes and the way the platforms fall back, yes. It cannot fetch the page as Facebook’s, LinkedIn’s or X’s own crawlers do, and it cannot refresh their caches, so use the networks’ own tools (Sharing Debugger, Post Inspector) for that last step.
Why is my og:image not loading in the browser check?
Some servers refuse images requested from other sites (hotlink protection), and an http:// image cannot be loaded on an https page. If the server check shows status 200 and an image type, crawlers can probably still fetch it. If both fail, the address is wrong, private or blocked.