Meta Tag Generator at a glance
- What it does
- Generate SEO meta tags, Open Graph and Twitter Card markup for any page, with guidance on lengths that actually work in search and social previews.
- Where it runs
- Entirely in your browser — no data is uploaded
- Works offline
- Yes, once the page has loaded
- Cost
- Free, with no account and no usage limit
- Category
- Webmaster & SEO
How to use the meta tag generator
- Enter your page title and description, keeping to the lengths below.
- Add the canonical URL - the definitive address for this page.
- Add a share image, ideally 1200 × 630 pixels.
- Copy the generated tags into the
<head>of your page.
Writing a title that works
Google truncates by pixel width, not character count, so a title in capitals or wide letters is cut sooner. Around 55-60 characters is the practical target.
- Put the important words first. Both readers and search engines weight the opening more heavily, and a truncated title keeps only the beginning.
- Make each one unique. Duplicate titles across a site are one of the most common issues Search Console reports.
- Describe the page, not the site. "Home" tells nobody anything.
- Add the brand at the end, separated by a pipe or dash, if it is worth the characters.
- Avoid keyword stuffing. Google frequently rewrites titles it considers over-optimised, at which point you have lost control of the wording entirely.
And a description that earns the click
The meta description is not a ranking factor. It is advertising copy shown to someone who has just searched, and its only job is to make your result more appealing than the nine others on the page.
Say what the reader will get, be specific rather than generic, include the search terms they are likely to have used - matched terms are shown in bold - and where appropriate include a reason to act. Write a distinct one per page; a template repeated across a site does nothing.
Google rewrites descriptions perhaps 60-70% of the time, usually pulling a more relevant passage from the page for that particular query. That is not a reason to skip it: when it does use yours, it is the version you chose.
Canonical tags
A canonical tag tells search engines which URL is authoritative when the same content is reachable at several addresses - with and without a trailing slash, with tracking parameters, in a print view, or under multiple category paths.
Three rules keep it out of trouble. Self-reference: every page should carry a canonical pointing at itself. Use absolute URLs. And never point every page at the homepage, a surprisingly common misconfiguration that tells Google the rest of your site does not exist.
Frequently asked questions
No. Google stopped using them in 2009 and no major search engine uses them now. The tag is harmless and pointless.
Because it often generates a snippet from page content that better matches the specific query. That is usually helpful. Writing a strong description means that when Google does use yours, it is the version you intended.
1200 × 630 pixels, a 1.91:1 ratio, under about 1 MB, served over HTTPS at an absolute URL. Keep any text large enough to read at thumbnail size.
Not directly. It affects click-through rate, which affects how much traffic a given ranking delivers - so it matters commercially without being a ranking factor.
It is good practice. A self-referencing canonical prevents duplicate versions created by tracking parameters or trailing-slash variations from being treated as separate pages.
Nothing you enter here leaves your browser
Meta Tag Generator does its work in JavaScript running on your own device. The page loads once, and after that there is no upload step and no server involved — which matters here because site structure and configuration are worth keeping to yourself.
You can verify this rather than taking our word for it: load the page, disconnect from the internet, and the tool keeps working. Our privacy policy sets out what is and is not collected, and this guide explains why the distinction matters.
Open Graph and Twitter Cards
Without Open Graph tags, a shared link shows whatever the platform can scrape - often the wrong image and a fragment of navigation text. With them, you control the preview entirely.
The image is the part that matters most. Use 1200 × 630 pixels, under about 1 MB, with any text large enough to read at thumbnail size. Serve it over HTTPS as an absolute URL - relative paths do not work here.
Test with each platform's own debugger before you rely on it. They cache aggressively, so if you fix a bad preview after sharing, you will need to force a re-scrape through the debugger tool.