What the Tags Do
Open Graph tags are meta elements in a page's head that describe the page to whatever reads it. When a link is shared in a messaging app, a social feed or a chat tool, the platform fetches the page, reads these tags, and assembles a card from the headline, the description, the image and the site name. The tags are the page's own description of how it should look when shared.
Twitter, now X, has a parallel set of twitter: tags. They decide the card layout, which is either a compact summary or a large image card, and they can override the Open Graph values for that platform. Most platforms fall back to the Open Graph values when the Twitter tags are missing, so the Open Graph set does most of the work.
The generator lets you fill in one set of values, see two generic cards built from them, check each value against simple rules, and copy the resulting tags. It does not publish anything or contact the platforms.
Field Walkthrough
The form is in three groups. Each field below is named by its label, with the tag it produces in code formatting.
Page content: og:title, og:description, og:url, og:image, og:image:alt
og:title is the headline of the card. A small counter beside the label shows its length and a suggested band of 40 to 60 characters. Counts above 70 are marked as likely cut off. og:description is the summary line, with a band of 70 to 200 characters and a warning above 300. og:url is the canonical address of the page and must be a full address starting with https://. og:image is the picture, which must be an absolute https address. og:image:alt is a short text description of the picture for screen readers, and the checklist asks for it whenever an image is set.
Site and type: og:type, og:locale, og:site_name
og:type is a dropdown with website, article, book, profile and product. og:locale takes a language and territory joined by an underscore, such as en_IN; a hyphen such as en-IN turns the field red. og:site_name is the name of your brand, shown above the headline on many cards.
Twitter / X card: twitter:card, twitter:site, twitter:creator
twitter:card chooses between summary_large_image and summary. The matching preview card carries a badge. twitter:site and twitter:creator take account handles that begin with @, using letters, digits or underscores, up to 15 characters. The creator field is optional.
Inherited Twitter title, description and image
Each Twitter text field has a Same as checkbox. While it is ticked, the field is locked and mirrors the Open Graph value. Untick it to edit the Twitter value; the box keeps the text it last copied, so you can adjust it from there. The image field works the same way, against og:image.
Write explicit twitter tags
This checkbox controls whether the output includes twitter:title, twitter:description and twitter:image when they match the Open Graph values. Without it, those lines are replaced by a comment explaining that the card falls back to the Open Graph tags.
Preview cards and image information
The large and compact cards show the same title, description and domain. The domain comes from the og:url field, without the www prefix. When an image is valid, the browser loads it once to read its natural width and height, and the line under the cards reports those numbers with a verdict. The placeholders explain what is missing.
Readiness checks
The checklist gives a pass, warning or failure for the title, description, image, URL, alt text, handles and locale. Failures are missing or invalid values; warnings are values that will probably be cut or cropped.
Load sample, Clear, Copy and Download
Load sample fills every field with a demonstration page, which is useful for seeing the cards at work. Clear empties the fields, restores the default locale and card type, and forgets the saved entries. Copy tags places the output on the clipboard, and Download .html saves it as social-meta-tags.html.
Worked Example
Load the sample and read the results. The title, Monsoon Collection: Handloom Sarees from 1,499, is 46 characters long, inside the 40 to 60 band, so its counter reads "good". The description is 117 characters, inside the 70 to 200 band, and reads "good" too. The Twitter card type is summary_large_image, and the handle is @weaverstreet. Because every Twitter text field is inherited, the output is:
<!-- Open Graph - read by most social networks and messaging apps -->
<meta property="og:type" content="website">
<meta property="og:title" content="Monsoon Collection: Handloom Sarees from 1,499">
<meta property="og:description" content="Hand-woven cotton and silk sarees shipped anywhere in India in 3-5 days. Free returns on every order until 31 August.">
<meta property="og:url" content="https://example.com/collections/monsoon-handloom">
<meta property="og:site_name" content="Weaver Street">
<meta property="og:locale" content="en_IN">
<!-- Twitter / X card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:site" content="@weaverstreet">
<!-- twitter:title, twitter:description and twitter:image are omitted on purpose:
the card falls back to the og: values above. Tick "write explicit twitter tags" to include them. -->
The sample has no image, so the checklist shows three passes and one failure, "No og:image". The og:image:alt line is not written, because it is only emitted alongside an image.
Now paste http://example.com/share.jpg into the og:image field. The field turns red with a message asking for https, the large card shows a prompt to fix the URL, and the checklist reports that og:image is not an absolute https address. The output still carries the address exactly as typed, so the warning is your cue to correct it before you copy the tags.
Finally, change the og:locale value to en-IN. The field explains that the format is language_TERRITORY with an underscore, and the checklist adds a failure for the locale. Changing it back to en_IN clears both messages.
Tips and Common Mistakes
- Write the title for the card, not the page. Lead with the words a reader needs to decide, because long titles are cut off.
- Choose a picture that works small. A landscape image close to 1200 by 630 pixels is the widest target. The tool flags images that are too small or cropped badly.
- Describe the image. Fill in og:image:alt for every image. It helps screen-reader users and is easy to forget.
- Use absolute https addresses. Relative paths only work on your own site, and http is refused by many platforms.
- Keep og:url canonical. Use the clean address of the page so shares of tracked or trailing-slash variants count as one page.
- Check the cache after publishing. Platforms store previews, so use their link debugger to refresh a page you have changed.
- Mind the locale format. en_IN is correct and en-IN is not, although many people type the hyphenated form by habit.
Frequently Asked Questions
The og tags cover most platforms, so they are the essential part. The twitter tags let you choose the card layout and override the title, description or image for X. If you leave the twitter values inherited, the generator omits them, and the platform uses the Open Graph values.
Many platforms refuse to fetch or display images served over plain http, and relative paths such as /images/share.jpg cannot be resolved by a crawler that is not on your site. An absolute https address is the form that works everywhere, so the tool flags anything else.
By default the generator writes no twitter title, description or image when they match the Open Graph values. Ticking the option writes all three explicitly, even when they are identical, which is useful if you want the X card to be fully specified in the page source.
Platforms store previews and refresh them on their own schedule. After you update the tags on your live page, use the platform's link debugger or refresh tool to ask it to fetch the page again. The preview in this tool only shows what the tags say, not what a platform has cached.