Open Graph Generator
Build Open Graph meta tags and preview how the link will look when shared on Facebook and other social platforms.
About the Open Graph Generator
Without Open Graph tags, platforms like Facebook and LinkedIn have to guess at a title, description, and image whenever someone shares a link, and the guess is often wrong or missing outright, an unrelated headline pulled from elsewhere on the page, no image at all, or a thumbnail that has nothing to do with the actual content. Fill in the fields above to generate the correct og: meta tags, along with a live approximation of what the resulting share card will actually look like before it's ever pasted into a real chat or feed.
Why og:image is the one that matters most
A missing title or description in a share card is a minor annoyance, a missing or broken og:image is the one that makes a shared link look outright broken, showing up as a blank gray box or a default site logo instead of anything relevant to the actual page. Most platforms also expect this image at a specific aspect ratio, roughly 1.91:1, something close to 1200x630 pixels works reliably across Facebook, LinkedIn, and most link-preview bots without getting awkwardly cropped.
og:url and canonical usually should match
The og:url field is meant to state the canonical, shareable version of a page, if that differs from the actual canonical URL set elsewhere in the page's head, likes and shares on Facebook can end up split across two different URLs instead of consolidating on one, which quietly undercounts social engagement on whichever version gets less traffic. Setting og:url to exactly match a page's canonical link tag avoids that split.
Different og:type values change how a share card behaves
Most pages use website, but a blog post benefits from article, since it unlocks additional Open Graph fields like publish date and author on platforms that read them, and a product page benefits from product for the same reason. Choosing the type that actually matches the content isn't just semantic correctness, some crawlers and platforms use it to decide which additional metadata fields to look for.
Cached previews don't update automatically
Facebook and LinkedIn cache a link's preview the first time it's shared, so fixing the og:image or title on a page after that first share often doesn't change what people already see when the link circulates. Facebook's Sharing Debugger and LinkedIn's Post Inspector both offer a way to manually force a re-scrape after tags change, worth doing right after updating Open Graph tags on a page that's already been shared at least once.
og:image needs an absolute URL
The image referenced by og:image has to be a full, absolute URL, https://example.com/images/preview.jpg, not a relative path like /images/preview.jpg. A relative path works fine for an <img> tag on the page itself, since the browser resolves it against the page's own URL, but a social platform's crawler fetching the tag out of context has no page URL to resolve a relative path against, so the image silently fails to load in the share preview. This is one of the more common reasons an Open Graph image works perfectly on the live site but shows up blank the moment the link gets shared somewhere else.
Twitter Card tags aren't automatic
X/Twitter does fall back to Open Graph tags when its own twitter: tags aren't present, but relying on that fallback means the card renders differently, or not at all, compared to a page with dedicated Twitter Card tags. The separate Twitter Card Generator on this site builds those tags specifically, and running both generators for a page that's likely to be shared on X gives more reliable control over how it displays there.
Frequently Asked Questions
What image size works best for og:image?
Roughly 1200x630 pixels, an aspect ratio close to 1.91:1, is the size that renders reliably across Facebook, LinkedIn, and most other platforms without awkward cropping. Smaller images may display at reduced size or get skipped by platforms with a minimum size requirement.
Why isn't my updated og:image showing up when I share the link?
Facebook and LinkedIn cache the preview from the first time a link was shared. Updating the tags on the page afterward doesn't automatically refresh what's already cached, use Facebook's Sharing Debugger or LinkedIn's Post Inspector to manually force a re-scrape.
Does og:url need to match my canonical tag?
It should. If they differ, shares and likes on a page can split across two different URLs instead of consolidating in one place, undercounting engagement on whichever version gets less traffic.
Does the og:type value actually matter?
Yes, beyond labeling. Some crawlers use og:type to decide which additional metadata fields to look for, article unlocks fields like publish date and author on platforms that read them, so matching the type to the actual content type is worth doing rather than defaulting to website everywhere.