Meta Tag Generator
Turns what you type into a complete set of meta tags ready to paste into the page's <head>: the core tags, Open Graph and the Twitter card.
- Sign-in requiredMembership is free
- Open on the Ücretsiz plan5 runs a day
- Saved to your historyReachable from your account
What does this tool look at?
Anything that is easy to get wrong by hand, generated for you: meta tags, schema, robots.txt, sitemaps and redirect rules.
- Core, Open Graph and Twitter tags together
- Length limits checked as you type
- Output ready to copy and paste
What this tool measures
The common mistake with meta tags is not leaving them out, it is leaving them half done: title and description present but no canonical; Open Graph tags present but no image dimensions; a Twitter card declared that falls back to the small layout because no image was given.
From five inputs the tool produces the full set: title, description, canonical, robots (index, follow, max-image-preview:large), viewport, Open Graph and Twitter tags. Supply an image and og:image arrives with its 1200×630 dimension lines while the Twitter card upgrades to summary_large_image.
The same output is printed a second time as a Next.js Metadata object. On App Router you paste that object into the page instead of the HTML block; the canonical is written as a path, and your domain comes from the site configuration.
How to use it
- 1
Write title and description for this page
The title carries the promise, the description explains how it is kept. Never reuse one pair across pages; Google replaces duplicate descriptions with text of its own choosing.
- 2
Enter the full page address
The address becomes both the canonical and og:url. Strip filter and tracking parameters: a canonical pointing at a parameterised URL leaves Google unsure which version to index.
- 3
Add a share image
1200×630 pixels is the safe size. Without an image the og:image lines are omitted entirely and your link appears bare on WhatsApp, LinkedIn and X.
- 4
Pick the right locale
og:locale is printed as tr_TR, en_US or de_DE. On a multilingual site, generate each language version in its own language, then connect them with the Hreflang Generator.
- 5
Put the output in the right place
File paths are in the placement section below. After pasting, publish the page and confirm with the Rich Results Test or a social card preview.
When to use it
- Editing the head section of a hand-written HTML site page by page.
- Before sharing a new campaign page on social media, to guarantee how the card renders.
- Right after the Meta Tag Analyzer flags a missing canonical or og:image on an existing page.
- In a Next.js project, to start from a working metadata object rather than an empty one.
Reading the result
On a plain HTML site
The block goes into <head>, just before the closing tag. Delete any existing title or description first: with two title tags the browser takes the first and so usually does Google, so the second is wasted.
Next.js App Router
Use the Metadata object, not the HTML block. It goes at the top of app/<route>/page.tsx, above the default export. Keep shared values such as siteName and icons in app/layout.tsx and write only the differences per page.
WordPress
With Yoast or Rank Math installed, do not paste tags into the theme. Fill the plugin's SEO title, meta description and social image fields instead. Without a plugin, the block belongs in the <head> of wp-content/themes/<theme>/header.php.
Description length warning
The check expects 70 to 165 characters, with 150 to 160 as the sweet spot. Short descriptions let Google fill the gap with its own sentence; long ones get cut in the result line.
Image warning
With no image, twitter:card prints as summary, the small card. Add one and the same line becomes summary_large_image, which renders full width in feeds.
Questions about the Meta Tag Generator
Google dropped it as a ranking signal in 2009 and Bing ignores it. It was left out deliberately: all it does now is show competitors which terms you are targeting.
It permits Google to show a large image preview from your page in search results. It lifts click-through in Discover and image-heavy results and has no effect on indexing.
The same content is usually reachable with and without www, with and without parameters. The canonical states which address is the real one and stops link equity from splitting across duplicates.
Yes. One site-wide set prevents Google from treating each page as a distinct answer. With dozens of pages, define the title pattern in the Next.js layout and write only the changing field per page.
Use it alongside these
The other tools in the same category. Run them together and you see the whole picture.
The tool found the problem. Now for the fix
We run technical SEO, content and AI visibility work end to end. Let us review your site and come back with a clear list of what to do.
Monday – Saturday 09:00 – 18:00