What the Head Does
The head of an HTML page holds information that visitors rarely see but machines read first. Search engines take the title and description from it to build a result listing. Chat apps and social networks read Open Graph and Twitter card tags to draw the preview box when someone shares a link. Browsers read the character set, viewport and theme colour to decide how the page should look on a given device.
The generator on the companion page turns a set of fields into a finished, correctly escaped block. It shows the search snippet as you type, flags problems in plain words, and gives you the block as a copy or a downloadable file. It runs entirely in your browser, and it does not fetch any of the addresses you enter.
Control by Control
The form is divided into five groups. The notes below follow the order on the page and name each control as it appears there.
Page basics
Page title is the headline of the search result and the text on the browser tab. A counter beside the label shows the characters and an approximate pixel width, and a thin meter under the box fills as the title grows. Meta description is the grey summary under the headline, with a counter that reads against about 160 characters. Keywords and Author are optional. The keywords tag is ignored by the major search engines for ranking, so use it only if a tool of yours reads it.
Technical
Character set offers UTF-8 (the recommended choice), the legacy ISO-8859-1, or Omit. Language does not produce a meta tag at all. Instead, the output includes a comment reminding you to add the lang attribute to your html element. Viewport is pre-filled with the standard mobile value and should normally be left alone. Canonical URL must be a full address with its protocol, and the tool marks anything else. Theme colour pairs a colour swatch with a hex box; the two stay in step, and the colour tints the browser toolbar on supporting phones.
Robots directives
The Indexing switch chooses between index and noindex, and the Links switch chooses between follow and nofollow. Four checkboxes add noarchive, nosnippet, noimageindex and notranslate. max-snippet takes a whole number of characters, where -1 means no limit and 0 means no text snippet. max-image-preview offers Omit, none, standard and large. max-video-preview takes a whole number of seconds. A noindex setting shows an amber note in the summary, and noindex combined with a canonical address shows a second note, because the two signals can conflict.
Open Graph
The Open Graph group has two switches in its heading. Include turns the whole group on or off, and Inherit from basic fields copies the main title, description and canonical address into og:title, og:description and og:url. While inherit is on, those three boxes are locked. The remaining fields are og:type (website, article, product, profile, video.other or book), og:site_name, og:image and og:locale. The summary warns when no image address has been given, because a link without an image shows a bare card.
Twitter / X card
This group follows the same pattern. Include switches the group, and Inherit from Open Graph copies the title, description and image from the Open Graph fields. The twitter:card menu chooses between summary, which uses a small square image, and summary_large_image, which uses a wide one. twitter:site takes a handle; a leading @ is optional, and the tool adds one when it is missing.
Output and preview
The output area shows the finished block with its tags coloured by type. Copy places the block on the clipboard. head.html downloads the same text as a file. Example loads a built-in sample page for a leather goods shop, and Reset clears the form and the stored entries. The summary pills above the code count the tags and list anything that needs attention. Beneath the code, the search snippet preview shows roughly how the title, address and description will appear in a result.
Worked Example
Suppose you are building a page for a small candle maker. Enter these values and leave every other field at its default:
- Page title:
Handmade Candles | Lumen Studio(31 characters) - Meta description:
Hand-poured soy candles in six scents, made in small batches and shipped across India in recyclable boxes within two working days.(130 characters, so the counter reads "130 / 160 chars" with no warning) - Canonical URL:
https://www.example.com/candles/ - Open Graph image:
https://www.example.com/images/candles-1200x630.jpg, with og:site_name set to Lumen Studio - Twitter / X site:
lumenstudio
Because both Open Graph and Twitter groups inherit, the title, description and canonical address are copied across, and the image is shared with the Twitter card. The default values supply the remaining lines: a UTF-8 character set, the standard viewport, index and follow, a teal theme colour, the website type and the summary_large_image card. The generator then produces this block, with the comment headings it always writes:
<!-- Add lang="en" to your <html> tag --> <!-- Basic --> <meta charset="UTF-8"> <meta name="viewport" content="width=device-width, initial-scale=1"> <title>Handmade Candles | Lumen Studio</title> <meta name="description" content="Hand-poured soy candles in six scents, made in small batches and shipped across India in recyclable boxes within two working days."> <meta name="robots" content="index, follow"> <link rel="canonical" href="https://www.example.com/candles/"> <meta name="theme-color" content="#0f766e"> <!-- Open Graph (link previews on social and chat apps) --> <meta property="og:type" content="website"> <meta property="og:title" content="Handmade Candles | Lumen Studio"> <meta property="og:description" content="Hand-poured soy candles in six scents, made in small batches and shipped across India in recyclable boxes within two working days."> <meta property="og:url" content="https://www.example.com/candles/"> <meta property="og:image" content="https://www.example.com/images/candles-1200x630.jpg"> <meta property="og:site_name" content="Lumen Studio"> <!-- Twitter / X card --> <meta name="twitter:card" content="summary_large_image"> <meta name="twitter:site" content="@lumenstudio"> <meta name="twitter:title" content="Handmade Candles | Lumen Studio"> <meta name="twitter:description" content="Hand-poured soy candles in six scents, made in small batches and shipped across India in recyclable boxes within two working days."> <meta name="twitter:image" content="https://www.example.com/images/candles-1200x630.jpg">
The summary pill row reads "18 tags" and shows no warnings, because every field passes its check. Notice what the generator did for you: the handle gained its @, the description was not escaped because it contains no quotes or angle brackets, and the Open Graph and Twitter values were copied rather than typed twice. Had the description contained a double quote, the quote would have been written as " inside the attribute so the markup stayed intact.
Now change the canonical address to candles/. The canonical field turns red with the message to use a full address that starts with https:// or http://. Because Open Graph inherits the canonical address, the og:url box is filled with the same invalid value and turns red too, and both the canonical line and the og:url line disappear from the output. The tag count drops by two, to 16. The rest of the block is unchanged, so one mistake does not corrupt the others.
Tips and Common Mistakes
Frequently Asked Questions
There is no fixed character count. Search engines stop a title when it runs out of width in the result, so a title of 50 to 60 characters is a good target, but letter widths matter. The counter reports both characters and an approximate pixel width, and the bar turns amber or red as the title approaches the estimated limit.
No. For a search listing, the title, description, robots directives and canonical address are the important ones. Open Graph tags shape the preview card when a link is shared in chat or on social networks. Twitter and X card tags are optional, because many readers fall back to the Open Graph values when their own are missing.
Inside the head element of each page, normally near the top. Keep the charset line first, as the generator's own notes advise, and add the lang attribute to the html element using the comment the output provides.
No. It builds the block from what you type and never fetches your address, so it cannot confirm that an image loads or that a canonical address resolves. Open the address in a browser after publishing, and check the social platform's own preview tool to see how the card renders.