Meta Tag Generator
Title, description, canonical, Open Graph and Twitter cards - with the length checks that decide whether they show in full.
Output — meta-tags.html
About this tool
Fill in one form and get the whole <head> block: title, meta description, canonical link, robots directive, Open Graph tags for Facebook and LinkedIn, and Twitter card tags. The panel under the output tells you when a title will be truncated in search results or an og:image will not load. Everything runs in your browser.
Why the same text appears three times
The output repeats your title in <title>, og:title and twitter:title, and the description in all three places too. That looks wasteful and is deliberate: each consumer reads a different tag first. Google reads <title>, Facebook and LinkedIn read og:title, and X falls back through twitter:title to og:title. Setting all three means a rewritten page title never silently changes what a shared card says.
The one tag you can drop is twitter:image when og:image is already set - X falls back to it happily. It is included here because being explicit costs one line and removes a fallback you have to remember.
What the length checks mean
Google truncates titles on pixel width, not character count, so no tool can tell you the exact cut-off. Around 60 characters is where wide-character titles start getting cut, and around 155 for descriptions. Treat both as a warning light rather than a limit: a clear 65-character title beats a padded 58-character one.
A description does not influence ranking. It influences whether somebody clicks, and Google will overrule it with its own passage from the page whenever it thinks that answers the query better - which happens for well over half of results.
Frequently asked questions
Do meta keywords still do anything?
No. Google stopped using the keywords meta tag in 2009 and has said so publicly. It is not generated here because the only thing it reliably does is show competitors which terms you are targeting.
Where exactly do these tags go?
Inside <head>, and nowhere else. A meta tag placed in the <body> is ignored, and so is one that a script injects after the page has loaded - crawlers do read rendered HTML, but the social scrapers behind link previews generally do not run JavaScript at all.
Why is my og:image not showing when I share the link?
Three usual reasons: the URL is relative rather than absolute, the image is behind a login or a hotlink block, or the platform has cached the old preview. Facebook and LinkedIn both have a debug tool that force-refreshes what they have stored for a URL.
Should every page have a canonical tag pointing at itself?
It is a reasonable default and it costs nothing. It stops parameter and tracking variants of the URL from being treated as separate pages. Just make sure it is absolute and points at a URL that returns 200 - a canonical aimed at a redirect or a 404 is worse than none.