Open Graph Checker
Check a page's og: and twitter: tags and preview how its link card may look on Facebook, X and LinkedIn before you share it.
The interactive tool loads here when JavaScript runs.
About this toolWhat is the Open Graph Checker?
The Open Graph Checker reads every og: and twitter: meta tag on a page and lays them out one per row, with the og:image shown inline. Below that it draws approximate link previews in the style of Facebook, X (Twitter) and LinkedIn using the title, description, image and site name it found.
Each tag is labelled. og:title, og:description, og:image and og:url are marked required, og:type, og:site_name and twitter:card recommended, and anything else optional. When a tag appears twice, the first value is kept, which matches how Facebook reads single-valued properties.
Browsers do not let one site read another site's HTML (the same-origin policy and CORS), so the page is fetched through the public allorigins.win proxy and parsed in your browser. The URL you enter is therefore sent to that third-party service. The previews are drawn here, not fetched from the platforms, so treat them as a layout check. Each network caches cards and applies its own cropping.
- Lists every og: and twitter: tag on the page
- Required, recommended and optional badges
- Inline og:image thumbnail with relative paths resolved
- Approximate Facebook, X and LinkedIn previews
- Parsing is local; the page is fetched through a public CORS proxy
Updated
How to use the Open Graph Checker
- Paste the page address, including https://, into the URL box.
- Click Check Tags or press Enter.
- Review the Analysis Results list. Each tag shows its value, a required, recommended or optional badge, and a copy button; og:image renders as a thumbnail.
- Scroll to Social Media Preview to see approximate Facebook, X and LinkedIn cards built from those tags.
Worked examples
Relative og:image
Input
<meta property="og:image" content="/images/card.png"> on https://example.com/blog/post
Output
og:image: /images/card.png (preview loads https://example.com/images/card.png)
The checker resolves the path so you can see the picture, but Facebook expects an absolute URL. Change the tag to the full https:// address.
Missing twitter:image
Input
og:title, og:description and og:image set; only twitter:card="summary_large_image" for X
Output
X preview uses the og:image and og:title
X falls back to Open Graph values, so duplicating every field as twitter: tags is optional.
Background and insight
Open Graph was introduced by Facebook in 2010 so any web page could become a rich object in the social graph. The protocol at ogp.me defines four required properties: og:title, og:type, og:image and og:url. Almost every chat app and social network now reads them to build link previews, including Slack, Discord, LinkedIn, iMessage and WhatsApp.
X (Twitter) has its own card tags. twitter:card picks the layout (summary or summary_large_image are the common ones) and X falls back to og:title, og:description and og:image when the twitter: equivalents are missing, so most sites only need twitter:card plus the Open Graph set. X documents its tags with the name attribute; Open Graph uses property.
The most common breakage is the image. og:image must be an absolute URL that a crawler can fetch without cookies; relative paths, images behind authentication, and huge files fail silently. 1200 by 630 pixels (about 1.91:1) is the size Facebook recommends for large cards and works well elsewhere. After you fix tags, platforms keep showing the old card until their cache is refreshed: Facebook has the Sharing Debugger and LinkedIn the Post Inspector for that.
Common use cases
Before posting a launch link
Make sure the card shows the right headline and image, not the homepage defaults.
Debugging an ugly Slack unfurl
See which og:image and og:description the page really serves.
Checking per-route tags in an SPA
Confirm each route ships its own Open Graph tags in the server HTML.
Reviewing a CMS template
Verify that blog posts fill og:type="article" and a post-specific image.
Tips and limitations
- Use absolute https URLs for og:image and og:url. Many crawlers do not resolve relative paths.
- Keep the important part of the image in the centre; networks crop large cards differently.
- After fixing tags, refresh the platform's cache with the Facebook Sharing Debugger or LinkedIn Post Inspector, or the old card keeps showing.
- Social crawlers usually do not run JavaScript. If tags are injected client-side, prerender the page.
- The previews here are approximations. Fonts, truncation and cropping on the real platforms change without notice.
Sources and further reading
- The Open Graph protocol, Open Graph protocol. The og: properties, including the four required ones
- What's in the head? Web page metadata, MDN Web Docs. How meta elements and Open Graph tags fit in the HTML head
- Post Inspector, LinkedIn. Refreshes LinkedIn's cached preview of a URL
Frequently asked questions
Which Open Graph tags are required for a link preview?
The Open Graph protocol lists four required properties: og:title, og:type, og:image and og:url. In practice og:title and og:image decide whether a card looks good, and og:description fills the second line. Add twitter:card for X; it falls back to the Open Graph values for title, description and image.
What size should an og:image be?
Use 1200 by 630 pixels, about a 1.91:1 ratio, which is what Facebook recommends for large link cards and which LinkedIn and X display well. Keep the file reasonably small, serve it over https from a public URL, and keep text away from the edges in case a platform crops it.
Why is Facebook still showing my old preview image?
Facebook caches the scraped tags for a URL. Open the Sharing Debugger, enter the URL and click Scrape Again to fetch fresh tags. LinkedIn has the equivalent Post Inspector. Changing the image file name also helps, because some platforms cache the image separately from the page.
Do I need both og: tags and twitter: tags?
Usually not. X reads twitter:card to choose the layout and falls back to og:title, og:description and og:image when twitter: versions are missing. Set the Open Graph tags plus twitter:card, and add twitter:site if you want the card attributed to your account.
Why does the Open Graph Checker find no tags on my single-page app?
The checker reads the HTML your server returns and does not execute JavaScript, just like most social crawlers. If your app adds og: tags on the client after load, they are not in that HTML. Prerender or server-render routes so the tags exist in the initial response.
Are these previews exactly what Facebook, X and LinkedIn will show?
No. They are drawn locally from the tags to show which title, description and image each platform is likely to pick. Real cards depend on each network's current layout, image cropping, cached data and content policies, so confirm important shares with the platform's own debugger.
Is there an in-depth guide to the Open Graph Checker?
Yes. “Meta Tags That Still Matter: Titles, Descriptions and Open Graph” covers the background, how it works, common pitfalls and worked examples. Read the full guide.
Related Tools You May Like
Free, in-browser tools that pair well with this one.