Meta Tag Generator Free Tool

Site Title

Site Description

Site Keywords (Separate with commas)

Allow robots to index your website?

Yes No

Allow robots to follow all links?

Yes No

What type of content will your site display?

UTF-8 UTF-16 ISO-8859-1 WINDOWS-1252

What is your site primary language?

English French Spanish Russian Arabic Japanese Korean Hindi Portuguese No Language Tag

---

(Optional Meta Tags)

Search engines should revisit this page after     days.

Author:

About Meta Tag Generator

What This Tool Actually Does

The Meta Tag Generator on limitlessreferrals.info is a server-side form that produces a fixed block of eight HTML meta tags for you to copy into the head of a web page. You fill in a title, a description, a keyword list, and a few choices about robots, character encoding, and language. When you submit the form, the server assembles the tags in a set order and shows them inside a <pre> box under the heading "Copy and paste into your site." There is no copy button and no download option. You select the text by hand and paste it where you need it.

This is a small, focused tool. It does one thing without asking for an account or showing a CAPTCHA. The form posts to /meta-tag-generator/output, and the result appears on a fresh page with a "Try New Document" button that takes you back to the start. The whole interaction takes about ten seconds. You will not find character counters that the server enforces, length validations, or a search preview anywhere in the flow.

The output is fixed in structure. Every generated block contains the same lines in the same order, with your text dropped into the content attributes. The live test run for this rewrite used the title "my test page", a description containing a quoted phrase and a line break, keywords "seo, tools", index and follow for robots, UTF-8, English, a revisit-after period of seven days, and an author name of Jan. That test produced exactly eight lines, which appear in the table later in this article.

The server applies three transformations to your input before assembling the block. The first letter of the title is capitalised. Line breaks are removed from the description and keywords, with the lines joined together and no space inserted between them. Double-quote characters that you type are escaped into the literal text ". That last behaviour is a quirk of the order in which the server runs its processing.

You type a description like A "quoted" description. The server HTML-escapes the input first, which turns your quote into the six-character sequence ". Then the quote removal step runs, but by that point there are no actual quote characters left to remove. The literal text " survives into the output. So the generated tag reads content="A "quoted" description". This is valid HTML, and browsers will render it correctly, but it looks odd when you read the source code. You will see the entity, not the character you typed.

The form itself is straightforward. There is a text field for the site title and a textarea for the description. A second textarea accepts keywords as a comma-separated list. Two sets of radio buttons ask whether robots may index the site and whether robots may follow all links. A dropdown offers four character encodings, which are UTF-8, UTF-16, ISO-8859-1, and WINDOWS-1252. Another dropdown offers ten language choices, which are English, French, Spanish, Russian, Arabic, Japanese, Korean, Hindi, Portuguese, and "No Language Tag". Two optional checkboxes add a revisit-after line with a number of days and an author line with a name. A browser-side check refuses to submit an empty title or description, and that check lives in the page's JavaScript.

The tool's name says generator, and that is what it is. It generates meta tags. It does not generate the <title> element that appears in browser tabs and search results, and it does not generate a viewport tag, a canonical link, or any Open Graph or Twitter Card tags. Those absences matter, and a later section of this article explains why the old description of this page got them wrong.

The category on the site is Meta Tags Tools, and the tool sits alongside an analyzer, a keyword density checker, and a robots.txt generator in the same family. You can reach all of them from the site's SEO tools index. This generator is the one you use when you want a starting block of classic meta tags and you prefer to type your content into a form.

How to Use This Tool

