induwara.lk
induwara.lkDeveloper · SEO

Meta Tag Preview — Open Graph, X, Facebook, LinkedIn & Slack

Type the meta tags or paste your <head> HTML and watch live previews of how every major platform will render the share card. Lengths and image aspect ratios are validated against each platform's published display rules. No signup, no analytics.

By Induwara AshinsanaUpdated May 11, 2026
Preview your social share cardOG · X · LinkedIn · Slack · Google
OG Protocol · X Cards

Used in tabs, on Google, and as og:title. Aim for 60 chars or under.

Absolute URL of the page being shared (sets og:url and canonical).

Snippet shown by Google and most social platforms. ~160 chars works everywhere.

Absolute URL, 600px+ wide, ~1.91:1 aspect ratio (1200×630 is the safest target).

Brand label shown beneath the title on Facebook/LinkedIn (og:site_name).

Quick actions

Live previews

Google · search result
your-domain.com

Your page title shows here

Your meta description appears here in the SERP snippet.

X (Twitter) · summary_large_image
yourdomain.com
Your title here
Facebook · feed
yourdomain.com
Your page title
LinkedIn · post
Your page title
yourdomain.com
Slack · link unfurl
Your page title

Validator

Errors
2
Warnings
2
Card type
summary_large_image
  • No <title>, og:title, or twitter:title found.
  • No description meta tag or og:description found.
  • No og:image or twitter:image set. Posts without an image render as a plain text link on most platforms.
  • No og:url or canonical link set. Add one so each share resolves to the right page.

Limits sourced from the OpenGraph Protocol spec, X/Twitter Cards docs, Google Search Central, and LinkedIn's Post Inspector guidance — see the “Sources” section below.

How it works

The previews on this page are not screenshots of someone else's rendering — they are computed from your input using the same character limits and image rules the platforms publish themselves. Three pieces of behaviour drive what you see:

  1. Tag resolution. Most platforms prefer platform-specific tags but fall back to Open Graph when absent. The tool follows the documented order: X uses twitter:* then og:*; Facebook and LinkedIn use og:*; Google's SERP prefers the page's <title> tag and the standard <meta name="description">.
  2. Truncation.Strings are cut at the grapheme-cluster boundary closest to the platform's display limit — 60 graphemes for Google titles, 160 for descriptions, 70 for X card titles, 200 for X descriptions, 200 for Facebook / LinkedIn descriptions. Using grapheme counting (via Intl.Segmenter) means a flag emoji counts as 1, not 2, matching what users actually see.
  3. Image handling. Relative image URLs are resolved against og:url or link rel="canonical". Non-https URLs and unreachable images produce a friendly placeholder; the validator records the failure so you can fix the tag before it costs you a share. The aspect ratio target is 1.91:1 — that's the lowest-common-denominator across X's summary_large_image, Facebook, LinkedIn and Slack.

The optional “Fetch URL” tab is the only path that touches the network. It calls /api/meta-fetch which makes a server-side request with an 8-second timeout, a 1 MB response cap, a strict text/html content-type check, and IPv4 private / loopback / link-local blocking to prevent the route from being used as a request proxy. The HTML is parsed entirely in your browser after that.

Worked examples

Scenario

Fully-tagged page (the happy path)

  1. Input: <title>induwara.lk — Tools for Sri Lankans</title>
  2. <meta property="og:title" content="…">
  3. <meta property="og:image" content="https://…/og.png">
  4. <meta name="twitter:card" content="summary_large_image">
  5. Resolved title: <title> on Google · og:title on Facebook/LinkedIn
  6. Resolved image: 1200×630 OG card on X, Facebook, LinkedIn, Slack
  7. Validator: 0 errors, 0 warnings

Scenario

Missing description (common bug)

  1. Input: title and og:image set, but no description / og:description
  2. Google preview: shows '(no description)' — Google may auto-extract page text
  3. X preview: card renders but description line is blank
  4. Validator: 1 error — 'No description meta tag or og:description found.'
  5. Fix: add <meta name="description" content="…"> and og:description

Scenario

Title that's too long (truncation test)

  1. Input title: 'Sri Lanka Income Tax Calculator (APIT) — 2025/26 Year of Assessment — Free' (75 chars)
  2. Google: truncates to ~60 chars → 'Sri Lanka Income Tax Calculator (APIT) — 2025/26 Year of…'
  3. X (Twitter): truncates to ~70 chars
  4. Validator: 2 warnings — exceeds Google (60) and X (70) limits
  5. Fix: rewrite to ≤60 chars; put the keyword first; trust the brand suffix to be added by the platform

Frequently asked questions

Sources & references

Display limits and tag-precedence rules on this page were last cross-checked against the sources above on 2026-05-11. The page is reviewed whenever a major platform updates its rendering rules.

Related tools

Rate this tool
Be the first to rate

Comments & feedback

Spotted a bug or want an improvement? Tell us — our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Spotted a platform-specific rendering quirk, or want a Discord / WhatsApp preview added?

Email me at [email protected] — most fixes ship within 24 hours.