<meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1.0"> <title>My Awesome Page</title> <meta name="description" content="A short description of this page for SEO and search engine results."> <meta name="keywords" content="vue, nuxt, tools"> <meta name="robots" content="index, follow"> <link rel="canonical" href="https://example.com/page">
About Meta Tag Generator
This tool builds the basic SEO metadata — title, description, keywords, author, robots and a canonical link — locally in your browser from what you enter, with a live Google-style result preview. Tags are assembled client-side and the page information you type is never sent. The snippet is ready to paste into the <head> of a landing page, campaign page or blog post so summaries are not truncated and duplicate addresses are avoided. Open Graph and Twitter Card tags for social sharing are a separate group — use our Open Graph tag generator for those. The title and description shown in search results and browser tabs are declared through basic metadata rather than guessed from the body. Without a description, a search engine pulls an arbitrary passage whose length and readability you do not control; an over-long title gets cut into half a sentence in the results. Writing these tags into the source turns presentation from guesswork into a declaration. The basic group has four kinds of declaration: charset and viewport decide how the browser decodes and scales; title and description drive search and tab display; robots decides whether indexing and following are allowed; canonical names the page's preferred address. Images and social cards belong to Open Graph and Twitter Card, a parallel group outside this tool's output. Practical notes: Write the canonical address as an absolute URL, since relative ones fail to resolve for some consumers, and give each page its own canonical address when the same content is reachable at several URLs, or search engines may treat them as duplicates. Keep the description within the truncation habit of your target market, or it gets cut into a confusing half sentence. If a page varies by language, supply tags per language and consider declaring the applicable locale. Limits: These tags affect presentation, not ranking, so treating them as a direct ranking lever is a misunderstanding; their job is click-through rate. Keywords have long been ignored by mainstream search engines and are kept only for a few regional ones, and a robots noindex is a hint whose effect still depends on the server response and site configuration. Data and privacy: metadata is publicly exposed in the page source, so never write internal addresses, unreleased project codenames or authenticated parameters into it. This tool generates the tag text in the browser, uploads nothing and works offline. Two misuses stand out. Treating metadata tags as a ranking lever: they shape presentation and take no part in search ordering, so investing here while neglecting content quality misses the point. And letting several pages share one canonical URL, where search engines treat them as duplicates and keep only one version, so the others drop out of the index.
How It Works Internally
Metadata tags declare what the page is for search engines and browsers, so they do not take part in ranking and only affect presentation. The basic group covers charset, viewport, title, description, robots and canonical; Open Graph and Twitter Card are separate parallel groups for social sharing and must be generated elsewhere. A canonical URL must be absolute — a malformed one is ignored rather than reported.
Writing the canonical address as a relative pathSearch engines cannot resolve the preferred address and may treat several URLs as duplicates; canonical must be absoluteMeasured on This Page
| Escaping correct | Quotes, &, < and > in the title all escape to " & < > and round-trip exactly — pasting cannot break the HTML structure and it is not an injection point |
|---|---|
| Charset first | <meta charset> is always the first line (the encoding declaration must live in the first 1024 bytes) |
| Canonical & | The & in URLs becomes & — required inside attribute values, and browsers restore it |
| Empty fields omitted | Leaving author blank drops the whole <meta name=author> instead of emitting an empty tag |
| Live preview | Title 60 / description 160 counters turn red when exceeded |
Attribute escaping is the life-or-death line for generators of this kind: one " in the description terminates the content attribute early and the rest becomes DOM nodes — both a layout bug and an injection hole. This page escapes & < > and quotes and round-trips exactly (all 6 checks pass with 4 special-character classes in the title). Two reminders: <title> is text content with different escaping rules (this page applies the attribute convention throughout, which renders the same), and the keywords meta has been ignored by Google for years — it persists only for some Chinese search engines.
How to Use
- Open "Meta Tag Generator"
- Fill in the title, description, canonical URL and keywords
- Choose a robots policy and toggle charset or viewport
- The HTML tags build up in the right pane
- Check the search preview, then copy the whole block
Use Cases
- Fill in basic tags — Generate title, description and canonical for an article so summaries are not truncated and URLs do not duplicate.
- Unify site metadata — Produce description, canonical and robots for new pages to keep site conventions consistent.
- Check the search snippet — Use the built-in Google preview to see how the title and description truncate in results.
- E-commerce landing — Write a description and canonical for a campaign page so links are not merged by search engines.
- Audit head tags — Compare against the generated standard tags to find missing or duplicate meta declarations.
- AMP pages — Generate the required meta tags for Accelerated Mobile Pages to ensure they validate and appear in search.
- Theme templates — Produce a reusable meta tag snippet for a CMS theme so every new page inherits correct meta defaults.
FAQ
What size should og:image be?
Most platforms recommend 1200x630 px (about 1.91:1) and a modest file size. The image needs a publicly accessible absolute URL, or crawlers cannot fetch it and the card shows blank.
Why does the share preview not update?
Platforms cache crawl results. After editing, force a re-scrape with the platform's debugger (such as Facebook's sharing debugger) or wait for the cache to expire.
Do Open Graph and meta description conflict?
No, they serve different purposes: description feeds search snippets, og:description feeds social cards. Fill both, with content that can differ slightly in emphasis.
Are twitter: tags required?
Twitter/X falls back to Open Graph tags when twitter: tags are absent, but setting twitter:card explicitly gives finer control over the card style (large image or summary).
Do these tags affect search ranking?
og tags are not a direct ranking factor, but better previews boost clicks and sharing. Meanwhile title and description shape the search snippet and indirectly affect click-through.
The tags look right but the shared link has no thumbnail. Why?
Confirm the image URL is absolute and publicly reachable: relative addresses cannot be resolved by most platforms, and internal or authenticated image URLs are refused. Then check the format and dimensions, since undersized images are commonly ignored. Note also that platforms cache the fetched result, so after a change you need to refetch or test with a different link, or you keep seeing the old card.
Is it a problem to reuse one set of tags across several pages?
Yes. Most platforms use the address to decide uniqueness, so pages sharing one tag set, especially the same image and canonical address, may be treated as duplicates and merged, giving you a card that shows the wrong page title. Give every page its own title, description and canonical address; the image can be reused but its URL should point at that page asset.
Where do the generated meta tags go in the HTML?
Inside <head>, after <title>. Placing them in the body gets them ignored or warned about, and search engines may not read them. Open Graph tags also live in the head — verify actual crawling with the Facebook Sharing Debugger or WeChat devtools.