Skip to main content

Meta Tag Generator

What it does

The Meta Tag Generator builds a complete page <head> block from a small set of inputs — title, description, canonical URL, robots directives, viewport, charset, theme-color, author, language. The output is a copy-ready chunk of HTML you paste into your template. Title and description fields show live character counters with truncation warnings at 60 and 160 characters, the standard SERP cutoffs.

Common situations

You are publishing a one-off landing page that does not get its meta from a CMS. The generator gets you to a complete and correct head block in less time than it takes to look up the right meta names in another tab.

You are auditing an existing page that has a partial set of tags — meta description but no canonical, viewport but no theme-color, robots tag with a typo. Type the values you want, copy the output, replace the existing block. Faster than editing line by line.

You are setting up a CMS or template that will produce these tags programmatically and you want a known-good reference to compare your output against. Generate a complete block, view the output, and use it as the spec your template should match.

A page is appearing in search with a Google-rewritten title because your title was too short, off-topic, or missing. Test new titles in the generator until the character count and content fit, then deploy. Google rewrites titles when it decides the page-supplied title doesn’t represent the content well; a tighter, on-topic title gives it less reason to.

You have a development team writing tags by hand and you keep finding inconsistencies — name="robots" on some pages, http-equiv="x-robots" on others, missing canonicals, mismatched viewport directives. Use the generator’s output as the team’s reference template; deviation from it should be a code-review flag.

What you need to know

Meta tags do not influence rankings the way they did fifteen years ago, but they still control how a page appears in search and social. Title and description determine the SERP snippet; canonical resolves duplicate content; robots controls indexing; viewport controls mobile rendering; theme-color sets the browser chrome on mobile. Each one is small; together they shape every impression of your page.

Title length: Google truncates titles at roughly 600 pixels on desktop, which works out to ~60 characters of typical text. The generator’s 60-character warning is the practical limit. If your title is over, Google will truncate at the nearest word boundary or rewrite the title entirely. Mobile is tighter — around 380 pixels, or ~35 characters before truncation. Optimise for mobile first if your traffic is mobile-dominant. The SERP Preview tool shows pixel-accurate truncation.

Description length: Google’s description cutoff varies but rarely shows more than 160 characters on desktop, less on mobile. Anything over 160 characters either truncates or gets rewritten by Google from page content. Anything under 70 characters tends to get expanded by Google into a richer snippet. The 150–160 character window is the sweet spot for getting your description shown verbatim.

Canonical URL: must be absolute (with the scheme), must point to the page you actually want indexed. Self-referential canonicals (a page declaring itself canonical) are the default for most pages and are correct. The mistake is forgetting to update canonical when URLs change — the page now redirects but its canonical still points at the old URL, sending mixed signals to Google.

Robots: the value is a comma-separated list of directives. Common combinations: index, follow (default — explicitly opt in), noindex, follow (don’t index but follow links — common for utility pages), noindex, nofollow (full exclusion), index, nofollow (rare). The X-Robots-Tag HTTP header carries the same directives at the response-header level — useful for non-HTML resources (PDFs, images) that cannot have meta tags.

Viewport: width=device-width, initial-scale=1 is the universal correct value for responsive sites. Disabling user scaling (user-scalable=no) is an accessibility violation and a Lighthouse demerit; never include it. The generator’s default is correct for almost every site.

Theme-color: a hex colour applied to the browser chrome on mobile (the address bar tint on Chrome Android, Safari iOS, and PWAs). Optional but cheap — supplying it makes the site feel slightly more polished on mobile.

Frequently asked questions

Do meta tags affect rankings?

Title is a moderate ranking signal — the keywords in the title still influence which queries the page can rank for. Description does not directly affect rankings but affects click-through rate, which indirectly matters. The other tags (canonical, robots, viewport) are not ranking signals — they are control mechanisms.

What happens if the title is too long?

Google truncates at the nearest word boundary, replacing the cut content with an ellipsis. If Google decides the truncated title is misleading or off-topic, it will rewrite the title using on-page content. Either way, control of the SERP impression slips out of your hands.

Should every page have a unique title and description?

Yes. Duplicate titles and descriptions across multiple pages dilute SERP differentiation and can trigger duplicate-content concerns. Most CMSes generate per-page titles automatically; the description is more often left blank or templated, which is the common gap.