1. Open the tool page. Find the input box above this article and make sure you are on the Meta Tag Generator page at limitlessreferrals.info.
2. Fill in the required fields. Type a site title in the first text field and a description in the textarea. The page will refuse to submit if either one is empty, so give both a value.
3. Choose your options. Add keywords as a comma-separated list, pick index or noindex for robots, pick follow or nofollow, choose a character encoding from the four options, and choose a language from the ten options or select "No Language Tag".
4. Tick the optional lines. If you want a revisit-after tag or an author tag, tick the checkbox for each and enter a number of days or a name.
5. Submit the form. Click the button that posts your entries to the output page. The server will capitalise the first letter of the title, strip line breaks, and show your block inside a <pre> box.
6. Copy the block and paste it. Select the text inside the box by hand and paste it into the head of your HTML document. Use the "Try New Document" button when you want to start over with different values.

That is the entire workflow. There is no preview of how the snippet will look in search results, no export file, and no way to save multiple documents. You generate one block at a time.

What the Output Looks Like

The live test run for this rewrite produced a block that you can examine line by line. The table below shows each tag as it appeared in the output, with the exact content values from the test.

Two details in that table stand out. The description in the test contained a quoted phrase and a line break. The quote became " in the output, and the line break vanished so that the second line of the description ran straight into the first with no space between them. The title "my test page" became "My test page" because the server capitalised the first letter.

The block is shown inside a <pre> element, which preserves the line breaks between tags. Each tag sits on its own line. The order is always the same, and the optional lines appear at the end. If you do not tick the revisit-after or author checkboxes, those lines simply do not appear, and the block ends with the language line or the Content-Type line.

There is no closing comment after the block, no instructions inside the output box, and no indication of which lines are still supported by search engines. The tool gives you raw HTML and leaves the interpretation to you.

Correcting the Old Description of This Tool

The previous version of this page made several claims about the output that do not match what the server actually produces. Those claims have now been corrected, and this section names them so that anyone who read the old copy understands what changed.

The old description said the tool assembles a <title> tag. It does not. The output contains a line that reads <meta name="title" content="...">, which is a meta tag with a name attribute, not the <title> element that belongs in the head of an HTML document. Google does not use the meta name="title" line as a substitute for the real title element. The distinction matters because many people copy a block like this into their page and wonder why the browser tab shows the site name instead of their carefully chosen title.

The old description said the tool generates a viewport tag. It does not. There is no <meta name="viewport" content="width=device-width, initial-scale=1"> anywhere in the output. The viewport tag is what tells mobile browsers how to scale the page, and its absence means a page that uses only this generator's block will render on a phone at a desktop width unless you add the tag yourself.

The old description said the tool includes a charset declaration. It includes a line that reads <meta http-equiv="Content-Type" content="text/html; charset=utf-8">, which is the older form of the charset declaration. It does not include the modern shorthand <meta charset="utf-8">. Both forms work in practice, and the http-equiv form is still honoured by browsers, but the modern form is shorter and is what most current documentation recommends.

The old description said the tool produces Open Graph and Twitter Card tags depending on the version of the tool. It does not. There is no og:title, no og:image, no twitter:card, and no other social media tag in the output. The old FAQ about Open Graph implied that the tool might cover social sharing, and that implication was wrong. When you share a page built from this generator's block on Facebook, X, or LinkedIn, the platform will have no structured data to read and will fall back to guessing.

The old description also failed to mention three behaviours that the server applies to your input. It did not say that the first letter of the title is capitalised. It did not say that line breaks are removed from the description and keywords with no space inserted. It did not say that typed double quotes turn into the literal text ". The live test run for this rewrite confirmed all three behaviours, and the corrected description in this article now covers them.

The corrected picture is simpler. This tool generates a fixed block of classic meta tags, some of which search engines still read and some of which they ignore. The old description dressed the tool up as something more capable than it is. The tool remains useful as a starting point, but you should know exactly what you are getting before you paste it into a production page.

Which Lines Still Matter in 2026

Search engine support for meta tags has changed a great deal since the late 1990s, when webmasters stuffed keywords into every available attribute and hoped for the best. The output of this generator is a time capsule of that era, and some of its lines have aged better than others. The live test output contains eight lines. Two of them still carry weight with Google and other major engines. The rest are ignored, deprecated, or only marginally useful.

