Entrovix AI

Open Graph Generator

Builds Open Graph and Twitter Card tags with live previews of the Facebook, LinkedIn and WhatsApp cards — and catches the absolute-URL mistake that breaks most of them.

Runs in your browser — nothing is uploaded

Page details

0 characters · Facebook shows ~88, X ~70

0 characters · LinkedIn cuts near 155

Preview

How the link renders when it is shared. Each platform crops differently.

No og:image — the card will be a grey box

EXAMPLE.COM

Your page title appears here

Your description appears here.

WhatsApp

Your page title appears here

Your description appears here.

EXAMPLE.COM

Meta tags
<meta property="og:type" content="website" />
<meta property="og:locale" content="en_IN" />
<meta name="twitter:card" content="summary_large_image" />
Checks
2 Errors3 Warnings
  • og:title is missing

    Without it, every platform falls back to the <title> tag or the bare URL.

    Add a title. It can differ from the SEO title — this one is written to be clicked in a feed.

  • og:image is missing

    This is the single biggest factor in whether a shared link gets clicked. Without it the card is a grey box.

    Add a 1200×630 image URL.

  • og:description is missing

    The card shows a bare link with no explanation, which measurably reduces clicks.

    Write one or two sentences. Around 155 characters survives everywhere.

  • og:url is missing

    og:url is the canonical address for sharing. Without it, the same page shared with different tracking parameters counts as several different pages.

    Set it to the clean canonical URL of the page.

  • summary_large_image with no image

    X falls back to a plain card, or shows nothing at all.

    Either add an image or set the card to summary.

Platforms cache aggressively. After changing these tags, run the page through Facebook's Sharing Debugger to force a refresh — otherwise the old preview keeps appearing for days.

Why use it

Built to be genuinely useful

See the card before you ship

Feed-style and WhatsApp-style previews, so you know what people will actually see.

Catches the usual killer

A relative og:image is why most previews show a grey box. Platforms fetch it from their own servers, where /og.png means nothing.

Twitter tags included

X reads its own tags and falls back awkwardly. Both sets are generated together.

Nothing is uploaded

It runs in your browser. Your keyword list and your draft copy are a content plan — they should not have to leave the machine to be analysed.

How it works

Three steps

  1. 1

    Enter the title, description, URL and image.

  2. 2

    Check the previews and the warnings.

  3. 3

    Copy the tags into your page's head.

Why the preview is worth more than the traffic

When a link is shared on WhatsApp, LinkedIn or X, the preview card is the entire advertisement. A card with a clear image and a real headline is a link people tap; a bare blue URL with no image is a link people scroll past, whatever is behind it.

In India this weighs more heavily than the global averages suggest, because so much sharing happens in WhatsApp groups rather than on public feeds. A link forwarded into a group of forty people either carries a card or does not, and that single difference decides whether anyone opens it.

It costs about six lines of HTML, set once per page, usually by a template. It is one of the few genuinely high-return, low-effort things left in this area.

The mistake that breaks most cards

A relative og:image. Writing content="/images/og.png" works everywhere else in HTML, because your browser resolves it against the current page — and fails here, because Facebook, LinkedIn and WhatsApp fetch the image from their own servers, where that path resolves to nothing.

The result is a card with no image and no error message, which is why it survives so long: nothing tells you, and the person who shared the link is not the person who wrote the tag. Every image URL must be absolute, starting with https://.

Two more that follow closely: an image served over http, which some platforms refuse to load into an HTTPS context, and og:url pointing at a tracking-parameter version of the page, which fragments the share count across every campaign that ever linked to it.

Sizing, caching and testing

1200×630 is the size to use. It is the standard large-format ratio, and it degrades acceptably everywhere else — including WhatsApp's small square thumbnail, which centre-crops. Keep essential text away from the edges, because different platforms crop differently.

Every platform caches aggressively. Change your tags and the old preview keeps appearing for days, which is exactly when people conclude the tags do not work and start rewriting things that were already correct.

Force a refresh instead: Facebook's Sharing Debugger, LinkedIn's Post Inspector and X's card validator each re-fetch on demand. WhatsApp uses Facebook's cache, so the Sharing Debugger covers it too. Run those once after publishing and the problem disappears.

FAQ

Questions people ask

Need a tool like this for your business?

We build internal tools, dashboards and automation that fit how your team works.

See Our Services