Runs 100% in your browser — your input never leaves this page.
Page details
Ignored by Google since 2009 — included only for legacy systems.
Open Graph (Facebook, LinkedIn…)
X (Twitter) card
Live previews
Preview — approximate rendering. Google may rewrite titles/descriptions; card rendering varies by platform.
Google — preview, approximate
Your page title
https://example.com/page
Your meta description will appear here.
Facebook — preview, approximate
example.com
Your page title
Your description.
X — preview, approximate
Your page title
Your description.
Generated tags
Paste inside your page's <head>.
Working…
Something went wrong
Your results will appear here.
Fill in the input above and run the tool to get started.
Honest limits
Meta keywords are ignored by Google, and descriptions earn clicks — not rankings.
How to use the Meta Tag Generator
Fill in your title and description — the character counters and previews update as you type.
Add Open Graph and X card details so shared links look right on social platforms.
Copy the generated tags and paste them into your page's <head>.
Examples
Example
Title Blue Widget — Free Shipping | Example Store (52 chars, within the 60-character guide) → the Google preview shows exactly how it would look in results.
What this tool doesn't do
Previews are simulations — Google may rewrite titles and descriptions, and social card rendering varies by platform.
Character guides (60 / 155) are rules of thumb; Google truncates by pixel width, not characters.
Good meta tags help click-through; they are not a ranking shortcut.
Frequently asked questions
Yes — fill the form, copy the code, no account and no payment.
Indirectly. The title is a genuine ranking signal and the description drives clicks. The rest (OG, Twitter, canonical, viewport) are about display correctness, social sharing, and technical hygiene — they make your SEO work count, but they don't rank you by themselves.
Inside your HTML's <head> section. In WordPress, use your theme's header file or an SEO plugin's custom-code area; in static sites, paste it into the template before </head>.
You can generate a block per page, but don't duplicate one block across the site — every page deserves its own title and description. Duplicate titles across pages is one of the most common on-page issues.
Social platforms cache link previews. After fixing tags, re-scrape the URL: Facebook's Sharing Debugger and X's Card Validator force a fresh fetch.
X falls back to Open Graph tags when Twitter Card tags are absent, so the page will still render. But explicit twitter: tags give you control over the card type, which the fallback doesn't guarantee — generate both.
HTML meta tags (like og:title, og:description, og:image) that tell social platforms how to build the preview card when your page is shared. They live in the page's <head>.
Facebook, LinkedIn, WhatsApp, Telegram, Slack, Discord, and most chat apps. X (Twitter) has its own Twitter Card tags but falls back to Open Graph tags when they're missing.
website is the default for general pages; article is for blog posts and news, and supports extra properties like publish date and author. For most homepages and landing pages, website is correct.
Not directly for rankings, but they increase social click-through and share quality, which drives referral traffic and brand visibility.
Most messaging apps cache link previews aggressively. After fixing tags, test with a fresh URL (add a query parameter) or wait for the app's cache to expire — the tags themselves are usually fine.
1200×630 pixels is the widely recommended size — it displays well across Facebook, LinkedIn, and X without awkward cropping.
Generally no — platforms all read the same tags from the same URL. You can serve different tags per user-agent, but that's advanced territory and easy to get wrong; one correct set works for everyone.
summary shows a small thumbnail; summary_large_image shows a large wide image. Large-image cards get more visual attention in the timeline and are the standard choice for most content.
For large-image cards, 1200×675 pixels (2:1 ratio) is the recommended size. Images must be hosted on an absolute HTTPS URL — relative paths won't render.
Common causes: X has a cached version of the page (re-validate the URL), the page blocks X's crawler via robots.txt, the image URL is relative or too small, or the tags sit outside the <head> section.
Yes — the tags work on any public page. The twitter:site handle is optional; cards render fine without it.
Not directly, but better-looking shares earn more clicks and engagement from X traffic, which supports visibility and brand growth.
No — unlike the old days, there's no approval process anymore. Add valid tags to a public page and cards render automatically when the link is shared.
X crops card images to fit its layout, and images below the recommended size get stretched. Use 1200×675 for large-image cards, keep key content centered with safe margins, and use an absolute HTTPS URL.
A meta tag is a short piece of HTML in a page's <head> that describes the page to browsers and search engines — for example the title and description shown in search results. Visitors do not see meta tags on the page itself, but search engines and social platforms read them.
At minimum, every page should have a unique title tag and a meta description. Add Open Graph tags if the page is shared on social media, and a robots tag only when you want to control how search engines crawl or index the page.