Skip to content
Subscribe

Open Graph Generator

Generate Open Graph and Twitter Card tags with live previews of how your link actually renders on Facebook, X, LinkedIn, Discord, Slack, and WhatsApp.

Free · no signup · real data — provided by Keywords Everywhere, embedded live below.

Powered by Keywords Everywhere

What the Open Graph Generator does

Every link shared in a feed or group chat renders from Open Graph tags — and a missing or malformed tag set turns your share into a naked URL nobody clicks. This generator builds correct OG and Twitter Card markup with live previews across six platforms, auto-fills from your URL, verifies your image dimensions, and catches the fourteen most common OG mistakes before platforms punish you for them.

The multi-platform preview matters because platforms disagree: an image cropped beautifully on Facebook can decapitate your headline on LinkedIn, and Discord renders differently again. For publishers, social embeds are unattributed distribution — every WhatsApp share of your post renders through these tags. They’re also part of the social markup the SEO Analyzer scores. Two minutes here fixes what would otherwise silently cost shares for years.

How to use it

  1. Paste your URL to auto-fill existing tags — or start clean.
  2. Set title, description, and image; verify the image passes the dimension check (1200×630 is the safe standard).
  3. Review the live previews per platform and adjust until nothing crops badly.
  4. Copy the generated tags into your page head, then re-share a test link to confirm.

Open Graph Generator FAQ

What image size should I use for Open Graph?

1200×630 pixels (1.91:1) is the cross-platform standard — sharp on Facebook and LinkedIn, acceptable everywhere. Keep critical text away from edges; platforms crop differently, and the generator’s dimension check flags images that will break.

Why does my link show an old image after I fixed the tags?

Platform caches. Facebook, LinkedIn, and the rest cache OG data aggressively — use their sharing debuggers (Facebook’s Sharing Debugger, LinkedIn’s Post Inspector) to force a re-scrape after any change.

Do I need separate Twitter Card tags if I have OG tags?

X falls back to OG tags, but explicit twitter:card markup gives you control over the format — summary_large_image renders the big visual card that dramatically outperforms the small summary card. The generator emits both sets correctly.