Skip to content
motifuse
SEO & Marketing

Open Graph Preview & Generator

Draft Open Graph and Twitter Card tags with live social card previews, a readiness score, and copy-ready snippets for shared links.

  • Free public tool
  • No sign-up for this tool
  • Processing clearly labeled
  • Instant results

Content last reviewed

Social sharing metadata

Open Graph Preview & Generator

Draft, validate, preview, and copy Open Graph and X/Twitter Card tags. Final previews may vary by platform, cache state, image availability, and crawler access.

Readiness score

100

out of 100

Quick templates

46 characters. Aim for clear text around 40-70 characters.

Use the final public URL, not a temporary preview link.

126 characters. Aim for a useful 120-200 character summary.

Large preview images often work best around 1200x630.

Describe the image clearly for accessibility and context.

Article metadata

These tags are included when content type is article or when fields are filled.

Comma-separated. Each tag becomes an article:tag meta property.

Preview card for the Open Graph Preview & Generator tool

motifuse

Open Graph Preview & Generator - Free SEO Tool

Create, preview, validate, and copy Open Graph and Twitter Card meta tags for articles, landing pages, products, and websites.

https://motifuse.com/tools/open-graph-preview-generator

Launch readiness

Page title

Good

Title length is within the recommended range.

Page description

Good

Description length is strong for social previews.

Canonical URL

Good

URL is valid.

Image URL

Good

Image URL is valid.

Image alt text

Good

Alt text is included.

Twitter/X card

Good

Card type is selected.

Site name

Good

Site name is present.

Image dimensions

Good

Dimensions are close to the recommended 1200x630 large-card ratio.

Preview note

This tool helps you draft and preview social sharing metadata. Final previews may vary by platform, cache state, image availability, and crawler access.

Implementation tips

  • Paste the generated tags inside the page head or metadata layer for the final URL.
  • Use an image that crawlers can access without authentication or blocked robots rules.
  • After publishing, test with platform debuggers because social networks cache previews.
  • Metadata can improve preview clarity, but it does not guarantee clicks, rankings, or reach.

Better social previews

Use this generator with the Meta Tag Generator, Slug Generator, UTM Builder, and JSON-LD Schema Generator to prepare cleaner launch metadata from one workflow.

Client-side only

Quick Start

  1. Fill in the page metadata

    Enter the title, description, URL, image, and site details — or start from a quick template.

  2. Check the previews and score

    Review the Universal, X/Twitter, LinkedIn, and Facebook-style cards and fix anything the readiness checklist flags.

  3. Copy the tags

    Copy the full head snippet, or just the Open Graph or Twitter blocks, into your page's metadata.

Examples

A complete article card

With every check satisfied, the readiness score reaches 100 and the previews show a full card.

Input

Title (52 chars) · description (148 chars) · valid page URL · reachable 1200 × 630 image with alt text · site name and card type set

Output

Readiness score 100/100 — all eight checks Good; previews show the image, title, description, and site name on every platform tab

Article tags from a comma list

Comma-separated tags each become their own article:tag property in the Open Graph block.

Input

Article tags: Open Graph, Twitter Cards, SEO

Output

<meta property="article:tag" content="Open Graph">
<meta property="article:tag" content="Twitter Cards">
<meta property="article:tag" content="SEO">

About the Open Graph Preview & Generator

When a link is shared, the receiving platform builds its preview card from the page's Open Graph and Twitter Card tags — and a missing image or thin description quietly costs clicks on every share. This tool lets you draft that metadata with immediate visual feedback: as you fill in the form, styled preview cards approximating X/Twitter, LinkedIn, Facebook, and a universal layout update live, so you see the card people will encounter before the page ships.

The form covers considerably more ground than the basic tags. Alongside title, description, URL, and image, it handles the site name, locale, content type, all four Twitter card types, separate site and creator handles, image dimensions and alt text, a theme color, and the article-specific properties — published and modified times, author, section, and tags. Four quick templates (blog post, product page, SaaS landing, documentation) pre-fill realistic values to adapt, and an eight-point readiness checklist scores the metadata, flagging missing images, overlong titles, invalid URLs, and absent alt text with specific guidance for each.

Output comes in three copyable blocks — the full head snippet, Open Graph tags only, or Twitter tags only — with values properly HTML-escaped. Two honesty notes the tool itself displays: previews are realistic approximations, since each platform renders and caches cards its own way, and after publishing you should still verify with the platforms' own debuggers. Your form data stays in the browser; the only network activity is your own browser fetching the preview image you point it at.

