Meta & Social

See your page the way Google and social platforms see it

Enter a URL and we fetch the real HTML, read every meta tag on it, and render the search result and each social card exactly as those platforms will build them.

We fetch the page and read its meta tags. Nothing is stored.

The previews are rendered from the meta tags actually present in the HTML your server returned, following each platform's documented fallback order — Open Graph first, then Twitter Card tags, then standard meta tags, then page content. Where a platform would fall back to something, the preview shows what it would fall back to.

The guide behind this tool Meta Tags and Social Previews: What Actually Shows Up Which tags Google, Facebook, X, LinkedIn and WhatsApp really read, in what order, and why your link looks right on one platform and broken on another. Read the guide · 5 min read →

What this tool checks

Every tag each platform reads, plus a rendered preview of what it will actually build.

  • Google result preview

    Your title and description rendered at the length Google displays, so you can see where truncation lands.

  • Facebook, LinkedIn, WhatsApp card

    Built from your Open Graph tags, following each platform's documented fallback order.

  • X card

    Including whether twitter:card is set to summary_large_image or you are getting the small thumbnail.

  • Title length

    Flagged if it will be cut off in search results, with the exact character count.

  • Description length

    Same, against the ~155–160 character limit Google displays.

  • og:image

    Present, absolute, and reachable. Missing it means each platform scrapes your page for any image it can find.

  • Canonical URL

    Whether one is declared, and whether it points where you expect.

  • og:locale

    Which language version a platform thinks it is looking at.

How to read your result

Look at the three preview cards first — they show what a real person sees, which is more useful than any score.

If the image is missing or wrong, that is the highest-impact fix. A link with no image gets a fraction of the clicks of one with a good image, on every platform.

If the title is truncated, the fix is not always to shorten it. Check that the distinguishing words come first — a title reading "Live Ajans — Global Web Design, Software & Performance…" wastes the visible space on the brand. "Global Web Design & Performance Advertising — Live Ajans" says more in the same room.

One thing to know before you fix anything: social platforms cache aggressively. Facebook holds Open Graph data for around 30 days and LinkedIn for about 7, and neither re-scrapes on its own. Fixing the tag does not fix an already-shared link — you have to force a refresh through the platform's own debugger. Check before you publish, not after.

Which tags each platform actually reads

Every platform reads a slightly different set of tags in a different order. That is why a page can look correct on Facebook and broken on LinkedIn.

Google

Uses <title> and <meta name="description">, but rewrites them freely when it thinks a page's own text answers the query better — which happens for roughly half of results. Titles are truncated around 580 pixels, which is about 55–60 characters. Descriptions run to about 155–160 characters on desktop and less on mobile.

Facebook, LinkedIn, WhatsApp, Slack, Discord

All read Open Graph: og:title, og:description, og:image, og:url, og:type. If og:image is missing they scrape the page for a suitable image, and the result is usually your logo or a random icon.

Image dimensions matter more than most people expect. 1200×630 is the safe size. Anything under 200×200 is ignored entirely, and a tall image gets cropped from the centre — which is how half a face ends up in a link preview.

X (Twitter)

Reads twitter:card, twitter:title, twitter:description and twitter:image, falling back to Open Graph when they are absent. twitter:card must be summary_large_image to get the large format; without it you get a small thumbnail regardless of image size.

The one that catches everyone

Social platforms cache aggressively. Fixing a tag does not fix an already-shared link — you have to force a re-scrape through the platform's own debugger. Facebook's Sharing Debugger and LinkedIn's Post Inspector both do this. Check before you publish, not after.

Frequently asked questions

Why does my page look right on Facebook but wrong on LinkedIn?

Almost always caching. LinkedIn caches Open Graph data for around seven days and does not re-scrape on its own. Run the URL through LinkedIn's Post Inspector to force a refresh. The other common cause is an image below LinkedIn's minimum size, where Facebook is more forgiving.

Google is not using my meta description. Why?

Google rewrites descriptions in roughly half of results, choosing text from the page that better matches the query. That is normal and not a fault. A well-written description still matters — it is what gets used for brand and navigational searches, which are the ones with the highest intent.

What image size should I use?

1200×630 pixels, under 5MB, in JPEG or PNG. That works everywhere. Add a separate 1200×1200 square version if a large share of your sharing happens on WhatsApp, which crops to square in some contexts.

Do I need both Open Graph and Twitter Card tags?

Not strictly — X falls back to Open Graph. But you do need `twitter:card` set to `summary_large_image`, or X shows the small thumbnail layout no matter how good your image is. That one tag is worth adding on its own.

Other free tools

SEO & Speed Audit

Real Core Web Vitals from Google's API, plus live on-page checks against your actual HTML.

Tell us what you are trying to grow.

One team. Three offices. Twenty-six languages. Send us the problem and you get a senior answer — not a sales script.

Get a proposal → Message us now

A written proposal within one business day, in your language.