Open Graph Tag Generator

Share title:

Use the exact page or content title that should appear in link previews.

Share description:

Write one or two natural sentences; the checklist flags very short, long, or duplicated copy.

Canonical share URL:

Enter the final public URL, including https:// and the canonical path.

Preview image URL:

Use a public HTTPS image URL; 1200 by 630 pixels is a broad social-preview default.

Preview image alt text:

Describe the preview image itself; keep X card alt text within 420 characters.

Site name:

Use the public brand or site label that should appear beside the preview.

Open Graph type:

Choose the closest object type; article unlocks optional article-specific metadata below.

X card type:

Keep summary_large_image for visual pages; choose summary for compact cards.

{{ item }}

Image dimensions:

Width and height hints help crawlers resolve the image without guessing.

× px

Image MIME type:

Use the real served MIME type, or omit the structured image type tag.

Open Graph locale:

Use underscore format like en_US, or leave blank to omit the tag.

X site handle:

Leave blank unless the domain has a real public X account.

Emit X card fallback tags

Keep enabled when the snippet should control X/Twitter previews explicitly.

Article author URL:

Use an absolute author/profile URL, or leave blank to omit article:author.

Article published time:

Use an ISO timestamp such as 2026-05-06T09:00:00+08:00.

Article modified time:

Leave blank when the page has no separate updated timestamp.

Article section:

Use a concise section name such as Product, Engineering, or Guides.

Article tags:

Each non-empty value becomes a separate article:tag meta tag.

{{ headMarkup }}

Family	Tag	Content	Crawler role	Copy
{{ row.family }}	{{ row.tag }}	{{ row.content }}	{{ row.note }}

Level	Check	Evidence	Action	Copy
{{ row.level }}	{{ row.area }}	{{ row.evidence }}	{{ row.action }}

Embed:

Customize

Include current inputs

Size

Advanced

Width

Height

Aspect ratio

Max height

Collapsible embed

Allow fullscreen

Referrer policy

Sandbox tokens

Shared URLs carry a public promise about the page before anyone opens it. Social networks, team chat apps, bookmarking tools, and search-side previews usually fetch the page head and assemble a card from metadata rather than from the visible layout. Missing or conflicting tags leave the crawler guessing, which is how stale titles, cropped thumbnails, generic descriptions, and blank cards reach real users.

Open Graph gives a page a small vocabulary for that promise: title, object type, canonical share URL, preview image, description, site name, locale, and structured image details. X cards use their own twitter: names for card type and attribution, with some fallback behavior from Open Graph values. Publishing both families reduces ambiguity, but it does not make every platform crop, truncate, or cache the preview the same way.

Common Open Graph metadata decisions and mistakes
Metadata Choice	What It Settles	Common Mistake
Title and description	The short text a person sees before deciding whether the link is relevant.	Repeating the page title in the description or writing a sentence that is too long for preview cards.
Canonical share URL	The public identity crawlers associate with the shared object.	Using a draft URL, redirect-heavy URL, fragment URL, or page that requires a login.
Preview image	The visual anchor for the card, especially on large-image layouts.	Pointing to a relative image, a tiny asset, or a file that blocks crawler requests.
Object type	The kind of content the page represents, such as a website page, article, profile, book, product, or video.	Marking ordinary pages as articles, then publishing article fields that do not match the content.

Preview metadata is also a publishing habit. A marketing page may need a centered 1200 by 630 image that survives mobile crops. A documentation page may need a precise title and a description that explains the task rather than the brand. An article needs dates and author information only when those facts are real publishing records. The metadata should describe the exact URL being shared, not the site in general.

Open Graph metadata flow from page facts to crawler preview checks

The most reliable previews come from matching three things: metadata that describes the page accurately, public assets that crawlers can fetch without authentication, and final testing after deployment. A valid tag set cannot force every platform to render the same card, but it removes avoidable causes of wrong titles, missing images, and stale-looking shares.

How to Use This Tool:

Start with the facts that should appear in a public share card, then use the review output to catch invalid URLs, weak text, and image choices before copying the head markup.

