What a complete meta tag block looks like
Fill in the seven fields on the left and the generator writes a block you can paste straight into the <head> of your page. With the page title, description, URL, OG image, site name, author, and Twitter handle filled in, the output looks like this, with one robots line added by hand because the tool does not emit one:
<title>My Awesome Product - Free Online Tool</title> <meta name="description" content="An amazing tool that solves your problem in seconds. Free, private, and browser-based."> <meta name="author" content="Jane Doe"> <link rel="canonical" href="https://example.com/"> <meta name="robots" content="index, follow"> <!-- Open Graph --> <meta property="og:type" content="website"> <meta property="og:title" content="My Awesome Product - Free Online Tool"> <meta property="og:description" content="An amazing tool that solves your problem in seconds. Free, private, and browser-based."> <meta property="og:url" content="https://example.com/"> <meta property="og:image" content="https://example.com/og.png"> <meta property="og:site_name" content="Example"> <!-- Twitter Card --> <meta name="twitter:card" content="summary_large_image"> <meta name="twitter:title" content="My Awesome Product - Free Online Tool"> <meta name="twitter:description" content="An amazing tool that solves your problem in seconds. Free, private, and browser-based."> <meta name="twitter:image" content="https://example.com/og.png"> <meta name="twitter:site" content="@example">
Every line has a different audience. The title is read by search engines, by the browser tab, and by anything that scrapes a page for a label. The description is offered to search engines as a candidate snippet. The canonical link says which address is the real one, and the robots tag says whether to index the page at all. The og: lines are read by Facebook, LinkedIn, Slack, Discord, WhatsApp, and most chat apps that unfurl links. The twitter: lines are read by X, which falls back to the og: values for anything it does not find.
How search engines actually use the title and description
The title tag carries real weight in ranking and it is the single line most people read before deciding whether to click. Write it so it reads as a sentence fragment a person would say, put the distinguishing words first, and keep the brand name at the end where it can be trimmed without losing meaning. Search engines rewrite titles too, usually when the tag is stuffed with keywords, repeats the site name on every page, or does not match what is on the page.
The meta description is not a ranking factor. Google has said for years that it does not use the description to decide where a page ranks. What it affects is click-through, and only when it is used at all: search engines rewrite a large share of descriptions, pulling a passage from the page body that matches the query more closely than your summary does. Write a good one anyway, because it is the version shown for brand and title queries and the text most other systems copy verbatim.
The keywords meta tag does nothing. Google announced in 2009 that it ignores meta keywords for ranking, and Bing has said the same. The generator does not produce one, which is correct.
Title and description length: pixels, not characters
Search results are truncated by pixel width, not by character count. Google renders the title in a fixed container, roughly 600 pixels wide on desktop, and cuts whatever does not fit. Sixty narrow characters such as lowercase i, l, and t can survive where fifty wide capitals are already clipped, and mobile uses a different container that often wraps instead of truncating.
That is why every character-count rule is an approximation rather than a limit. The practical guidance still holds: aim for under 60 to 70 characters in the title and 140 to 160 in the description, which is what the counters under the two fields track, and the tool caps the title at 70 and the description at 160 so you cannot drift past the useful range. Treat those numbers as a budget for the part you cannot afford to lose rather than a promise about what will display.
The safest habit is front-loading. Put the words that identify the page in the first forty characters of the title and the first hundred of the description, so that if the tail is cut, nothing important goes with it.
Which tags matter most when a link is shared
When someone pastes your URL into Slack, LinkedIn, iMessage, Discord, or X, none of that software reads your search result. It fetches the page, reads the Open Graph tags, and builds a card. The four that decide whether the card looks finished are og:title, og:description, og:image, and og:url. Miss og:image and most platforms fall back to the first usable image on the page, which is often a logo, an avatar, or nothing at all.
og:image is worth the most care. Use 1200 by 630 pixels, PNG or JPEG, under 8 MB, and always an absolute URL with the scheme included, because a relative path that works in your HTML will not resolve for an external scraper. The same applies to og:url, which should be the canonical address so that shares of tracking-parameter variants collapse to one entry.
The twitter:card value the generator writes is summary_large_image, which produces the wide card with the image above the text. The alternative is summary, a small square thumbnail beside the text. X reads twitter:title, twitter:description, and twitter:image when present and otherwise falls back to the og: equivalents, so the twitter: block is mainly there to let you write a different headline for that one platform. twitter:site names the account the card is attributed to.
Canonical and robots: the two tags that change what gets indexed
The canonical link is a hint to search engines about which URL is the real one when several addresses serve the same content. Query strings from campaigns, trailing slash variants, http and https pairs, and printable versions all create duplicates that split signals between addresses. Setting rel=canonical on all of them to one address consolidates those signals. The generator uses your page URL field for both the canonical link and og:url, so enter the clean address you want to be authoritative rather than the one currently in your address bar.
A canonical is advisory. Search engines weigh it alongside internal links, sitemaps, and redirects, and can pick a different URL if those disagree, so keep them consistent: link internally to the canonical address, list it in your sitemap, and redirect variants where you can.
The robots meta tag is the stronger instruction. index, follow is the default and does not need stating. noindex genuinely removes a page from results once the crawler sees it, which is what you want for thank-you pages, internal search results, and staging copies. The trap is combining noindex with a blocked path in robots.txt: if the crawler is not allowed to fetch the page, it never reads the noindex, and the URL can persist in results. Allow the crawl and let the tag do the work.
Checking the tags after you paste them in
Paste the block inside <head> and nothing else. Meta tags placed in the body are ignored or misread, and a stray tag after the first content element can end the head early. If your site is built with a framework that manages the head, feed these values into its own metadata API rather than hardcoding a second copy, because two title tags on one page leave the choice to the crawler.
Verify in two places. For search, read the rendered HTML of the live page rather than trusting your template, since frameworks sometimes strip or overwrite tags at build time. For social, use each platform debugging tool, which also clears the cached card; most platforms store a scraped card for days and keep showing the old preview after you fix the tag.
Then check uniqueness. Duplicate titles and descriptions are the most common failure in an otherwise correct setup, and usually come from a template that interpolates the site name but not the page name. Treat any two pages sharing a title as a bug.