The description meta tag is the first line that still matters. Google uses the meta name="description" content as a source for the snippet text that appears under your page title in search results, though it may choose a different snippet if it decides your description is not a good match for the query. Bing behaves similarly. A well-written description of roughly 150 to 160 characters gives the engine a clear summary to work with. The generator places no length limit on this field, so you have to judge the length yourself.

The robots meta tag is the second line that still matters. The output of this generator shows content="index, follow" when you choose those options, and that is the default behaviour for search engines even when no robots tag is present. The tag becomes useful when you choose noindex or nofollow, because those values instruct engines to stay away from the page or to avoid following its links. Google has supported the robots meta tag since the late 1990s, and it remains a reliable way to control crawling and indexing at the page level.

The other six lines in the output range from ignored to never-supported. The meta name="keywords" tag has been ignored by Google since 2009, when Google's Matt Cutts announced that the company does not use the keywords meta tag for ranking. Bing has said it gives the tag no weight either. You can leave the line in your page and it will do no harm, but it will do no good.

The meta name="revisit-after" tag was never supported by any major search engine. It was a suggestion that a crawler should come back after a certain number of days, and no engine implemented it. The line is harmless but pointless. The meta name="language" tag, which this generator fills with plain English words like "English" or "French", is similarly ignored. Search engines detect the language of a page from its content, and the tag does not use the BCP 47 codes like en or fr that the HTML lang attribute requires.

The meta name="title" line is a special case. It is not the same as the <title> element, and Google does not use it to determine the title shown in search results. Some older directories and non-Google systems may read it, but for modern search engine optimisation it is dead weight. The http-equiv="Content-Type" line is the old form of the charset declaration, and while browsers still honour it, the modern <meta charset="utf-8"> shorthand does the same job in fewer characters.

You should keep the description and robots lines, and you can drop the rest without losing anything that a search engine will notice. The author line has no effect on rankings, though it can be useful for attribution inside your own organisation. The charset line should stay in some form, because declaring the character encoding is good practice, but you can modernise it to the shorthand version.

What Is Missing from the Output

The generator's fixed block covers the classic meta tags, but a complete modern document head needs several elements that this tool does not produce. If you paste the output into a page as-is, you will have a head that works for basic indexing but lacks the structure that current best practice recommends.

The most obvious absence is the <title> element. The generator produces a meta name="title" line, which is not the same thing. The <title> element is a required part of any HTML document, and it appears in the browser tab, in bookmarks, and as the clickable headline in search results. Google constructs the search result title from the <title> element, not from the meta title line. You must add <title>Your Page Title</title> to your head yourself, because this tool will not do it for you.

The viewport tag is also absent. Mobile browsers assume a page width of 980 pixels unless you tell them otherwise with a viewport meta tag. Without one, a page built from this generator's block will appear zoomed out on a phone, with tiny text and a horizontal scroll. The standard tag is <meta name="viewport" content="width=device-width, initial-scale=1">, and you should add it to every page you build.

The canonical link is missing. A canonical tag tells search engines which URL is the preferred version when the same content appears at multiple addresses. The tag looks like <link rel="canonical" href="https://example.com/page/">. Without it, engines have to guess which of several URLs should rank, and they sometimes guess wrong. This generator gives you no way to specify a canonical URL.

Open Graph tags are missing. Facebook, X, LinkedIn, and other platforms read Open Graph meta tags to build the preview cards that appear when someone shares a link. The essential tags are og:title, og:description, og:image, and og:url. Twitter has its own Twitter Card tags, which overlap with Open Graph. The generator produces none of these, so shared links will show whatever the platform can scrape from the page content, often with an ugly or missing image.

The generator also omits the lang attribute on the <html> element. That attribute, written as <html lang="en">, tells browsers and assistive technology which language the page is in. The generator's meta name="language" tag uses plain English words, and it sits in the head rather than on the root element. Screen readers and translation tools rely on the lang attribute, so you should add it when you build your page.

