Fill in the fields, copy the tags into your page's <head>. og:* for Facebook, LinkedIn, WhatsApp, Slack and Discord; twitter:* for X. Nothing leaves your browser.
| Tag | What it is for |
|---|---|
og:title | The headline of the card. Keep it under about 70 characters; it may differ from the page <title>. |
og:description | One or two sentences under the title. Around 150–200 characters show; the rest is cut. |
og:image | The picture. An absolute https:// URL — crawlers do not resolve relative paths. 1200×630 works everywhere. |
og:image:width | With og:image:height, lets Facebook lay the card out on the first share, before it has downloaded the image. |
og:url | The canonical address of the page: shares of its variants count as one. |
og:type | website for most pages, article for posts. Changes little in the card itself. |
og:site_name | Your site's name, shown above the title on Slack, Discord and Telegram. |
twitter:card | summary_large_image for the big image card on X; summary for the small square one. X falls back to og:* for title, description and image. |
twitter:site | The X account of the site, optional. |
The tag is the easy part; the image is the work. Shareglint renders a branded card for every page from its title — 153 ready templates or your own HTML, 100 images a month free.
You need og:title, og:description, og:image and twitter:card. X reads the og:* values when its own twitter:title, twitter:description or twitter:image are missing, so the twitter:* copies are optional — they let you show X a different text.
In the <head> of each page, in the HTML your server sends. Social media crawlers do not run JavaScript, so tags inserted on the client are never seen.
1200×630 pixels (1.91:1), JPEG or PNG, under 600 KB so WhatsApp shows it too. Per-platform minimums and limits, with sources, are on the OG image size page.
No. The tags are built by JavaScript in this page; the form is never submitted.