Input
Result
The result will appear here.What a link looks like when pasted into Slack, LinkedIn, Facebook, Discord or X is decided by a handful of meta tags most pages get slightly wrong: a relative og:image URL, a missing og:url, a title long enough to be cut off. Enter the page's title, description, URL and image as simple lines and this writes the full set — the title and description tags, the canonical link, the Open Graph properties from ogp.me and the X card tags — correctly escaped. It also measures the title and description against the widths Google tends to show and lists anything the four required Open Graph properties are missing. In a Next.js project, next-seo (garmeeh/next-seo, 8.5k stars, MIT) or the framework's own metadata API generates the same tags from code.
How it works
- Short keys are enough — title, description, url, image, image:alt, site_name, type, locale — and any og:, article: or twitter: property can be added as it is spelled in the specifications.
- og:type defaults to website, the canonical link defaults to the url line, and locales typed as en-US or zh-cn are rewritten as en_US and zh_CN, the form Open Graph expects.
- Only twitter:card is added for X by default, because X falls back to og:title, og:description and og:image; the card becomes summary_large_image when there is an image.
- Title and description widths count a CJK character as two, since Google truncates by pixel width and Chinese characters are about twice as wide as Latin letters.
Where your data goes
Nowhere. This tool runs entirely in your browser: the text you paste is processed by the page and is never transmitted to a server or written to a log.
This tool is free and needs no account. Its results exist only in your open page and are not saved anywhere.
What it costs
This tool is free, with no sign-in and no points.
Common questions
- How long should the title and description be?
- Google cuts titles at roughly 600 pixels, about 60 Latin characters or 30 Chinese ones, and descriptions at around 155–160 characters. These are rules of thumb, not limits: a longer value is still indexed, it just ends in an ellipsis. Social platforms have their own, usually more generous, cut-offs.
- What size should the og:image be?
- 1200×630 pixels, a 1.91:1 ratio, is the size Facebook and LinkedIn recommend and it also works for X's large card. Use an absolute https URL, keep the file under a few megabytes, and set og:image:width and og:image:height so the first share renders without waiting for the image to download.
- I changed the tags but the old preview still shows. Why?
- Every platform caches the preview it scraped. Facebook's Sharing Debugger and LinkedIn's Post Inspector both let you force a fresh scrape; for other platforms, adding a query string such as ?v=2 to the shared URL makes it look new.
- Do I still need twitter: tags?
- Only twitter:card is essential, since X reads the og: values for title, description and image when twitter: equivalents are absent. Add twitter:site (the site's @handle) and twitter:creator (the author's) if you want the card attributed; a handle typed without the @ gets one added.
The open-source behind it
This tool is a self-contained implementation. garmeeh/next-seo (MIT) does the same job as a library — if you need this behaviour inside your own program, start there rather than calling a web page.
garmeeh/next-seoAlso known as
- open graph generator
- og meta tags
- twitter card generator
- meta tag generator
- social share preview tags
- og image tags