The generator is a starting point, not a complete solution. You take its eight lines, keep the description and robots tags, add the missing elements by hand, and you have a respectable document head. A later section of this article walks through that process.

The Quote and Line Break Quirks

The live test run for this rewrite exposed two quirks in how the server handles your input, and both are worth understanding before you type a long description. The first quirk involves double quotes. The second involves line breaks.

When you type a double-quote character into the description or keywords field, the server runs its HTML escaping before it runs its quote removal. The escaping step converts your " into the six-character sequence ". The quote removal step then looks for actual quote characters, finds none, and leaves the entity alone. The result is that the output contains the literal text " inside the content attribute, as the live test demonstrated with A "quoted" description becoming A "quoted" description.

This output is valid HTML. When a browser parses the content attribute, it decodes the entity back into a quote character, and the rendered page shows your sentence exactly as you typed it. The oddity only appears when you read the raw source code or when a search engine ingests the raw HTML. The entity is longer than the character it represents, which matters if you are counting characters toward a snippet length limit, and it makes the source harder to read.

The second quirk is line break removal. If you type a description that spans multiple lines in the textarea, the server removes the line breaks and joins the lines together with no space between them. The live test used a description with a second line that read "second line", and the output showed descriptionsecond line, with the two words running into each other. If you want a space where the line break was, you have to type that space yourself at the end of the first line.

These two quirks are consequences of the order in which the server processes the input, and they produce output that is valid HTML even if it reads strangely. The practical advice is to avoid double quotes in your description and to keep your description on a single line. Use single quotes or rephrase to remove the quotes, and type your description as one continuous line of text.

Rate Limits and Privacy

This tool does not show a CAPTCHA and it does not have a per-tool request cap. The form is open to anyone who reaches the page, and you can submit it as many times as you like within a single session. There is a site-wide throttle that applies to every page on limitlessreferrals.info, and it works on a simple rule. If one visitor address makes more than fifteen requests within a single second, that address receives a 503 error for the rest of the day.

For a form tool like this one, the throttle is unlikely to affect you. You fill in the form, submit it once, read the output, and copy the block. The whole interaction involves two or three requests. You would have to automate submissions at a rate of more than fifteen per second to trip the throttle, and even then the block would only last until the end of the day.

The tool makes no request to this site when you are merely reading this article. The Meta Tag Generator performs its work on the server when you submit the form, so the check happens at submission time. The output page is a separate URL, and the server assembles your block fresh for each submission. Nothing about the tool requires you to create an account or provide an email address.

Limitations

The Meta Tag Generator has a clear scope, and the limitations come straight from the code that runs it. There is no character counter that the server enforces. The small hint next to the fields is browser-only, which means you can submit a description of any length and the server will accept it. There is no length validation at all, so a description of two thousand characters will produce a two-thousand-character content attribute.

There is no preview of how your snippet will look in search results. Many modern SEO tools show you a Google-style preview with the title, URL, and description rendered as they would appear on a results page. This tool does not. You see the raw HTML block and nothing else. Judging whether your description will fit in the snippet is entirely up to you.

The tool handles one page at a time. There is no batch mode, no CSV import, and no way to generate meta tags for a whole site in a single pass. If you have two hundred product pages, you will submit the form two hundred times.

There is no export. The output appears in a <pre> box, and you copy it by hand. There is no download button, no copy button, and no API. The "Try New Document" button simply reloads the form for another submission.

The quote and line break quirks described earlier are also limitations in practice. Typed double quotes become " entities, and multi-line descriptions get joined without spaces. You can work around both by typing carefully, but the tool gives you no warning that these transformations will happen.

Using the Block as a Starting Point