How to Use Open Graph Preview & Generator

  1. Start from scratch or click a Quick template — Blog page, Product page, SaaS landing, or Docs page — to load realistic values you can adapt.

  2. Fill in the core fields: Page title (the helper tracks characters against a 40–70 target), Page description (120–200 target), Canonical/page URL, Image URL, and Image alt text.

  3. Set the identity and card details: site name, locale, content type (website, article, product, profile, or video), the Twitter/X card type, and optional site and creator handles.

  4. For articles, complete the Article metadata section — published and modified times, author, section, and comma-separated tags, each becoming an article:tag property.

  5. Switch between the Universal (desktop and mobile), X/Twitter, LinkedIn, and Facebook preview tabs to review the card, and work through the Launch readiness checklist until the score looks healthy.

  6. Open the Code tab or use the copy buttons to copy the full head snippet, the Open Graph block, or the Twitter block, and paste it into your page's head or framework metadata layer.

Key Features

  • Four live preview styles

    Universal (with desktop and mobile modes), X/Twitter, LinkedIn-style, and Facebook-style cards update as you type.

  • Readiness score and checklist

    Eight checks — title and description length, URL and image validity, alt text, card type, site name, and image dimensions — each with specific guidance, rolled into a 0–100 score.

  • Full tag coverage

    Basic title/description/canonical/theme-color tags, the Open Graph set including image dimensions and alt, article properties, and all four Twitter card types with site and creator handles.

  • Quick templates

    Blog, product, SaaS landing, and documentation presets fill the form with realistic values to adapt.

  • Three copyable snippets

    The full head block, Open Graph only, or Twitter only — values HTML-escaped so quotes cannot break the markup.

  • Handle normalization

    Twitter handles are cleaned up automatically — with or without the @, the output is correct.

When to Use Open Graph Preview & Generator

  • Pre-launch metadata

    Draft and visually verify the sharing card for a page before it goes live.

  • Article markup

    Produce the article:published_time, author, section, and tag properties for blog posts and news pages.

  • Fixing ugly shares

    Diagnose why a link previews badly — the checklist pinpoints the missing image, alt text, or thin description.

  • Cross-platform review

    Compare how one set of metadata reads on X, LinkedIn, and Facebook layouts before committing.

  • Developer handoff

    Marketers can perfect the wording and hand the developer a finished, escaped snippet.

How It Works

The form state drives three things in parallel. First, the snippet builder assembles the tag blocks: basic tags (title, description, canonical, theme color), the Open Graph set, and the Twitter set, HTML-escaping every value and omitting tags whose fields are empty. Article properties are included when the content type is article or when any article field is filled. Twitter handles are normalized so a missing or doubled @ cannot produce a malformed tag.

Second, the preview components render your values into card layouts modeled on each platform's conventions — image on top at the 1.91:1 ratio, then site name, clamped title, and clamped description. The image is loaded by your browser directly from the URL you provide, which doubles as a reachability test: if the preview cannot show it, crawlers may struggle too.

Third, the validator runs its eight checks and averages them into the readiness score. Length checks use practical editorial ranges (40–70 title, 120–200 description); URL checks require a parseable http or https address; the dimensions check looks for roughly the 1.91:1 ratio at 1000 pixels or wider.

Supported Formats and Options

Formats

  • HTML meta tag snippets

    Three copyable blocks — combined head snippet, Open Graph only, and Twitter/X only — with values HTML-escaped.

Options

  • Core fields

    Title, description, canonical URL, image URL, image alt text, site name, and locale.

  • Content type and card type

    og:type (website, article, product, profile, video) and twitter:card (summary, summary_large_image, app, player).

  • Handles and image details

    Site and creator Twitter handles, image width and height, and a theme color.

  • Article metadata

    Published time, modified time, author, section, and comma-separated tags.

  • Templates and preview modes

    Four quick-fill templates, a reset, five preview tabs, and desktop/mobile modes on the universal card.

Common Errors and Troubleshooting

Common errors

  • "Image preview unavailable" in the cards

    The image URL is missing, not a valid http(s) address, or the file failed to load. Platforms will hit the same wall — use a public, direct image URL that loads in a regular browser tab.

  • Title or description flagged Too Long

    The checklist warns beyond 70 title characters and 200 description characters because platforms clamp text to a line or two. The previews show roughly where the cut happens — front-load the message.

  • Real platform shows an old card after you update

    Platforms cache scraped metadata per URL. Re-scrape with the platform's own sharing debugger to refresh, or the old card can persist for days.

  • Needs Review on image dimensions

    Large cards work best around 1200 × 630 (a 1.91:1 ratio). Different proportions still work but may be cropped unpredictably — the check nudges you toward the safe shape.

Troubleshooting guide

When the live share does not match the preview

  • Verify the served HTML: view source on the published page and confirm the tags are present exactly once. CMS themes and plugins often inject their own OG tags, and duplicates make platforms pick unpredictably.
  • Use the platform debuggers: each major platform offers a card validator or sharing debugger showing exactly what its crawler fetched — the ground truth when previews disagree.
  • Check image accessibility: the crawler must fetch the image without cookies or logins, and robots rules that block the image path break cards even when the page itself is open.
  • Expect platform variance: each network crops, clamps, and styles differently, and this tool's cards are approximations of those conventions — close, but not pixel-identical to every feed.