Can I use the meta keywords tag?

No. Google has not used meta keywords since 2009 and treats it as noise. Other major engines do the same. Including it adds page weight without benefit.

What’s the difference between robots and X-Robots-Tag?

Same directives, different transport. <meta name="robots"> lives in HTML, X-Robots-Tag lives in HTTP response headers. Use meta robots for HTML pages; use X-Robots-Tag for non-HTML resources or when you cannot edit the page template.

Should I include <meta charset> if my site is UTF-8?

Yes — explicitly. Modern browsers default to UTF-8 in most cases, but <meta charset="UTF-8"> removes ambiguity and should appear in the first 1024 bytes of the response (which is why it is conventionally the first thing in the head).

Do I need separate Open Graph and Twitter tags or do meta tags cover them?

Separate. The standard <meta> tags here cover SEO basics; Open Graph and Twitter Cards are separate vocabularies for social card rendering. The Open Graph & Twitter Card Generator handles those.

What’s theme-color and is it worth setting?

A hex colour applied to the browser chrome on mobile (Chrome Android’s address bar, Safari iOS’s UI, PWAs). It does not affect SEO at all — it’s a presentational nicety. Set it to your brand primary if you want; skip it if you don’t care.

Common problems

Problem: Title is set in the template but Google shows a different title in results.

Google rewrites titles when it judges the supplied title to be off-topic, too short, too long, repetitive, or stuffed with keywords. The fix is to write a title that genuinely describes the page content in 50–60 characters. Once Google decides your title is reliable, it stops rewriting.

Problem: Description is being shown as a random sentence from page content.

Google ignores or replaces descriptions for the same reasons as titles — when the supplied description doesn’t match the visible content well. The fix is to write descriptions that summarise what the page actually says, not what you wish it said.

Problem: Canonical points to the right URL but Google still indexes a duplicate.

Canonical is a hint, not a directive. If Google has strong signals that the duplicate is the more authoritative version (more inbound links, more user engagement, older URL), it can choose the duplicate as canonical against your stated preference. The fix is usually to redirect the duplicate to the canonical, not to rely on the canonical tag alone.

Problem: noindex is set but the page is still in search results.

Google’s index updates lag behind page changes. After adding noindex, the page can stay in the index for days or weeks until Googlebot recrawls and processes the directive. Use Search Console URL Inspection to request recrawl if the change is urgent.

Problem: Mobile rendering is broken on Lighthouse despite a viewport tag being present.

Check that viewport is width=device-width, initial-scale=1 exactly. Common mistakes: width=480 (fixed-pixel), initial-scale=0.5 (causes zoom-out on load), user-scalable=no (accessibility violation). The generator’s default is the safe value.

Tips

  • Write the title for the user, not the keyword. Google rewards titles that match real intent over titles stuffed with terms.
  • The description is for click-through, not ranking. Treat it as ad copy: tell the searcher what they get if they click.
  • Canonicalise homepage variants to a single URL — https://example.com/, https://example.com, https://www.example.com/. Pick one, redirect the others, set canonical to match.
  • Always include the viewport meta tag. Mobile-first indexing is now Google’s default; pages without a working viewport are penalised by default in mobile-first ranking decisions.
  • Check rendered output with the SERP Preview tool before publishing — it catches truncation issues that character counts alone miss.

Related tools in this suite

The natural follow-up is the SERP Preview — paste the title, URL, and description from the generator and see exactly how Google will render them on desktop and mobile, with pixel-accurate truncation. The Open Graph & Twitter Card Generator handles the social-card metadata that complements these basic tags.

What this looks like at scale

Generating tags page by page is fine for a small site. For a content site that publishes regularly, meta tags should be templated — a per-page title from the post title, a per-page description from a meta field, a self-referential canonical from the URL, with sensible defaults for robots and viewport. Most CMSes do this; the gap is usually description, which often falls back to truncated content unless authors fill it in. The WP Beacon Plugin audits every page’s meta on every visit and flags missing or oversized values.

Take it further

If meta tags are inconsistent across a content set you have inherited, the right next step is usually a one-off audit pass with the WP Beacon Plugin to surface every page’s status, then a templated fix that generates correct tags from the underlying data going forward.