A complete basic HTML head block for any website contains exactly five elements in this order: a UTF-8 charset declaration, a responsive viewport meta tag, the page title element, the meta description, and an optional author tag. That is the smallest auditable set of metadata every HTML document should ship, and the Meta Tag Generator produces exactly this block — escaped, trimmed, and ready to paste into a single document head. The tool runs entirely in your browser, so the page title, description, and author you type never leave the device, which matters when you are drafting for a site that has not launched yet or when confidentiality around draft titles is a real concern. Everything else — canonical links, Open Graph properties, robots directives, Twitter Cards — is intentionally left out so that the basic block stays small, reviewable, and free of contradictory markup. Each line is HTML-escaped in its attribute context, and the UTF-8 declaration is emitted before any textual metadata so the parser can decode the title and description correctly.
What a Clean Basic Head Block Actually Contains
The HTML specification defines a head element as the container for machine-readable information about the document, and the standards-backed fixtures the generator follows come directly from the WHATWG HTML semantics. In practice, a clean basic head block holds five concerns: character encoding, layout viewport, document name, page summary, and optional authorship. Each of these answers a different question that browsers, assistive technologies, and search systems ask before showing the page. Combining all five with canonical, Open Graph, and robots directives in one generic form is how contradictory metadata ends up live on a site, which is why the tool keeps the basic set deliberately narrow.
The order matters as much as the content. The UTF-8 declaration has to come before any textual metadata so that parsers can decode the title and description correctly. The viewport tag follows, then the title element, then the description, then the optional author. That fixed order is what makes the output auditable — when you read the served source, you can predict where each concern sits and spot any duplicate a theme or plugin tries to add.
What the Meta Tag Generator Covers — and What It Leaves Out
The Meta Tag Generator produces a UTF-8 charset declaration, a responsive viewport meta tag set to width=device-width, initial-scale=1, the title element, the meta description, and an optional author meta tag. It does not produce canonical links, robots directives, Open Graph properties, Twitter Card markup, structured data, or hreflang alternates. Each of those excluded items encodes a separate page decision, and a clean basic head block without SEO bloat is the entire point of keeping the scope narrow. The viewport content is fixed on purpose: maximum-scale or user-scalable restrictions are not emitted because they harm accessibility, and responsive behavior still depends on CSS and media queries working on the page.
| Field | Required | Character limit | HTML treatment |
|---|---|---|---|
| Document title | Yes | 200 | Trimmed, escaped, control characters rejected |
| Page description | Yes | 500 | Trimmed, escaped, control characters rejected |
| Author name | No | 120 | Trimmed, escaped; line omitted entirely when blank |
Ampersands and angle brackets are encoded for every field, and quotes are encoded where they could break out of an attribute. A title such as "Q&A: Basics" reaches the page as a correctly escaped value rather than malformed HTML.
| Included by the generator | Excluded — handled by dedicated tools |
|---|---|
| UTF-8 charset declaration | Canonical link element |
| Responsive viewport meta | Robots meta and X-Robots-Tag header |
| Title element | Open Graph properties |
| Meta description | Twitter Card meta tags |
| Optional author meta | JSON-LD structured data and hreflang alternates |
Generate a Basic Meta Tag Block for Your Website
Use this sequence when you have an HTML page ready and want to populate its basic head block without hand-writing escape sequences or guessing length limits.
- Open the Meta Tag Generator and enter one accurate document title in the title field — the same string you want browsers to show in the tab and bookmarks — kept under 200 characters after trimming.
- Type a concise page description in the description field that summarizes what a visitor actually receives when they land on the page, kept under 500 characters and free of keyword lists or duplicate cross-page text.
- Add an optional author name only if the site maintains one — a maintained byline or organization name — under 120 characters; leave the field empty when there is no meaningful value to record.
- Generate the block and review the preview for character encoding, viewport content, and the order of the lines before you copy anything.
- Copy the escaped block from the output panel; do not retype it manually, because manual copying risks losing the entity-encoded ampersands and angle brackets.
- Paste the lines inside the document head of your HTML page, not into the body, and not into a visual editor that escapes the markup a second time.
- Inspect the delivered source in your browser, remove any duplicate title, description, or author metadata added by a theme, plugin, SEO framework, or deployment platform, then recheck that the document still has exactly one title element.
Processing happens client-side, so the values you typed stay on your machine and nothing is uploaded to Lizely. That matters when you are drafting a site that has not launched yet, or when an unpublished title and description are commercially sensitive.
Paste the Block and Inspect the Delivered Source
Generating the markup is the easy half. The harder half is verifying that what you pasted is what actually reaches a visitor, because themes, plugins, page builders, and deployment platforms frequently inject their own title, description, or author metadata on top of yours. A page that ships with two title elements or two meta descriptions behaves unpredictably: browsers usually pick the first, search systems may pick any of them, and validators flag the duplicates. After you paste the block, view the raw public source of the page and confirm one of each — one title element, one meta description, and at most one author meta tag.
Check the HTTP response headers too. If the server advertises a different character encoding than the UTF-8 declaration in your head, parsers resolve the conflict using the header, which can scramble titles and descriptions with non-ASCII characters. The generator cannot inspect your server headers, so this check stays with you. Google publishes title link guidance explaining how search systems can rewrite a title even when the source markup is correct, which is why a valid block may produce a different visible title in the search results.
Limits, Conflicts, and Decisions the Tool Will Not Make for You
The title element is limited to 200 characters and the description to 500, but those are syntax bounds, not ranking targets — there is no SEO claim attached to filling them. According to Google's title link documentation, search systems are free to select different visible text from the page, and what you write in the meta description is a hint that engines can ignore. If you need a title that exceeds 200 characters, shorten it; if the page genuinely needs more than 500 characters of summary, split the page or write a tighter description.
The author field is metadata about authorship, not a verified identity, not a copyright statement, and not a replacement for a rel=author link or structured data. For articles, people, and organizations, you still need accurate visible bylines on the page and the right structured data in JSON-LD or Microdata. The generator does not measure keyword quality, pixel width, click-through rate, or search demand. Those are content and product decisions, not syntax validation. It also does not fetch the page, update a CMS, or publish changes — keep metadata aligned with what visitors actually receive, then use a search-console inspection tool after recrawling to see what was picked up.