Meta Tag Generator

Which tags are always written

A successful click always emits eleven lines, in a fixed order. The title element uses the trimmed page title. The description meta uses the trimmed description. The canonical link and og:url both use the canonical after new URL, then the same HTML escape as the other attributes. og:title and twitter:title repeat the title. og:description and twitter:description repeat the description. og:site_name uses the trimmed site name, or the word Website if that field is empty or only spaces. og:type is the literal website. twitter:card is the literal summary_large_image.

Two optional tails follow those eleven. A non-empty image URL is parsed as a URL and, if that parse works, adds og:image and twitter:image with the escaped absolute form. A non-empty Twitter handle adds twitter:site with the handle trimmed and escaped, and nothing is inserted in front of it. @toolbench stays @toolbench. toolbench without an @ stays without an @. The page does not look the handle up.

The six fields

Page title and Meta description are text controls. Canonical URL, Site name, Open Graph image URL, and Twitter handle are single-line controls. Only the first three block the click when they are empty after trimming. Site name is prefilled with toolbench.online. Clear it and the snippet still generates, with og:site_name set to Website. The image and the handle are skipped when their boxes are empty. They are not skipped when they contain spaces only: the handle is trimmed to empty and then skipped, and the image is trimmed to empty and skipped.

Generate meta tags is the only action. Editing a field after a success leaves the old snippet until you generate again. The status starts as Fill in the page details to generate metadata tags. Copy output copies the snippet, not the status. There is no Download output button on this tool. There is no preview card and no pixel measurement of the title or the description.

When this snippet is the right paste

Paste the lines into a head when you want this exact set: title, description, canonical, Open Graph title, description, url, site name, and type, plus the three Twitter lines. A slug for the path can be drafted on the slug generator. A campaign query on that canonical URL is the UTM builder. This generator does not add utm_ parameters, and the UTM builder does not emit meta tags.

A robots.txt rule is a different file. The robots.txt generator writes User-agent lines, not a robots meta tag. This page never emits a robots meta, a keywords meta, a viewport, or an hreflang. A sitemap urlset is the XML sitemap generator. The canonical you type here is not added to a sitemap for you.

Escapes, a bare origin, and missing fields

Escaping replaces & with &amp;, < with &lt;, > with &gt;, and " with &quot;, in the title, the description, the site name, the canonical, the image, and the handle. An apostrophe is left as an apostrophe. The title is text content of the title element, so the same four characters are escaped there too. The canonical is not the raw field. new URL parses it first, so https://example.com becomes https://example.com/ with a slash before it is escaped. A path such as https://toolbench.online/tools/meta-tag-generator does not gain an extra slash.

If the canonical is relative, or the image is relative, or either value is not a URL, the click fails with Canonical URL and image URL must be valid absolute URLs when provided. The snippet is cleared. That one sentence covers both fields. If title, description, or canonical is empty, the click fails earlier with Title, description, and canonical URL are required. and never reaches the URL parser. The page does not fetch the canonical, does not check that the image exists, and does not offer og:type values other than website.

Rules and limitations

Title, description, and an absolute canonical are required. The eleven core lines always include og:type website and twitter:card summary_large_image. An image adds og:image and twitter:image. A handle is copied as typed into twitter:site. An empty site name becomes Website.

& < > and double quotes are escaped. A bare origin gains a trailing slash. Relative URLs fail and clear the snippet. There is no download. There is no robots, keywords, viewport, or hreflang line.

Common problems

If https://example.com came back as https://example.com/, the URL parser added the slash. A path is left without an extra slash. Put the path in the field if the slash on the origin is wrong for that host.

If the snippet disappeared, a required field was empty or a URL did not parse. The previous lines are not kept. Fill the three required fields with absolute URLs and generate again.

Frequently asked questions

About this tool

Maintained by Toolbench. For large or deeply nested files, split the input into smaller batches and verify representative results before using them in an import or application. Report reproducible problems through Contact.