SEOLivly
Menu
Home Tools Blog Services Contact Run the free scan

Meta Tag Generator - build the block, then write the words

Generate the meta block: title, description, canonical, robots, Open Graph and Twitter. Then write the title and description by hand: they are the copy.

This generator gives you a clean starting point, not a finished SEO strategy. Strong metadata still needs relevance, clarity, and a real reason for someone to click.
Site Title
Site Description
Site Keywords (Separate with commas)
Allow robots to index your website?
Allow robots to follow all links?
What type of content will your site display?
What is your site primary language?

(Optional Meta Tags)

Search engines should revisit this page after     days.


Author:



Captcha

A generator will happily produce a title and description for a page that has no argument, no research, and no reason to exist. The tag is not the problem. This tool handles the syntax: canonical, robots, Open Graph, Twitter cards, the description. It cannot write the sentence that makes someone click.

That is a writing job. And a generated description reads like a generated description, because it is one.

What this builds

You fill in the fields, it gives you a clean block you can paste into your template. Title, description, canonical, robots, Open Graph, Twitter card. That is the whole scope.

No score. No "SEO grade." No green checkmarks that make you feel like you shipped something. Just the tags, correctly quoted, in the order that works, ready to copy.

The old version of this page was a captcha-gated AtoZ form that made you solve a puzzle to get a title tag. That was silly. This is a builder and a copy button.

The syntax people get wrong

I have audited enough sites to know the same four mistakes show up every time. None of them are hard to fix. All of them are easy to miss because the page still loads.

  • Two canonicals. A CMS plugin adds one, the theme adds another, and now Google picks the wrong one or ignores both.
  • Unquoted content=. One missing quote and the rest of your head block becomes a text node. The page looks fine. The tags are gone.
  • Relative og:image. /images/hero.jpg works in a browser and fails in Slack, iMessage, and LinkedIn. It needs the full https:// URL.
  • Robots tag fighting the server. You write index,follow in the meta tag and your X-Robots-Tag header says noindex. The header wins. You will never see it in the HTML.

That last one is the reason I tell people to check the response headers, not just the source. The generator cannot see your headers. You have to look.

Title tags are copy, not metadata

The title tag is the thing a human reads in a search result. It is not a place to stuff keywords, and it is not a checkbox. It is a headline with a character limit and a competitor on either side.

Google rewrites titles when it thinks it has a better one. That is not a bug you can outsmart with a plugin. It is a reason to write a title that is actually the best description of the page, so Google has no reason to swap it.

Write the title first, in a doc, like a human. Then paste it into the generator. If you are staring at the field trying to invent a title, you are using the tool backwards.

Descriptions sell the click

A description gets about 140 to 160 characters before Google truncates it. In that space you get one promise, one specific thing, and one honest limit. That is it.

The mistake is writing a summary. Nobody clicks a summary. They click because the sentence named their problem and promised a specific answer. "Meta tag generator" is a summary. "Build the tag block, then write the words" is a promise with a limit baked in.

Google's snippet documentation is clear that the description is a suggestion, not a command. Google will rewrite it from page content when it wants to. Write it well anyway. The rewrite is usually worse.

The pre-publish check

Paste the block, upload the page, then actually look at what shipped. The generator builds the tags. It cannot verify the live page, and it cannot see what your CMS did to them on the way out.

Run the live URL through the meta tags analyzer and check the live page after you upload. It reads what the server actually returned, which is the only version that matters. If it flags a duplicate canonical or a missing og:image, fix it before you move on.

If you are still deciding which tags are worth writing by hand before you publish, the three tags worth writing before publish walkthrough covers the short list. If that post is not live yet, the word and character counter will at least keep your title and description inside the limits.

What a generator cannot do

It cannot choose the promise. It cannot know what the searcher actually wants when they type the query. It cannot read your analytics, your sales calls, or the three emails where a customer explained why they bought.

It cannot write a better title than you can. It can write a faster one. Those are not the same thing, and the difference shows up in click-through rate within a month.