Enter Share title, Share description, Canonical share URL, Preview image URL, Preview image alt text, and Site name. The summary changes from blocking issues to a generated tag count when required Open Graph fields are usable.
Set Open Graph type to the closest public object type. Keep website for ordinary pages, and choose article only when the page has real author, date, section, or topic metadata.
Choose X card type. Use summary_large_image when the preview image is meant to carry the card, or summary when a compact thumbnail card is more suitable.
Open Advanced for image dimensions, image MIME type, Open Graph locale, X site handle, the Emit X card fallback tags switch, and article-only fields. Leave optional fields blank when the value is not a true public fact.
Fix any Required tag fixes or Crawler warnings. Invalid absolute URLs block copying; short or long text, missing alt text, small images, unusual image ratios, and article timestamp issues stay visible for review.
Compare Head Tags with Tag Ledger and Crawler Checklist. Copy the head markup only after the generated tags and checklist tell the same story.

After the tags are published, test the final public URL with the platform crawler or preview debugger you care about most, because platform caches and fetch rules are outside the generated markup.

Interpreting Results:

Head Tags is the markup artifact. Tag Ledger explains every emitted tag by family, tag name, content, and crawler role. Crawler Checklist is the quality gate: errors stop copying, warnings point to likely preview failures, and review items flag choices that need human judgment.

A clean checklist means the metadata is internally consistent enough to publish. It does not prove that X, Facebook, Slack, LinkedIn, Discord, or another consumer will show the same crop, same text length, or same cached version. Verify the final URL and the preview image from a public network, then refresh platform caches when a previously shared URL still shows old metadata.

Treat any Error row as a stop sign, especially invalid og:url or og:image values.
Treat Warning rows as preview risk, not syntax failure.
Use Review rows to decide whether the metadata describes the specific URL well enough for a stranger seeing the card out of context.

Technical Details:

Open Graph represents a page as a shareable object. The basic object facts are title, type, image, and canonical URL; optional facts add description, site name, locale, and structured image properties. Structured image properties belong directly after the root image value, so crawlers can attach width, height, MIME type, and alternative text to the intended image instead of a later image on the page.

X card markup follows the same general idea with name attributes and twitter: tag names. Some consumers can fall back from Open Graph fields when dedicated X fields are absent, but explicit X card tags make the intended card type, title, description, image, and image alt text auditable before launch.

Rule Core:

Generated Open Graph and X card tag rules
Area	Tag Family	Emission Rule
Core object	`og:title`, `og:type`, `og:url`, `og:description`	The selected type is emitted as `og:type`. Title and description are emitted when supplied, and the canonical URL is emitted only after it parses as an absolute HTTP or HTTPS URL.
Preview image	`og:image`, `og:image:width`, `og:image:height`, `og:image:type`, `og:image:alt`	The image URL must parse as an absolute HTTP or HTTPS URL. Width, height, MIME type, and alt text are added only when values are present and valid for their field.
Site and locale	`og:site_name`, `og:locale`	Site name is optional. Locale is emitted only when it matches the usual language or language-territory shape, such as `en` or `en_US`.
Article metadata	`article:author`, `article:published_time`, `article:modified_time`, `article:section`, `article:tag`	Article tags appear only when the Open Graph type is `article`. Author URLs and timestamps are included only when they pass their shape checks; topic tags are split from comma or newline separated text.
X card fallback	`twitter:card`, `twitter:site`, `twitter:title`, `twitter:description`, `twitter:image`, `twitter:image:alt`	X card tags are emitted when fallback tags are enabled. The card type is limited to `summary` or `summary_large_image`, and the site handle is normalized to a valid public handle shape.

Validation focuses on the problems that usually break or weaken link cards. URL parsing protects against relative paths and non-web schemes. Text length checks protect against titles that are too vague or too long to survive truncation. Image checks look for enough dimensions to support large previews and a ratio close to common link-card crops.

Validation Boundaries:

