Meta Tag Generator
Fill in a short form and get a clean, copy-paste block of title, description, canonical, Open Graph and Twitter Card tags, correctly sized and ready for your <head>.
Your page
Meta tags are the small pieces of code in your page's <head> that tell search engines and social platforms how to title, describe and preview your page. Writing them by hand is fiddly and easy to get wrong: a missing canonical, a mistyped Open Graph property, an image at the wrong ratio. This free generator builds the whole block for you from a short form, checks your title and description against Google's pixel limits as you type, and gives you copy-paste code for your <head>. It is made for site owners, developers and content writers who want clean, correct markup without memorising every property name.
How to use it
Fill in the essentials
Enter your page title, meta description, URL and content language. The generator builds the markup live and flags your title and description when they run past Google's pixel widths.
Add social and advanced tags
Open the social section for Open Graph and Twitter Card fields, including a share image, and the advanced section for canonical, robots directives and author. Leave a field blank and it is simply omitted.
Copy the block into your <head>
Hit copy and paste the generated tags inside the <head> of your page. Nothing is sent anywhere; the code is built entirely in your browser.
Why it's useful
Correct markup without the memorising
Open Graph and Twitter Card properties are easy to misspell, and one wrong attribute silently breaks a preview. The generator uses the right property names every time and fills sensible defaults, so the block is valid before you ever paste it.
Sized for the SERP as you type
The title and description fields show their rendered pixel width against Google's limits, not just a character count, so you catch a title that will be truncated before it ships rather than after.
Nothing leaves your browser
Every tag is generated client-side. Your drafts, URLs and unpublished pages are never uploaded or stored, so you can safely prepare markup for client work and staging sites without signing in.
What these tags do, and what they do not do
Getting the share image right
1200 by 630 pixels is the size every major platform crops cleanly to, and it is the ratio the generator writes into the og:image width and height tags. Feed a social platform a different ratio and it decides what to cut, usually from the top and bottom, which is how text-heavy share images end up beheaded in the feed. A wider or taller image also risks falling back to a small square thumbnail on some networks, losing the large-card treatment entirely. The safest approach is to export at 1200 by 630 and keep logos, faces and any words well away from the edges so nothing important sits in the crop zone.
Why your new image does not show up
Platforms cache link previews aggressively. Once Facebook, LinkedIn or Slack has fetched your page, it can keep serving the old image and title for days no matter what your tags now say. Some networks offer a debugger that forces a refetch, which is the quickest fix for a single URL. The reliable fix at scale is to publish the new image under a new filename, so the URL itself changes and the cache has nothing old to serve.
Canonical tags are a signal, not a command
The canonical tag tells search engines which URL you consider the original when several pages show near-identical content, such as a product reachable through filters, tracking parameters or both www and non-www. Search engines usually follow it, which helps consolidate your visibility onto one URL instead of splitting it across duplicates. But it is a hint, not an instruction: they sometimes pick a different URL anyway, particularly when the pages are not as similar as the tag claims, or when your internal links and sitemap point somewhere else. Keep your canonicals consistent with the URLs you link to and list in your sitemap, so you are sending one clear signal rather than several conflicting ones.
Presentation, not ranking
These tags control how your page is presented, not where it ranks. A well-formed title and description make a result clearer and more clickable, and a correct Open Graph block makes a shared link look intentional instead of broken, which helps you get found and earns the click once you are visible. What they do not do is substitute for content worth reading. A tidy meta block around a thin page is packaging around an empty box. Use the generator to get the wrapper right, then make sure the page underneath genuinely answers the query, because that is what keeps you visible and worth citing. The same markup works whatever language you publish in, and Otorank tracks your visibility across 150+ languages once the page is live.
They use Otorank
Questions
What each tag is for, why previews cache, and where meta tags stop and content begins.
The title and meta description, a canonical link, robots directives and author, plus a full Open Graph and Twitter Card block for social previews. Blank fields are omitted so you only ship the tags you need.
1200 by 630 pixels. It is the ratio every major platform crops cleanly, and the generator writes the matching og:image:width and height tags. Keep important content away from the edges so nothing is cut.
They shape how your result is presented, which affects whether people click, not where the page ranks. Clear tags help you get found and earn clicks, but they do not replace content worth reading.
Social platforms cache link previews for days. Use the network's sharing debugger to force a refetch, or publish the image under a new filename so the URL changes and the old cache no longer applies.
No. The whole block is generated in your browser; nothing is uploaded or stored, so you can prepare markup for unpublished and client pages safely.