Open Graph Tag Checker
Preview and validate Open Graph tags for social media sharing.
Why Most Pages Have Broken Social Previews (And Do Not Know It)
When someone shares a URL on Slack, LinkedIn, Facebook, or iMessage, the platform's crawler fetches that URL and reads its Open Graph tags to construct a preview card. If those tags are missing, incorrect, or point to a broken image, the platform falls back to heuristic extraction — grabbing the first image it finds on the page, truncating the page title at an arbitrary length, and showing no description. The result is an ugly, unbranded preview that gets clicked far less than a properly configured card.
The problem is that most CMS setups only generate OG tags for certain page types (the homepage, blog posts) while leaving product pages, landing pages, and tool pages without any OG configuration. A single missing og:image tag on a high-traffic page can silently suppress thousands of potential social clicks per month.
Platform-Specific Requirements: One Tag Does Not Fit All
The Open Graph protocol (defined by Facebook) established the base spec. Twitter/X, LinkedIn, and Slack each have their own extensions and rendering behaviors:
- Facebook: Reads og:* tags. Image: 1200×630px minimum. Uses og:image:width and og:image:height to avoid aspect-ratio detection delays. Will not display images under 200×200px.
- Twitter/X: Reads its own twitter:* tags first, falls back to og:* tags. twitter:card must be set to either "summary" (square image thumbnail) or "summary_large_image" (full-width image header). Without twitter:card, no card is rendered at all — just a plain link.
- LinkedIn: Reads og:* tags. Image minimum: 1200×627px. LinkedIn caches previews aggressively — after changing OG tags, you must use the LinkedIn Post Inspector to force a cache refresh, or shares for 7+ days will show the old image.
- Slack: Reads og:* tags. Slack renders previews inline in channels and DMs. It respects og:image but does not display images that return HTTP errors or redirect chains. Slack also reads schema.org JSON-LD for article metadata.
- iMessage/WhatsApp: Reads og:* tags for link previews. Image must be accessible without authentication; CDN-cached images work well, auth-gated images do not render.
The og:type Tag: More Than a Formality
Most implementations set og:type to "website" and move on. But the type tag affects how platforms parse the remaining OG data. Setting og:type to "article" unlocks article-specific tags: article:published_time, article:author, article:section, and article:tag. LinkedIn and Facebook parse these to display richer article metadata. News publishers and blogs that omit the article type are leaving structured metadata unused that could improve how their content appears in social feeds and aggregators.
Common OG Tag Failures
- og:image points to a relative URL — OG images must be absolute URLs including the https:// scheme. Relative paths like /images/hero.jpg are not valid.
- og:image returns a redirect — Some platforms do not follow redirects when fetching OG images. CDN redirects, HTTP-to-HTTPS redirects, and URL forwarding can silently break image rendering.
- Missing og:url canonical — Without og:url, likes and shares can get split across multiple URL variations of the same page (with/without trailing slash, UTM parameters, etc.), reducing the social proof count displayed on each.
- Image dimensions not specified — Some platforms must download the full image to detect its dimensions before deciding whether to display it. Specifying og:image:width and og:image:height allows the platform to skip this step, resulting in faster preview rendering.
How to Use This Tool
- Enter the URL you want to inspect.
- The tool fetches and displays all Open Graph and Twitter Card tags found on the page.
- A social preview card shows how the page will appear when shared.
- Use the tag analysis to identify missing or incorrectly configured tags.
▎ FAQ
01 Do Open Graph tags directly affect Google search rankings? +
No. Google does not use Open Graph tags as ranking signals in organic search. OG tags are read by social media platforms and messaging apps for link preview rendering, not by Google's ranking algorithms. The indirect SEO benefit comes from better social previews driving more shares and clicks, which can generate referral traffic and natural backlinks — both of which do influence rankings. But the OG tags themselves are not in Google's ranking equation.
02 I updated my og:image but the old image still shows when I share the link. Why? +
Social platforms aggressively cache Open Graph data after the first fetch. Facebook's cache persists for up to 24 hours but can be force-refreshed using the Facebook Sharing Debugger. LinkedIn's cache is the longest — use the LinkedIn Post Inspector to force a refresh. Twitter/X typically refreshes within a few hours. For immediate cache invalidation on all platforms, the most reliable approach is to change the og:image URL itself (by adding a version query parameter like ?v=2) so platforms treat it as a new image.
03 What is the difference between og:title and the HTML title tag? +
The HTML title tag is what appears in the browser tab and is the primary signal Google uses for search result titles. The og:title is used exclusively by social media platforms for link preview cards. They serve different audiences in different contexts and should often be written differently. Your HTML title might be "Image Compressor — Reduce File Size Online | SiteName" (optimized for SERP keyword matching). Your og:title might be "Compress Images in Seconds — No Upload Required" (optimized for social media engagement and click intent).
04 My page has no Open Graph tags at all. What does it look like when shared? +
Without OG tags, each platform falls back to its own heuristics. Facebook grabs the first image it finds on the page (often a logo, icon, or random inline image) and truncates the page title. LinkedIn may show no preview image at all. Twitter renders a bare text link with no card. The result is a generic, unbranded preview that gets significantly fewer clicks than a properly configured card. For any page you expect to be shared socially, OG tags are not optional.
