What this tool does
This meta tag generator writes the head tags a page needs — title, description, canonical, robots, Open Graph and Twitter Card — and shows a live preview of how the result is likely to appear in Google. You fill in the fields, copy the block, paste it into your page.
Everything runs in your browser. Nothing you type is sent anywhere, which matters when you are drafting tags for a client site that has not launched yet.
How to use it
- Write the page title. The counter turns amber past the point where truncation becomes likely.
- Write the meta description as a sentence someone would actually read, not a keyword list.
- Add the canonical URL — the address this page should be indexed under.
- Fill in the social fields if you want control over how shared links look.
- Copy the block into the
<head>of your page, or download it as a file.
Writing a title that survives
Google rewrites page titles in a meaningful share of results, and the rewrite is usually a symptom rather than a punishment. The three patterns that invite it are a title that repeats the same keyword, a title identical to dozens of others on the same site, and a title that describes the site rather than the page.
The fix is the same in all three cases: describe this page specifically, put the distinguishing words first, and leave the brand for the end — where truncation costs you nothing, because the reader already knows which site they are looking at.
The description does not rank, but it decides the click
Meta descriptions have not been a ranking factor for years. What they do is compete for the click against nine other results, and Google will happily replace yours with a sentence pulled from the page if it thinks that sentence answers the query better.
Write it as a promise about what the reader gets, include the words they searched so they appear in bold, and keep the essential part early — the tail is what disappears on a narrow screen.
Canonical and robots: the two that break things quietly
A wrong canonical tells search engines to index a different URL than the one you are on, and the page vanishes from results without any error appearing anywhere. Point it at the current page unless you are deliberately consolidating duplicates.
The robots directive is the other silent failure. noindex shipped to production because someone
forgot to flip it after a staging deploy is one of the most common causes of sudden traffic loss,
and nothing in your analytics will tell you it happened.
Social tags decide what people see when they share
A link shared into Slack, WhatsApp or LinkedIn is rendered from Open Graph tags, not from the page
itself. When they are missing, each platform improvises: it takes the title from the <title>, the
text from whatever paragraph it finds first, and the image from the first one in the document —
which is frequently a logo, an icon, or an avatar from a comment.
Declaring og:image explicitly is the whole point. Use an image around 1200×630, keep the
important part away from the edges, and remember that most platforms cache aggressively: after
changing it, you may need to force a refresh in the platform's own debugging tool before the new
image appears.
Twitter Card tags exist separately because X reads its own namespace, though it falls back to Open
Graph when the twitter: tags are absent. This generator emits summary_large_image only when you
provide an image, since declaring the large card without one produces a broken preview rather than
a big one.