Fill in the fields and copy the exact title, description, robots, Open Graph and Twitter Card tags for your page head, with live character counters.
The tags are assembled locally in your browser. Nothing you type is sent anywhere.
Honest note: Google has ignored this tag since 2009. It is emitted only if you fill it, as a comment-flagged line.
og:image must be an absolute https:// URL — 1200×630 px, under 8 MB is the safe format.
summary_large_image wants 1200×630 (1.91:1); plain summary crops a ~1:1 thumbnail.
hreflang alternates are not emitted here: they need one link per language version of the page — add them manually if the site is multilingual.
The builder writes real HTML elements, in head order: <title> and description for search results, canonical and robots directives for indexing control, then the Open Graph and Twitter Card blocks that social scrapers read when your link is shared. Everything you see in the preview is paste-ready inside your <head> — attributes are escaped, so quotes and ampersands in your text survive.
/img/og.jpg silently fails and the preview renders empty. Use the full https:// address, under 8 MB, ideally 1200×630 for the standard 1.91:1 crop. The builder warns when you leave a relative path in.summary pairs a small square thumbnail with your text; summary_large_image takes the wide 1200×630 hero. X historically required whitelisting for large cards on unfamiliar domains, so check the first share in the card validator. Image ratios outside ~2:1 to ~1:1 get cropped or letterboxed, hence the size hint under the field.No. Google has ignored the keywords meta tag since 2009, and Bing treats heavy keyword lists as a spam signal. The field exists here because some internal site search engines and very old crawlers still read it — if you use it, keep it short and honest. Your time is far better spent on the title, description and headings of the page itself.
They serve different scrapers with different dialects. Facebook, LinkedIn, WhatsApp and most messengers read og:*; Twitter/X reads twitter:* (it does fall back to OG when card tags are missing, but loses control over card type). The mapping is direct: og:title → twitter:title, og:description → twitter:description, og:image → twitter:image, and twitter:card picks the layout. The "use Open Graph content" switch here writes both blocks from one input.
Use the official debuggers rather than guessing: Facebook's Sharing Debugger re-scrapes og:* tags on demand, and the X (Twitter) Card Validator does the same for cards — both tell you when a cached scrape is stale so you can force a refresh. Search for "Facebook Sharing Debugger" or "X Card Validator" to reach the current versions from the platforms themselves.
A page has exactly one title element and one canonical description. Search engines show either your title or, when they judge a page passage more relevant, that passage instead — you can only influence, not dictate. Social previews, by contrast, are what you declare: og:title and og:description are shown as written, which is why giving them slightly different wording than the SERP title is a legitimate strategy.
No. The tags are assembled with plain JavaScript in the browser from your form inputs; copy and download are client-side too. No URL you type is fetched or sent anywhere while you use the tool.
If you just finished with Meta Tag Generator, the natural next steps are UTM Link Builder, App Icon Generator, Favicon Generator, or browse every tool in Daily Tools.