The generator writes tags. You have to write the reason someone clicks. Treat the output as a starting point, not a publish button. A generated description is boilerplate, and it reads like boilerplate.

The tags that actually matter

Most pages need five tags. A few need more. Here is the honest breakdown, including the mistake I see on each one.

Tag What it does The mistake people make
</code></td> <td>The clickable headline in search results and browser tabs</td> <td>Keyword stuffing, or letting the CMS append the brand to every page</td> </tr> <tr> <td><code>meta description</code></td> <td>The snippet under the title, when Google uses it</td> <td>Writing a summary instead of a reason to click</td> </tr> <tr> <td><code>link rel="canonical"</code></td> <td>Tells Google which URL is the real one</td> <td>Two of them, or a canonical pointing at a redirect</td> </tr> <tr> <td><code>meta robots</code></td> <td>Index and follow instructions for the page</td> <td>Conflicting with the server header, or leaving <code>noindex</code> on after launch</td> </tr> <tr> <td><code>og:image</code></td> <td>The preview image on social and messaging apps</td> <td>A relative URL, or an image under 1200px wide that renders blurry</td> </tr> </tbody> </table> <p>Add Open Graph title and description when the page will be shared, which is most marketing pages. Add a Twitter card when you care about the preview on X. Skip the rest. Keywords meta tag has been dead for over a decade and adding it just tells competitors what you were aiming at.</p> <h2>A safe default block</h2> <p>If you want the minimum that will not embarrass you, build these: title, description, canonical, robots, og:title, og:description, og:image, og:url, twitter:card. That is nine lines and it covers search, social, and messaging.</p> <p>Everything else is conditional. Hreflang only if you have language variants. Article tags only on articles. Product schema only on product pages. The generator will not stop you from adding noise, so stop yourself.</p> <p>Once the block is in, go back to the writing. The tags are the easy part. The sentence is the work.</p> <h3>Which tags matter?</h3> <p>Title, description, canonical, robots, and og:image cover 90% of what most pages need. Everything past that is situational. If you only fix five things on a page, fix those five.</p> <h3>Should I use the generated description?</h3> <p>No, not as-is. Use it as a starting point if you are stuck, then rewrite it with the specific promise and the honest limit. A description that sounds like a generator wrote it will get skipped in the results, because it will read exactly like the nine other generated descriptions above and below it.</p> <h3>Is canonical required?</h3> <p>Not on every page, but on any page reachable by more than one URL. That includes trailing-slash variants, <code>?utm=</code> parameters, and <code>http</code> vs <code>https</code>. If you are not sure, add it. A correct canonical is cheap. A missing one is a slow leak.</p> <p>If you want to see what else is broken on the page beyond the tags, run the free 40-point scan at <a href="/website-auditor">/website-auditor</a>. If you would rather hand the whole site to someone who will actually fix it, the fix service is at <a href="/page/seoservices">/page/seoservices</a>. Either way, start with the free scan and see what it finds. You can also browse <a href="/tools">all the tools on the site</a> if you want to check the rest of the page yourself.</p> </article> <script type="application/ld+json"> {"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Which tags matter?","acceptedAnswer":{"@type":"Answer","text":"Title, description, canonical, robots, and og:image cover 90% of what most pages need. Everything past that is situational. If you only fix five things on a page, fix those five."}},{"@type":"Question","name":"Should I use the generated description?","acceptedAnswer":{"@type":"Answer","text":"No, not as-is. Use it as a starting point if you are stuck, then rewrite it with the specific promise and the honest limit. A description that sounds like a generator wrote it will get skipped in the results, because it will read exactly like the nine other generated descriptions above and below it."}},{"@type":"Question","name":"Is canonical required?","acceptedAnswer":{"@type":"Answer","text":"Not on every page, but on any page reachable by more than one URL. That includes trailing-slash variants, ?utm= parameters, and http vs https. If you are not sure, add it. A correct canonical is cheap. A missing one is a slow leak."}}]} </script> <section class="sl-more" aria-label="More SEO tools"> <h2>More free tools that return a result</h2> <div class="sl-more-grid"> <a href="/website-auditor"><strong>Website Auditor</strong><span>Forty checks on one page, sorted by what to fix first.</span></a> <a href="/meta-tags-analyzer"><strong>Meta Tags Analyzer</strong><span>Read the title, description and tags the way a crawler gets them.</span></a> <a href="/broken-links-finder"><strong>Broken Links Finder</strong><span>Every dead link on one page, with the status code.</span></a> <a href="/keyword-density-checker"><strong>Keyword Density Checker</strong><span>The phrases a draft really repeats. Runs in your browser.</span></a> <a href="/word-character-counter"><strong>Word & Character Counter</strong><span>Counts against the limits that matter: titles, metas, posts.</span></a> <a href="/spider-crawling"><strong>Spider Crawling</strong><span>The page as a bot gets it, before JavaScript.</span></a> </div> <p class="sl-more-all"><a href="/tools">All the tools, sorted by what works</a> · <a href="/page/seoservices">Have the fixes done for you</a></p> </section> </div><!-- /.sl-tool --> </main> <footer class="site-foot"> <div class="wrap foot-grid"> <div class="foot-brand"> <span class="foot-wordmark">SEO<span>Livly</span></span> <p>Free SEO tools that return a result, and a one-time fix for sites that are drowning. One person, no agency theatre.</p> </div> <div> <h2 class="foot-h">Tools</h2> <ul> <li><a href="/website-auditor">Website Auditor</a></li> <li><a href="/meta-tags-analyzer">Meta Tags Analyzer</a></li> <li><a href="/broken-links-finder">Broken Links Finder</a></li> <li><a href="/keyword-density-checker">Keyword Density</a></li> <li><a href="/tools">All tools</a></li> </ul> </div> <div> <h2 class="foot-h">Site</h2> <ul> <li><a href="/page/seoservices">SEO services</a></li> <li><a href="/blog">Blog</a></li> <li><a href="/page/about-us">About</a></li> <li><a href="/contact">Contact</a></li> </ul> </div> <div> <h2 class="foot-h">The honest bit</h2> <p class="foot-small">No rankings guaranteed. The free scan is free because it costs me almost nothing to run.</p> </div> </div> <div class="wrap foot-bot"> <span>Copyright © 2025 Seolivly. All rights reserved.</span> <span><a href="/page/privacy-policy">Privacy</a> · <a href="/page/terms-conditions">Terms</a></span> </div> </footer> <!-- Framework JS --> <script src="https://www.seolivly.com/theme/simpleX-custom/app-assets/vendors/js/core/bootstrap.min.js"></script> <script type='text/javascript' src='https://www.seolivly.com/theme/simpleX-custom/js/sweetalert.min.js'></script> <script src="https://www.seolivly.com/theme/simpleX-custom/js/app.js" type="text/javascript"></script> <script src="https://www.seolivly.com/rainbow/master-js" type="text/javascript"></script> <!-- Statcounter --> <script type="text/javascript"> var sc_project=12529609; var sc_invisible=1; var sc_security="0b5455d8"; </script> <script type="text/javascript" src="https://www.statcounter.com/counter/counter.js" async></script> <script>window.os = window.os || function(){}; window.cs = window.cs || function(){};</script> </body> <script>'undefined'=== typeof _trfq || (window._trfq = []);'undefined'=== typeof _trfd && (window._trfd=[]),_trfd.push({'tccl.baseHost':'secureserver.net'},{'ap':'cpbh-mt'},{'server':'p3plmcpnl485736'},{'dcenter':'p3'},{'cp_id':'8722209'},{'cp_cl':'8'}) // Monitoring performance to make your website faster. If you want to opt-out, please contact web hosting support.</script><script src='https://img1.wsimg.com/traffic-assets/js/tccl.min.js'></script></html>