Validation boundaries for generated Open Graph metadata
Check	Boundary	Result Meaning
Title	Blank is an error, fewer than 20 characters asks for review, and more than 95 characters warns.	The title should be specific without hiding the useful words in a cropped card.
Description	Blank warns, fewer than 70 characters asks for review, and more than 200 characters warns.	A concise one or two sentence summary is more reliable than a title repeat or a long paragraph.
Share and image URLs	Only absolute `http` or `https` URLs pass the required URL shape. `http` passes with a warning.	Crawlers need a public URL they can fetch without relying on the document location or a logged-in browser.
Image dimensions	Images below `300x157` warn; ratios below `1.7:1` or above `2.1:1` ask for review.	Small or unusually shaped images are more likely to crop badly or fail large-card expectations.
Image alt text	Missing alt text asks for review when an image exists; more than 420 characters warns.	Open Graph and X card metadata can carry an image description for accessibility and fallback contexts.
Article dates	Published and modified values are checked against an ISO-like date or date-time shape.	Article metadata should describe a real publishing record rather than a loose display date.

The JSON output mirrors the same settings, generated counts, checklist rows, tag ledger, and head markup for handoff or audit notes. It is useful for review, but the final proof is still a crawler fetch against the published public URL and image URL.

Limitations and Privacy Notes:

The checks validate metadata shape and common preview risks. They do not fetch the canonical URL, inspect the image bytes, read robots rules, test platform caches, or prove that a crawler can reach the deployed page.

Do not treat a generated snippet as a platform preview guarantee.
Do not paste private draft URLs, embargoed titles, or non-public image links into exports you plan to share.
Use the platform's own crawler or preview debugger after deployment when the card matters for launch.

Worked Examples:

A product landing page titled Project Dashboard Checklist with a 1200 by 630 PNG image, website type, summary_large_image, site name, locale, and X site handle produces a Head Tags snippet with Open Graph object tags, structured image properties, optional site and locale tags, and X card fallback tags. If Crawler Checklist reports ready rows for URL shape and image dimensions, the next check is the published page in a crawler preview tool.

An article page can switch Open Graph type to article after the author URL and timestamps are ready. A value such as 2026-05-06T09:00:00+08:00 is accepted for article:published_time, while a casual phrase like next Wednesday morning remains a review item until it is converted or removed.

A troubleshooting case starts with a relative image path such as /assets/share.png. Crawler Checklist marks og:image as an error, and the copy action remains blocked. Replacing it with a public absolute URL on www.example.com using the same image path clears the blocking URL shape problem, then image size, ratio, and alt text can be reviewed.

FAQ:

Does a valid snippet guarantee the same card everywhere?

No. The generated tags remove common metadata problems, but each platform can truncate text, crop images, cache old values, or ignore fields it does not use.

Why are absolute URLs required?

Crawlers fetch metadata outside the original browser context, so og:url and og:image need complete HTTP or HTTPS URLs rather than relative paths.

When should I choose summary instead of summary_large_image?

Use summary when the preview should be compact or the image is not important. Use summary_large_image when the image is public, high quality, and central to the shared link.

Why does the checklist warn about a missing image alt value?

When a preview image is present, both Open Graph and X card metadata can carry image alt text. The warning asks you to add a concise description rather than publishing a visual-only cue.

Does the page test whether my URL or image can be fetched?

No. It validates the field shape and review boundaries in the page. Use a live crawler test after publishing to confirm reachability, robots access, TLS behavior, and cache refresh.

Glossary:

Open Graph: A metadata protocol that describes a web page as a shareable object for preview consumers.
X card: A preview metadata family that uses twitter: tag names for card type, title, description, image, and attribution.
Canonical share URL: The public URL used as the stable identity for the shared object.
Preview image: The public image URL crawlers use when building a visual link card.
Structured image property: An image detail such as width, height, MIME type, or alt text attached to the root image tag.
Crawler: A platform fetcher that reads the page head and related assets before rendering a link preview.
Article metadata: Open Graph fields for article author, publication time, modification time, section, and topic tags.

References:

The Open Graph protocol, Open Graph protocol.
Summary Card with Large Image, X Developer Platform.
Getting started with Cards, X Developer Platform.
Troubleshooting Cards, X Developer Platform.