Open Graph Tag Generator
Generate Open Graph and X card tags for a public page with useful image hints, article fields, and crawler-focused review warnings.{{ summaryTitle }}
{{ summaryLine }}
{{ headMarkup }}
The chart renderer is unavailable. The same counts remain available in the tag ledger.
| Family | Tag | Content | Crawler role | Copy |
|---|---|---|---|---|
| {{ row.family }} | {{ row.tag }} | {{ row.content }} | {{ row.note }} |
| Level | Check | Evidence | Next action | Copy |
|---|---|---|---|---|
| {{ row.level }} | {{ row.area }} | {{ row.evidence }} | {{ row.action }} |
A page can look complete in a browser and still produce a blank or misleading link preview. Social crawlers usually read metadata from the document head, then cache a title, destination, image, and summary for display in feeds and messages. Those values need to describe the public page that people will reach after opening the card.
Open Graph supplies the shared object's identity and presentation clues. The core properties name the object, classify it, point to its canonical URL, and provide a preview image. Descriptions, site names, image dimensions, image type, alternative text, and locale add context. X card tags can state a card layout and repeat key values explicitly for X.
| Decision | Why it matters | Common mistake |
|---|---|---|
| Canonical share URL | Gives the shared object one stable public identity. | Using a tracking URL, fragment, preview host, or private page. |
| Preview image | Provides the visual fetched by crawlers. | Requiring login, blocking crawler access, or relying on a crop-sensitive layout. |
| Object type | Separates ordinary pages from articles and other object categories. | Selecting article without valid publication details. |
| Title and description | Explain the destination before a person opens it. | Repeating the same phrase or allowing the important words to be truncated. |
Metadata cannot force identical rendering. Each consumer chooses its own truncation, crop, fallback, and cache lifetime. Image dimensions are hints, not proof that the file is reachable or has those dimensions. The final check must use the deployed page and public image, preferably with the target platform's crawler or preview debugger.
How to Use This Tool:
Write the preview for one public URL, not for an entire site or campaign.
- Enter a specific Share title, concise Share description, canonical HTTPS URL, and public HTTPS image URL.
- Choose the Open Graph type. Select Article only when author, publication time, modification time, section, or topic tags describe an article.
- Add image alternative text and, when known, both image dimensions and the MIME type. Leave both dimensions at zero when they are unknown rather than inventing values.
- Enable X card tags when the page should state X-specific values and choose a large-image or summary card.
- Review the generated head markup and crawler warnings, then place the tags in the deployed page's
<head>and test the live response.
Interpreting Results:
The generated markup is ready to publish when required inputs pass validation, but review messages still matter. A long title or description may be truncated, a lone width or height gives incomplete image information, and an HTTP URL may be blocked or rewritten by a consumer. Missing optional tags are not syntax errors; they reduce the information available to crawlers.
Use the generated character and byte counts as editorial clues only. The length warnings are local review heuristics, not universal Open Graph limits. Confirm that the final page returns one coherent property set and that the image response is public, stable, and recognizable as an image.
Technical Details:
Open Graph properties use the property attribute, while X card entries use name. Values are HTML-escaped before assembly. Fragments are removed from accepted HTTP or HTTPS URLs so the shared object keeps a stable identity. Optional values are emitted only when they are present and valid for the chosen type.
Rule Core:
| Condition | Emitted tags | Boundary or review rule |
|---|---|---|
| Every valid page | og:title, og:type, og:url, og:image | Title is required and limited to 200 characters; both URLs must be absolute HTTP or HTTPS URLs. |
| Description supplied | og:description and optional twitter:description | Maximum accepted length is 500 characters; review warnings appear below 70 or above 200 characters. |
| Image details supplied | Width, height, MIME type, and alternative-text properties | Dimensions are integers from 0 to 10,000 pixels. Values below 300 by 157 or an aspect ratio outside 1.7:1 to 2.1:1 receive review warnings. |
Type is article | Valid author URL, timestamps, section, and up to 12 topic tags | Author must be an absolute web URL; timestamps must match the accepted ISO-like date or date-time shape. |
| X tags enabled | twitter:card, title, image, optional description, site, and image alt | The site handle is normalized to at most 15 letters, digits, or underscores. Image alt above 420 characters receives a warning. |
The review considers titles shorter than 20 characters underspecified and titles longer than 95 characters at risk of truncation. Descriptions that repeat the full title also receive a review cue. These checks help edit a preview, but no single length or image ratio is guaranteed across platforms.
Limitations and Privacy Notes:
All assembly and review happen in the browser. The page and image URLs are treated as text and are not fetched, so reachability, redirects, response type, actual dimensions, cache state, duplicate tags, and platform rendering remain untested. Shared links can expose entered values through the URL; avoid private preview hosts, unpublished paths, or sensitive article details.
References:
- The Open Graph protocol, Open Graph protocol.
- Summary Card with Large Image, X Developer Platform.
- How to check Open Graph tags, Simplified Guide.