The output of this generator is best treated as a foundation that you extend by hand. The eight lines give you a working set of classic meta tags, and you can paste them into a template that already contains the missing modern elements. The process takes a few minutes and produces a document head that covers both the old and the current requirements.

Start by pasting the generated block into the head of your HTML document, between the <head> and </head> tags. Then add a real <title> element above or below the block. Use the same text you typed into the site title field, because the generator's meta name="title" line does not serve the same purpose. The <title> element is what appears in the browser tab and in search results.

Add the viewport tag next. The standard line is <meta name="viewport" content="width=device-width, initial-scale=1">, and it should appear early in the head so that mobile browsers read it before rendering the page. Place it before any stylesheets.

Add a canonical link if you know the final URL of the page. The tag is <link rel="canonical" href="https://example.com/your-page/">, and it tells search engines that this URL is the preferred version. If the page is reachable through multiple URLs, the canonical tag prevents duplicate content issues.

Add Open Graph tags if you expect the page to be shared on social media. The four essential tags are <meta property="og:title" content="Your Title">, <meta property="og:description" content="Your Description">, <meta property="og:image" content="https://example.com/image.jpg">, and <meta property="og:url" content="https://example.com/your-page/">. Facebook, X, LinkedIn, and WhatsApp all read these tags to build share previews.

Change the <html> tag to include a lang attribute. If your page is in English, write <html lang="en">. If it is in French, write <html lang="fr">. The generator's language tag uses plain words, so you have to make this change yourself.

Decide which of the generator's lines you want to keep. The description and robots lines are worth keeping. The charset line should stay, though you can shorten it to <meta charset="utf-8">. The keywords, revisit-after, language, and meta title lines can be deleted without any loss of search engine support. The author line is optional and has no ranking effect.

The result is a document head that covers the classic meta tags, the modern mobile requirements, the social sharing tags, and the language declaration. The generator saved you the trouble of typing the basic tags, and you added the rest by hand.

Related Tools

When you want to check whether the meta tags on a page you already published are working as intended, use the Meta Tags Analyzer to inspect what a page is actually sending to search engines and social platforms.

If you are optimising a page's content and want to know which phrases appear most often, the Keyword Density Checker counts keyword occurrences and shows you the balance of your text.

When you need to control how search engines crawl your whole site, the Robots.txt Generator builds the rules file that sits at the root of your domain.

Frequently Asked Questions

Does this tool generate a <title> tag?

No. The output contains a meta name="title" line, but that is not the <title> element. Google and other search engines use the real <title> element for the headline in search results and browser tabs. You need to add <title>Your Page Title</title> to your document head yourself.

Why did my typed quotes turn into "?

The server HTML-escapes your input before it runs the quote removal step. That means the quote character you typed becomes the six-character entity ", and the removal step finds nothing to remove. The output is valid HTML and browsers will render it correctly, but the raw source shows the entity rather than the character.

Which of the generated lines should I keep?

Keep the description and robots lines, because Google still reads both. Keep the charset line, though you can shorten it to the modern <meta charset="utf-8"> form. The keywords, revisit-after, language, and meta title lines are ignored by major search engines and can be deleted. The author line is optional.

Does the tool create Open Graph or Twitter Card tags?

No. The output contains no social media tags of any kind. If you want preview cards to appear when your page is shared on Facebook, X, or LinkedIn, you need to add Open Graph tags yourself. The essential ones are og:title, og:description, og:image, and og:url.

What happens if my description contains a line break?

The server removes line breaks from the description and keywords and joins the lines together with no space between them. A description that reads "first line" and then "second line" on the next line will become "first linesecond line" in the output. Type your description as a single continuous line to avoid this.

Is there a limit on how many times I can use the tool?

There is no per-tool cap and no CAPTCHA. A site-wide throttle applies to every page on limitlessreferrals.info, and it blocks an address for the rest of the day if that address makes more than fifteen requests within a single second. Normal use of the form involves only a few requests, so the throttle will not affect you.