Limitations and Important Notes

The previews are realistic approximations, not exact reproductions — platforms change layouts, crop images differently, and cache aggressively, so the published card can differ from any simulation. The readiness checks are editorial heuristics, not platform requirements. The tool cannot verify crawler access to your image (only that your browser can load it) and does not fetch or audit existing pages — paste values in rather than pointing it at a URL. Generated markup covers sharing metadata; structured data and search-specific tags are the JSON-LD Schema Generator's and Meta Tag Generator's territory.

Privacy and Data Processing

Form values, previews, and generated snippets are processed in your browser and never uploaded or stored by the tool. The one network request involved is your own browser loading the preview image from the URL you supply — the same fetch any web page would make to display an image.

Tips and Best Practices

Practical tips

  • Use a 1200 × 630 image at a stable, public URL — it is the safest shape across every platform.

  • Write alt text for the image; it costs one field and improves accessibility everywhere the card renders.

  • Keep the title under about 70 characters and put the distinguishing words first.

  • Use the final canonical URL, never a staging or preview link, so caches attach to the right address.

  • After publishing, re-scrape the URL with each platform's debugger to refresh cached cards.

Best practices

Cards that earn the click they are shown for

Design the image as the headline. On most platforms the picture occupies several times the area of your text, so a legible, on-topic 1200 × 630 graphic — ideally with the page's key message readable at thumbnail size — outperforms any wording refinement. Avoid text near the edges, where crops land.

Write the description as a reason to click, not a summary of the obvious. The title says what the page is; the description's job is the concrete detail that makes it worth opening — what the reader will learn, get, or be able to do.

Then close the loop after launch: share the real URL somewhere private (a DM to yourself works), compare the actual card against the preview here, and re-scrape with the platform debuggers if an old cache shows. Metadata work is only done when the live card looks right.

Technical Details

Snippet generation, validation, and previews all derive from one form state with memoized builders. Tag values pass through an HTML-escape function (ampersands, quotes, angle brackets), empty fields are omitted rather than emitted blank, and handles are normalized to a single leading @. URL validity is checked with the browser's URL parser restricted to http/https. The readiness score averages the eight checks (full credit for good, half for informational). The preview image is rendered with a plain img element pointing at your URL and hides itself on load error. The component is entirely client-side.

Comparison

This tool vs. the Meta Tag Generator

Meta Tag GeneratorOpen Graph Preview & Generator
SpeedSix fields, one outputFull form with previews and scoring
Tag coverageCore title/OG/Twitter setExtended set: locale, dimensions, alt, article properties, all card types
Visual previewsNoFour platform-style cards
ValidationLength hints in labelsEight-point checklist with score
Best forQuick, standard pagesLaunches and articles where the share matters

Both produce paste-ready head markup — pick by how much control and feedback the page deserves.

Who Is This For?

Marketers and founders preparing launch pages where the shared card is part of the campaign; bloggers and editors who want article metadata (dates, authors, tags) done properly; developers who prefer copying escaped, complete markup over remembering property names; and SEO or content teams auditing why a page shares badly. For a quick standard page, the simpler Meta Tag Generator may be all you need.

Frequently Asked Questions

Will the real share look exactly like the preview?

Close, but not guaranteed — the previews approximate each platform's conventions, while the platforms themselves crop, clamp, and cache in their own ways. Treat the preview as a strong draft check and the platform debuggers as final confirmation.

What image size should I use?

Around 1200 × 630 pixels — the 1.91:1 ratio the dimensions check looks for. It renders as a full-width card on X, Facebook, and LinkedIn without surprise crops, and the width comfortably exceeds every platform's minimum.

What is the difference between twitter:site and twitter:creator?

twitter:site is the publication or brand account; twitter:creator is the individual author. On article cards X may display the creator attribution. Enter either with or without the @ — the output is normalized.

When are the article tags included?

When the content type is article, or when any article field (published time, author, section, tags) is filled. Each comma-separated tag becomes its own article:tag property.

Why does my updated page still share with the old card?

Platforms cache scraped metadata per URL, sometimes for days. Use the platform's sharing debugger to force a re-scrape after you deploy new tags.

Does the readiness score affect SEO?

No — it is a completeness measure for your sharing metadata, not a ranking signal. Open Graph and Twitter tags shape how links look when shared; they do not move search positions.

Is anything I enter sent to a server?

No — the form, validation, and snippets are all processed locally. The only request made is your browser loading the preview image from the URL you provide.

Find this useful? Share it.