Meta tag generator
Generate ready-to-paste HTML meta tags: title, description, canonical, Open Graph and Twitter card.
Input
Result
Fill in the input and press Run.
Your input is processed in memory and then discarded. It is not stored or logged. Even so, don't paste live passwords or keys into any online tool.
Use it from code or an agent
curl -s https://setget.net/v1/tools/meta-tags-generate \
-H 'Content-Type: application/json' \
-d '{"input":{"title":"Tools & more","description":"Small web utilities.","url":"https://example.com/tools"}}'
import json, urllib.request
body = {'input': {'title': 'Tools & more', 'description': 'Small web utilities.', 'url': 'https://example.com/tools'}}
request = urllib.request.Request("https://setget.net/v1/tools/meta-tags-generate", json.dumps(body).encode(),
{"Content-Type": "application/json"})
print(json.load(urllib.request.urlopen(request))["result"])
const response = await fetch("https://setget.net/v1/tools/meta-tags-generate", {
method: "POST",
headers: {"Content-Type": "application/json"},
body: JSON.stringify({"input":{"title":"Tools & more","description":"Small web utilities.","url":"https://example.com/tools"}}),
});
console.log((await response.json()).result);
Tool: run_tool
Arguments:
{
"slug": "meta-tags-generate",
"input": {
"title": "Tools & more",
"description": "Small web utilities.",
"url": "https://example.com/tools"
}
}
{
"input": {
"title": "Tools & more",
"description": "Small web utilities.",
"url": "https://example.com/tools"
}
}
Endpoint: POST /v1/tools/meta-tags-generate. Over MCP: run_tool with slug: "meta-tags-generate".
Machine-readable: input schema, Markdown. Connect an agent.
Inputs
| Name | Type | Required | What it does |
|---|---|---|---|
title |
string | yes | The page title. |
description |
string | no | A one or two sentence summary of the page. |
url |
string | no | The canonical address of the page. |
image |
string | no | The address of the preview image (1200 x 630 pixels works well). |
site_name |
string | no | The name of the site. |
type |
string | no | The Open Graph type. One of: website, article, product, profile, book, video.other, music.song. Default: "website". |
twitter_card |
string | no | The Twitter card style. "auto" picks the large image card when there is an image. One of: auto, summary, summary_large_image. Default: "auto". |
twitter_site |
string | no | The @name of the site on X (Twitter). |
Example
Input
{
"title": "Tools & more",
"description": "Small web utilities.",
"url": "https://example.com/tools"
}Result
{
"text": "<title>Tools & more</title>\n<meta name=\"description\" content=\"Small web utilities.\">\n<link rel=\"canonical\" href=\"https://example.com/tools\">\n<meta property=\"og:type\" content=\"website\">\n<meta property=\"og:title\" content=\"Tools & more\">\n<meta property=\"og:description\" content=\"Small web utilities.\">\n<meta property=\"og:url\" content=\"https://example.com/tools\">\n<meta name=\"twitter:card\" content=\"summary\">\n<meta name=\"twitter:title\" content=\"Tools & more\">\n<meta name=\"twitter:description\" content=\"Small web utilities.\">",
"warnings": [
"There is no image. Link previews look much better with one."
]
}Questions
- Where do the tags go?
- Inside the head element of the page.
- Why the limits of 60 and 160 characters?
- Search results usually cut titles at about 60 characters and descriptions at about 160. Longer text still works but may be shortened.
- Must the image address be absolute?
- Yes. Preview generators do not resolve relative addresses, so start it with https://.
Related tools
- Open Graph and meta tag extractorPull the title, description, canonical link, Open Graph, Twitter card, favicons and JSON-LD out of HTML.
og-tags-extract - JSON-LD structured data checkerCheck JSON-LD structured data: valid JSON, @context, @type and the usual properties of common schema.org types.
jsonld-validate - HTML formatterRe-indent HTML so the nesting is easy to read, leaving pre, textarea, script and style content untouched.
html-format - .gitignore testerCheck which paths a .gitignore file ignores and which line decided each one, using real Git matching rules.
gitignore-test - Cache-Control explainerExplain a Cache-Control header directive by directive and how browsers and CDNs will treat the response.
cache-control-explain - Card number (Luhn) and IBAN validatorCheck a card number with the Luhn checksum and name its network, or check an IBAN by length and mod-97.
luhn-iban-validate