Open Graph Checker

Open Graph (OG) tags are HTML meta tags that control how your web pages appear when shared on social media platforms like Facebook LinkedIn Slack and Discord. Created by Facebook in 2010 the Open Graph protocol transforms your page into a rich object in a social graph giving you control over the title description image and URL that appear in the share preview card. The four essential OG tags are og:title (the headline shown in the preview) og:description (a brief summary) og:image (the preview image) and og:url (the canonical URL). Additional tags like og:type (article website product) og:site_name og:locale and og:video let you provide even more context about your content. Without OG tags social platforms attempt to auto-generate previews by scraping your page content. The results are unpredictable — they might grab the wrong image truncate your title awkwardly or display a generic description. Properly configured OG tags give you complete control over your social presence ensuring every share looks professional and drives maximum click-through. Studies show that posts with optimized preview cards receive significantly higher engagement than those with generic or missing previews.

If your pages display incorrect or missing preview cards when shared on social media start by checking that all four required OG tags are present in your HTML head section. The most common issue is a missing og:image tag or an image URL that is unreachable. Social platforms cache aggressively so even after fixing your tags you need to clear the cached version. For Facebook use the Sharing Debugger (developers.facebook.com/tools/debug/) to scrape fresh data. For LinkedIn append a query parameter to your URL and share it again to bypass the cache. For Twitter use the Card Validator. Slack respects the standard OG tags and updates its cache automatically after a few hours. Image specifications matter. Facebook recommends 1200x630 pixels for the og:image. Images smaller than 600x315 pixels may not display as large cards. Use absolute URLs (starting with https://) for all OG values — relative URLs will fail. Ensure your images load quickly and your server responds with correct CORS headers. Test every important page before launching or sharing. Social preview appearance directly impacts click-through rates and traffic making it one of the highest-ROI optimizations you can make for content distribution.

Twitter Cards and Open Graph serve the same purpose — controlling how shared links appear — but they are separate specifications maintained by different platforms. Twitter Cards use twitter: prefixed meta tags (twitter:card twitter:title twitter:description twitter:image) while Open Graph uses og: prefixed tags. Twitter supports four card types: summary (small square image with text) summary_large_image (wide image above text) app (mobile app install card) and player (inline video/audio). The most commonly used type is summary_large_image which produces the wide image cards you see in most tweet link previews. The good news is that Twitter falls back to Open Graph tags when Twitter-specific tags are not present. If you have og:title Twitter will use it as the title when twitter:title is missing. This means implementing OG tags gives you baseline coverage across all platforms. However adding Twitter-specific tags lets you customize the presentation for Twitter independently — for example using a different image aspect ratio or a more concise title. Best practice is to include both OG tags and the essential Twitter Card tags (twitter:card twitter:title twitter:description twitter:image). This gives you full control on every platform while keeping the meta tag overhead minimal.

Open Graph (og:*) was created by Facebook in 2010 and is now the de-facto standard used by LinkedIn Slack Discord iMessage and most other platforms. Twitter Cards (twitter:*) is Twitter/X's older format. If both are present Twitter uses its own tags; if only og:* is present Twitter falls back to them. In practice set og:* tags on every page and add twitter:card + twitter:site on top. You rarely need the full twitter:* set.

1200 × 630 pixels JPEG or PNG under 8 MB (most platforms prefer under 1 MB for fast preview loading). This 1.91:1 aspect ratio renders cleanly on Facebook LinkedIn Slack Discord and iMessage without cropping. Avoid 1:1 square images — they crop poorly on most platforms. For Twitter twitter:card = summary_large_image uses the same dimensions. Absolute URLs only (not relative paths) served over HTTPS.

Yes ideally — a generic site-wide og:image wastes the strongest click-through signal Facebook/LinkedIn give you. Use Next.js's ImageResponse (via opengraph-image.tsx or Vercel's @vercel/og to render per-page OG images at request time. Cache them at the edge. Include the page title category and brand styling. CheckFast itself uses dynamic OG images on tool pages — they dramatically improve CTR from social shares vs. a generic logo.

Platforms fall back to guesswork: they use the page the first and the first prominent image from the page body. Results are usually ugly — low-resolution images truncated or irrelevant descriptions or the site logo as the preview. Worse some platforms (LinkedIn in particular) cache these bad guesses for weeks. Fix the tags then use each platform's debugger (Facebook Sharing Debugger LinkedIn Post Inspector Twitter Card Validator) to force a cache refresh.

Not functionally — parsers scan the entire for meta tags regardless of order. But social-media scrapers often stop reading after the first ~100 KB of HTML to save bandwidth so if your is bloated with inline scripts and style blocks before the og tags scrapers may truncate before reaching them. Best practice: put all og:* and twitter:* meta tags near the TOP of before any or large inline CSS.