Free meta tag generator
Fill in your page details and copy a complete, correct head block: title, description, canonical, Open Graph, and Twitter card tags. Everything runs in your browser - nothing is uploaded, no signup.
Becomes the title tag, og:title, and twitter:title. Aim for 60 characters or less so search results and cards do not truncate it.
The meta description, og:description, and twitter:description. 160 characters or less keeps it intact everywhere.
Used for the canonical link and og:url. Must be the full, absolute address.
og:image must be an absolute https URL - platforms ignore relative paths.
The 1200x630 image shown above your link. Don't have one? Make one in the free editor in about a minute.
Your tags
Paste this inside the <head> of your page, then verify it with the link preview checker.
Rough preview
yoursite.com
Your page title
Your description
Approximate. Each platform renders cards slightly differently - the checker shows per-platform previews for a live URL.
What each tag does
Social platforms and search engines read a small set of tags from your page's head to build the preview card and the search snippet. This is the complete set the generator writes, and what each one controls.
| Tag | What it controls | Practical limit |
|---|---|---|
| title | The browser tab and the search result headline | 60 characters |
| meta description | The search snippet under the headline | 160 characters |
| link rel="canonical" | Which URL search engines treat as the original | Absolute URL |
| og:title / og:description | The headline and text on the share card | 60 / 160 characters |
| og:image | The picture on the card - the biggest click lever | 1200x630, https, under 5 MB |
| og:image:width / height | Lets platforms lay out the card before downloading the image | Match the real file |
| og:url | The canonical address shown and shared on the card | Same as canonical |
| og:type | website for landing pages, article for posts | One value |
| og:site_name | The small brand line some platforms show above the title | Your brand name |
| twitter:card | Opts in to X's large-image layout; without it X may show no card | summary_large_image |
| twitter:title / image / description | X-specific overrides; X falls back to og:* when absent | Same as og:* |
| og:image:alt / twitter:image:alt | Screen-reader text for the card image | One sentence |
Five rules that prevent most broken previews
- Make og:image absolute and https. A relative path like /images/og.png works in your browser and fails on every platform.
- Use 1200x630 pixels. It is the 1.91:1 size platforms recommend. Below roughly 600px wide, Facebook demotes the card to a small thumbnail.
- Always set twitter:card. X reads og:image for the picture, but the large layout is opt-in through twitter:card=summary_large_image.
- Keep og:url equal to the canonical. Mismatched URLs split share counts and confuse crawlers.
- Expect caching after changes. Platforms cache previews aggressively. Facebook re-scrapes via the Sharing Debugger, LinkedIn via the Post Inspector; for X, change the image URL (for example ?v=2).
The og:image is the biggest lever
Tags decide whether a card renders; the image decides whether anyone clicks it. Pages with a purposeful 1200x630 og:image get a large, branded preview instead of a random screenshot or an empty gray box.
The betterimage editor generates that image in the browser for free: pick a template, type your headline, download the exact PNG you previewed. The OG image generator page covers sizes and setup in detail.
Publishing many pages? Dynamic OG images render a unique, on-brand image for every page from one saved template - one meta tag, no rebuilds.
Meta tag questions, answered
What are meta tags and why do they matter?
Meta tags are short lines in your page's head that tell search engines and social platforms what the page is about. They control the search snippet, and Open Graph tags control the card (image, title, description) shown when the link is shared on X, Facebook, LinkedIn, Slack, Discord, or WhatsApp.
Do I need both Open Graph and Twitter tags?
Yes, but only a few Twitter ones. X falls back to og:title, og:description, and og:image for content, yet the large card layout itself is opt-in through the twitter:card tag. The generator includes the right minimal set automatically.
What size should the og:image be?
1200x630 pixels, a 1.91:1 ratio, served over https as PNG or JPEG. The editor exports exactly that size for free, plus five other platform sizes from the same design.
I updated my tags but the preview did not change. Why?
Platforms cache previews aggressively. Force a re-scrape with Facebook's Sharing Debugger or LinkedIn's Post Inspector. X has no public refresh tool - the practical workaround is changing the image URL, for example by appending ?v=2.
Does this tool upload or store anything?
No. The tags are assembled by JavaScript in your browser as you type. Nothing you enter leaves the page.
How do I generate an og:image for hundreds of pages?
Design one template in the editor, save it, and use dynamic OG images: each page points its og:image tag at a signed URL with that page's title, and the API renders a unique on-brand image per page.