WebToolVerseWebToolVerse

Meta Tag Generator

Runs in your browser

Generate SEO-optimised meta tags — primary, Open Graph, Twitter Card, canonical, and robots — with live character counters. Copy ready-to-paste HTML.

Basic Meta Tags

0 / 50–60

50–60 characters is the Google SERP sweet spot

0 / 150–160

150–160 characters. Shown in search results under your title.

Prevents duplicate content issues. Use exact preferred URL.

Open Graph (Facebook · LinkedIn)

0 / 40–60
0 / 100–200

Twitter / X Card

Generated HTML

<!-- Primary Meta Tags -->
<title>Your Page Title</title>
<meta name="title" content="Your Page Title">
<meta name="description" content="Your page description.">
<meta name="robots" content="index, follow">
<meta name="viewport" content="width=device-width, initial-scale=1.0">

<!-- Open Graph / Facebook / LinkedIn -->
<meta property="og:type" content="website">
<meta property="og:url" content="https://yourwebsite.com/">
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Your page description.">

<!-- Twitter / X Card -->
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:url" content="https://yourwebsite.com/">
<meta name="twitter:title" content="Your Page Title">
<meta name="twitter:description" content="Your page description.">

SEO Checklist

–Title 50–60 chars
–Description 150–160 chars
!Canonical URL set
!OG image URL provided
!Twitter handle set
Runs entirely in your browser — nothing is uploaded

Next steps

Open Graph Preview

See exactly how your link will look when shared on social media.

Schema Markup Generator

Generate structured data markup that helps search engines understand your site.

Keyword Density Checker

See which keywords dominate your content and fine-tune SEO.

Find & Replace

Find and replace across text with regex support and live preview.

View all tools →
Runs entirely in your browser. No uploads. Your files stay private.

What Are HTML Meta Tags?

Meta tags are HTML elements that live inside the document head and describe a page to machines: search crawlers, social link unfurlers, browsers, and increasingly LLM retrieval pipelines. They are not visible to users on the page itself, but they decide how the page is summarized everywhere it gets quoted — Google search results, the link card on X, the rich preview that appears when someone drops your URL into Slack.
This generator builds the tag block from a small template-string engine. As you fill in title, description, canonical URL, image, and locale, the right-hand panel renders the matching tags in valid HTML, ready to paste into a Next.js Metadata export, a WordPress header.php, or a static <head>. Nothing is sent over the network — the strings are assembled in your browser.
The set covers six families of tags. The classic SEO pair (title and meta description), the Open Graph block (og:title, og:description, og:image, og:url, og:type, og:site_name, og:locale) used by Facebook, LinkedIn, Slack, Discord, and WhatsApp, the Twitter Card block (twitter:card, twitter:title, twitter:description, twitter:image), the canonical link, the robots directive, and the viewport plus charset declarations every page needs.
Mind the length limits when writing copy. Google truncates titles at roughly 600 pixels of rendered width, which works out to about 50-60 characters in most fonts but can be fewer when capital letters or wide glyphs dominate. Meta descriptions are cut around 155-160 characters on desktop and closer to 120 on mobile. Anything past those thresholds is silently replaced with an ellipsis in the search snippet.
The meta keywords tag is intentionally not generated. Google dropped it from ranking signals back in 2009, Bing followed suit, and including it today only leaks your keyword strategy to competitors who view source. Likewise, the deprecated meta name=author is omitted in favor of structured data, which is a stronger signal for authorship.
Canonical tags deserve special care. Set the canonical to the exact URL you want indexed (with or without trailing slash, with or without www, but consistent across the site). Pages with conflicting canonicals or self-referential canonicals on duplicate URLs are a leading cause of pages dropping out of Google's index. The generator emits an absolute URL by default to avoid relative-path ambiguity.
Once you have pasted the tags, validate them with the Open Graph Preview tool below for social cards, and use Google's Rich Results Test to confirm the page parses cleanly. Schema.org structured data, generated separately, layers on top — meta tags describe the page as a resource; schema describes the entities it talks about.

Common Use Cases

01

New page SEO scaffolding

Generate a full head block for every page before deploy so titles, descriptions, and canonicals are in place from launch.

02

Social card setup

Produce matching Open Graph and Twitter Card tags so links show the right image and headline on every major platform.

03

Migrating a CMS

Build a clean reference set of tags when porting a site between WordPress, Ghost, Webflow, or a headless stack.

04

Marketing landing pages

Spin up campaign-specific titles, descriptions, and OG images for paid traffic without touching shared theme files.

Frequently Asked Questions

Aim for 50-60 characters in the title (Google truncates around 600 pixels of rendered width) and 150-160 characters in the description on desktop, dropping to about 120 for mobile snippets. Going longer is not penalized, but the extra text is replaced with an ellipsis.
No. Google dropped support in 2009, Bing dropped active use shortly after, and the tag is now ignored by every major search engine. Including one only exposes your keyword strategy to anyone who views the page source. The generator omits it on purpose.
A canonical tag tells search engines which URL is the authoritative version of a page when several URLs serve the same content (tracking parameters, trailing slashes, http vs https). Without one, ranking signals split across duplicates and the wrong URL may get indexed.
Open Graph is the Meta-originated standard adopted by Facebook, LinkedIn, Slack, Discord, WhatsApp, and most other unfurlers. Twitter has its own twitter:* tag set that overrides OG when present. Most pages need both — the generator emits matching pairs.
1200x630 pixels at a 1.91:1 ratio is the universal target. It satisfies Facebook's recommended size, Twitter's summary_large_image card, and LinkedIn. Keep file size under 1 MB and prefer JPEG or PNG; AVIF and WebP support is still inconsistent across unfurlers.
Each platform caches link previews independently. Facebook caches for roughly 30 days, Twitter and LinkedIn for similar windows, Slack until the workspace clears it. Use Facebook's Sharing Debugger, LinkedIn's Post Inspector, or Twitter's Card Validator to force a recrawl.
Yes for viewport — it is required for mobile rendering. Robots only needs an explicit tag if you are deviating from the default index,follow behavior, for example to noindex a tag archive or staging URL. The generator includes a robots field for those cases.
Inside the head element, ideally near the top before any external script tags. Some unfurlers stop parsing after the first 1 MB or first script, so meta tags placed late or after analytics snippets sometimes get missed. Above-the-fold in the head is safest.
Yes — copy the values into a Next.js Metadata export (app router) or into a Helmet/next-seo block. The generator outputs raw HTML, but the field names are 1:1 with Next.js Metadata keys, so the mapping is straightforward.
They are necessary but not sufficient. Meta tags describe the page; ranking depends on content quality, internal linking, page experience, and increasingly Schema.org structured data. Use the schema generator alongside this tool for a complete head block.

Advertisement