Generate HTML meta tags from a title and description

It enforces the widely used limits of 60 characters for the title and 160 characters for the description before producing any output. Special HTML characters are escaped safely, duplicate keywords are removed, and the returned block is ready for a template, static page, content management system, or automated publishing workflow.

Write a focused title and useful description

Begin with the specific page that will receive the markup. The title should identify its subject and, when useful, the site or organization behind it. Keep the most meaningful words near the beginning because search interfaces and browser tabs have limited space. This generator accepts a non-empty title of no more than 60 characters. The description should summarize what a visitor can expect after opening the page, using concrete language instead of a list of disconnected phrases. It must be non-empty and no longer than 160 characters. Both limits count Unicode characters rather than raw storage bytes, so ordinary accented letters and non-Latin characters are handled as visible characters. Leading and trailing whitespace is removed before validation and counting. If either value exceeds its limit, the request returns an input error and produces no partial markup. That strict behavior is useful in editorial systems because an invalid draft cannot quietly reach a publishing template with text that is likely to be truncated.

Add keywords only when your workflow requires them

Keywords are optional and are supplied as a list, with one phrase per item. When at least one keyword is present, the generator trims every item, rejects empty entries, removes duplicates without changing the order of the first occurrence, and joins the remaining phrases with commas. Duplicate matching ignores letter case, so Coffee and coffee are treated as the same keyword while the spelling of the first entry is preserved in the result. Up to 50 items may be submitted, which keeps input and output bounded for browser and API use. The keywords tag is not required for a complete title-and-description block, and many modern search engines do not use it as a ranking signal. It can still be useful for an internal search index, an older content system, a controlled publishing specification, or a downstream parser that expects the field. If your project has no such requirement, omit the list; the output then omits the keywords tag and the optional structured keywords field instead of returning empty placeholders.

Place the generated block and verify the page

The response provides the complete markup as html and also returns the same elements as a tags array for build tools that prefer individual lines. Place the block inside the document head, with only one title element and one description meta element for the page. A server-rendered application should normally add it in the route metadata or shared head component, while a static site generator can insert it during the page build. The result safely escapes ampersands, angle brackets, quotation marks, and apostrophes, preventing supplied text from breaking out of its HTML context. It does not fetch the destination page, choose marketing language, measure rendered pixel width, or add social sharing tags such as Open Graph and Twitter Card properties. After publishing, inspect the delivered page source rather than only the visual editor, confirm that no theme or plugin emitted competing tags, and test the final URL with the webmaster tools relevant to your search provider. Search services may rewrite displayed snippets, so valid source markup is a clear instruction rather than a guarantee of exact presentation.