Open Graph Preview & Social Card Validator

When visitors share your links on WhatsApp, LinkedIn, Facebook, or X, social platforms read Open Graph (og:*) and Twitter Card meta tags to build visual preview cards. This tool inspects your live server-delivered HTML, validates image URLs, flags missing or fallback values, and renders visual preview approximations.

What this tool helps with

The Open Graph Preview Tool helps with identifying missing og:title, og:description, or og:image tags, testing fallback HTML behavior, catching malformed image URLs, and checking canonical og:url alignment before launching content or marketing campaigns.

How to use the result

  1. Enter the exact public webpage URL you plan to share.
  2. Review your Share Readiness score and verify which tags were explicitly declared versus inferred from HTML fallbacks.
  3. Inspect the visual preview card approximations for WhatsApp, LinkedIn, and Facebook.
  4. Address flagged issues such as missing images, truncated titles, or relative image paths.

Best practices for stronger results

  • Always declare an explicit og:image with recommended 1200x630px resolution and 1.91:1 aspect ratio.
  • Use full absolute HTTPS URLs for og:image and og:url, not relative paths.
  • Keep og:title between 40 and 60 characters to prevent truncation on mobile feeds.
  • Serve meta tags in initial server-side HTML (SSR); social scrapers do not run client-side JavaScript.

Important: It cannot guarantee rankings because competition, backlinks, content quality, and search-engine decisions are outside a page-level scan.

Why Open Graph tags matter for organic social traffic

Links shared on messaging apps and social networks without visual preview cards receive significantly lower click-through rates. Rich snippets with compelling imagery, clear titles, and informative descriptions establish immediate credibility and context.

Platforms like WhatsApp, LinkedIn, and Facebook maintain independent scraping bots (e.g. WhatsApp/2.x, LinkedInBot, facebookexternalhit). Because these bots cache scraped metadata for hours or days, testing your tags before sharing is critical.

Understanding fallbacks and image validation

When og:title is omitted, platforms often fall back to the standard HTML <title> tag. While this ensures a title appears, dedicated Open Graph copy is usually more engaging for social feeds than an SEO-focused page title.

Our validator checks that your image URL is publicly accessible, absolute, and not pointing to private or restricted networks. Note that visual previews are approximations; platforms independently crop and style cards based on device viewport.

Open Graph Preview Tool FAQs

Answers to common questions before you use this free online tool.

Why does my shared link not show an image on WhatsApp or Facebook?

Common causes include a missing og:image tag, a relative image URL that the scraper cannot resolve, an image file that exceeds platform size limits (keep under 5MB), or a server that blocks social scraper user-agents.

What is the recommended size for an Open Graph image?

The optimal size across all major platforms is 1200 x 630 pixels (an aspect ratio of 1.91:1). This ensures high-resolution display without awkward cropping on both desktop and mobile feeds.

Why does WhatsApp or LinkedIn show old preview details after I updated my tags?

Social platforms aggressively cache Open Graph metadata. On Facebook/LinkedIn you can use platform debugger tools to force a cache refresh; on WhatsApp, appending a version query parameter (e.g. ?v=2) can trigger a fresh scrape.

Do social scrapers execute client-side JavaScript?

Generally no. Social crawlers make lightweight HTTP GET requests to inspect raw HTML. If your Single Page Application (SPA) injects meta tags dynamically in browser JavaScript, scrapers will only see an empty shell.