Free Meta Tag Generator
Generate SEO meta tags, Open Graph and Twitter Card tags for your website.
About Meta Tags
Meta tags provide metadata about your HTML page. They help search engines understand your content, control how your pages appear in search results, and define how link previews look on social media. A well-optimized set of meta tags can improve click-through rates from search and social sharing. Keep titles under 60 characters and descriptions under 160 characters for best display in search results.
The Four Families of <head> Metadata
A modern HTML page's <head> typically carries metadata in four buckets, each serving a different audience:
- Document basics, what every browser needs:
<title>,<meta charset="utf-8">,<meta name="viewport">,<meta name="description">. - SEO directives, what search engine crawlers read:
<meta name="robots">,<link rel="canonical">, the page title that ends up as the SERP link. - Open Graph, what Facebook, LinkedIn, Slack, Discord, iMessage, and most other share-link clients render:
og:title,og:description,og:image,og:url,og:type,og:site_name. - Twitter Card, what X / Twitter renders for shared links, with fallback to OG tags when absent:
twitter:card,twitter:title,twitter:image,twitter:site,twitter:creator.
This generator emits all four families from a single form. The output drops directly into the <head> of any HTML file: paste in, save, deploy. For a deeper dive on Open Graph specifically, the dedicated Open Graph Preview tool shows live platform renderings.
Title and Description: How Long Should They Be?
Google Search Central is direct about the answer: there is no hard maximum. Snippets are simply truncated to fit the device width. The 60-character title and 160-character description rules are industry conventions derived from the observed pixel-width truncation in Google's SERPs (~580 pixels on desktop). The practical take:
- Title, aim for 50–60 characters. Wide capital letters (W, M, capital A) consume more pixel space than narrow letters (i, l, t), so two 60-character titles can render at very different visible widths.
- Description, 150–160 characters on desktop, ~120 on mobile. Front-load the key information so it survives mobile truncation.
- Length doesn't affect ranking; it only affects how much of your snippet a searcher sees before clicking.
The robots Meta Tag: What It Actually Controls
Unlike the obsolete keywords tag (see below), <meta name="robots"> is alive and well; Google explicitly supports it. Common values:
index, follow, the default. Page can appear in search; crawlers follow its links.noindex, exclude this page from search results. Useful for thank-you pages, internal tooling, paginated archives, search-result pages, and anything else you don't want competing with your real content.nofollow, don't follow links on this page. Rarely the right choice page-wide; usually applied per-link viarel="nofollow".noindex, nofollow, both. The strongest privacy stance for a publicly-reachable page.noarchive, don't show a cached copy in search results.nosnippet, don't show a description snippet, only the title.
For Google-specific overrides, use <meta name="googlebot"> with the same values. Note that noindex is also expressible as an HTTP X-Robots-Tag header, which is the right place for it on PDFs, images, and other non-HTML resources where you can't add a meta tag.
Why Canonical URLs Matter
<link rel="canonical"> tells search engines which version of a page is the "official" one when multiple URLs serve the same or near-identical content. Common cases that need a canonical:
- Trailing slash vs not (
/pagevs/page/). - HTTP vs HTTPS (legacy redirects sometimes leave both indexable).
- WWW vs apex (
www.example.comvsexample.com). - Tracking parameters (
?utm_source=...,?ref=...) producing endless "different" URLs. - Pagination, sort orders, filter parameters that produce the same content in different order.
- Syndicated content republished on multiple sites (the canonical points to the original).
Without a canonical, Google picks one version on its own and may pick the wrong one. The canonical URL must be absolute (full https://) and should match exactly the URL you want indexed.
Tags You Can Skip in 2026
<meta name="keywords">, Google has explicitly stated since September 2009 that it does not use the keywords meta tag as a ranking signal. Bing has gone further: it treats excessive keyword stuffing in this tag as a spam signal. Including it doesn't hurt SEO but doesn't help either; the field exists in this generator for users whose corporate templates still expect it.<meta http-equiv="refresh">for redirects, use proper HTTP 301/302 redirects from the server instead. Meta refresh delays the redirect and confuses some accessibility tools.<meta http-equiv="X-UA-Compatible">, needed only for Internet Explorer compatibility, which is no longer a concern.<meta name="revisit-after">, never honoured by major crawlers. Pure cargo cult.<meta name="generator">, informational only; tells the world what built your site. Sometimes a security signal worth removing.
The Two Tags Every Page Genuinely Needs
Beyond <title> and <meta name="description">, two tags are non-negotiable for a modern web page:
<meta charset="UTF-8">, should appear within the first 1024 bytes of the document, ideally as the first child of<head>. The HTML Living Standard requires it for correct character handling. Without it, browsers may guess the encoding and get it wrong, especially on non-Latin scripts.<meta name="viewport" content="width=device-width, initial-scale=1">, tells mobile browsers to render the page at the device's actual width rather than zooming out from a fictitious 980-pixel desktop layout. Without it, every mobile user sees a tiny zoomed-out version of your page that's nearly unusable.
Open Graph and Twitter Cards in Brief
A short summary; for the deep dive use the Open Graph Preview tool. The four required OG tags per ogp.me: og:title, og:type, og:image, og:url. Optional but recommended: og:description, og:site_name. Image dimensions: 1200×630 (1.91:1) is the safest cross-platform size.
For X / Twitter: include twitter:card = summary_large_image (the modern full-width card) and X falls back to OG tags for everything else if Twitter-specific tags are absent. The standalone Twitter Card Validator preview was removed by X on 2 August 2022; verify by pasting the URL into the Tweet Composer instead.
Structured Data Is a Different Job
JSON-LD structured data (using schema.org vocabularies) is what powers rich Google results: recipe cards, product info with star ratings, FAQ snippets in search, breadcrumb trails. It's distinct from meta tags and lives in a <script type="application/ld+json"> block, not a <meta> tag. Both are recommended; one doesn't replace the other. Meta tags control the basic title / description / share-card; structured data unlocks the richer formats.
Common Mistakes
- Including
meta keywordsand expecting SEO benefit. Google announced in 2009 that it doesn't use it. Twenty-plus years later it's still in old templates; remove or ignore. - Forgetting
<link rel="canonical">. If your URL has tracking parameters or alternate versions, Google chooses one on its own. Without a canonical, the chosen version may not be the one with all your inbound links. - Different titles in
<title>,og:title, andtwitter:title. Not technically wrong, but inconsistent. The clean default is one title shared across all three. - Generic site logo as
og:imageon every page. Every page deserves a unique image that ties to its content; using a single logo across the whole site produces boring share previews. - Missing
viewportmeta on mobile-targeted pages. Mobile browsers render the page at fictitious desktop width and zoom out. The user experience is awful. - Using
<meta http-equiv="refresh">for redirects. HTTP 301/302 from the server is the right way; meta refresh is slower and accessibility-hostile, and many crawlers handle it inconsistently for ranking purposes. - Title longer than ~580 pixels (~60 characters wide). Truncated by Google with an ellipsis; the truncated portion isn't visible to searchers.
- Forgetting that single-page apps need server-rendered or pre-rendered meta tags. Many social-media crawlers (Facebook, LinkedIn, Slack, Discord) don't execute JavaScript. Tags written by client-side JS won't be visible to them.
Frequently Asked Questions
Does the keywords meta tag still help SEO?
No. Google's Matt Cutts announced in September 2009 that <meta name="keywords"> is not used as a ranking signal. Bing treats excessive keyword stuffing in this tag as a spam signal. The field is included in this generator for compatibility with older templates and CMS workflows that still expect it; safe to leave blank.
What's the difference between meta description and OG description?
The HTML <meta name="description"> is what search engines use as the snippet under your page title in results. The Open Graph og:description is what social-media share cards display. They can be the same text (and usually are) but you can write different versions if your search audience and your social audience expect different framing.
My JavaScript writes the meta tags after page load. Is that OK?
For Google's main crawler (Googlebot), yes; Googlebot renders JavaScript and sees the post-render meta tags. For social-media crawlers (Facebook, LinkedIn, Slack, Discord, WhatsApp), generally no; most of them don't execute JavaScript and only see the initial HTML. If your site is a single-page app, you need server-side rendering, pre-rendering, or a service like Prerender.io to ensure social-media crawlers see the right meta tags.
Where exactly do these tags go?
Inside the <head> of your HTML, ideally near the top. <meta charset> should be in the first 1024 bytes. <meta name="viewport"> immediately after. Then <title>, <meta name="description">, robots, canonical, OG tags, Twitter tags. Order within the <head> doesn't matter for SEO once the charset and viewport are early enough.
Should I worry about the meta refresh tag for security?
It's not a security risk per se, but it's a poor pattern. Server-side HTTP 301/302 redirects are faster, handle referrer headers correctly, and are accessibility-friendlier. Use meta refresh only when you have no server-side control over redirects (a static GitHub Pages-style host without redirect config).
Are my meta tags uploaded to a server?
No. The generator runs entirely in your browser. Your title, description, URL, and image fields stay on your machine; the output snippet is composed locally and copied to your clipboard on demand. This matters because draft tags often contain unpublished page URLs, internal product names, or pre-launch marketing copy you don't want flowing through a third-party server.
Related Tools
Open Graph Preview
Preview how your link appears on Facebook, Twitter and LinkedIn. Generate OG tags.
Robots.txt Generator
Build a robots.txt file with user-agent rules, allow/disallow paths, sitemaps, and crawl delays.
URL Slug Generator
Turn any text into a clean, URL-friendly slug. Handles accents, special characters, and more.