Creating meta tags for your website means producing a small, well-formed set of HTML head tags — a UTF-8 character encoding declaration, a responsive viewport tag, a title element, a description meta tag and an optional author name — that describe the document to browsers, assistive tools and crawlers. The minimum required elements are just three: a charset declaration, a viewport meta tag and a title. A description and an author line are added only when there is a meaningful, accurate value to publish. These tags live inside the HTML head element, above any visible body content, and they are read on every page load. They are deliberately separate from canonical links, robots directives, Open Graph properties and Twitter Cards, which carry indexing and social-sharing decisions that need their own dedicated blocks. A clean, escaped basic head block is the correct starting point for any website, and it should be written, audited and inserted before specialized tags are layered on top.
The five tags that belong in a basic head block
A minimal head block for a new website is built from five elements, all of which the WHATWG HTML standard defines as document-level metadata. The first is a character encoding declaration, written as <meta charset="utf-8">, which tells the browser how to interpret every byte that follows. UTF-8 covers the full Unicode range and is the only encoding most modern websites should publish. The second is a responsive viewport tag, written as <meta name="viewport" content="width=device-width, initial-scale=1">, which makes the layout viewport follow the device width without disabling user zoom. Removing or altering this tag is one of the most common reasons pages render incorrectly on phones.
The third is the <title> element, which per the WHATWG HTML semantics specification represents the document's title or name. Browsers display it in tabs, bookmarks, history lists and other interface surfaces. Search systems may also use it as one input when they build a result link, but they are free to choose other visible text instead. The fourth is a description meta tag, written as <meta name="description" content="...">, which provides a short summary of the page for any consumer that wants one. The fifth is an optional author meta tag, written as <meta name="author" content="...">, which describes authorship metadata only when the site maintains a meaningful name to publish.
These five elements share one important property: they all describe the document itself, not its indexing policy, social-share appearance or canonical address. That distinction is what makes the basic block a sensible foundation before any specialized tags are added.
Why keeping the block small is the safer default
Many online meta tag generators ask for canonical URLs, robots directives, Open Graph properties, Twitter Card fields and a dozen other inputs in one long form. That looks thorough, but it encourages a specific failure mode: the same page cannot have a canonical URL, a robots rule and a social description decided by a single dropdown. Each one is a separate page-level decision with its own tool. When every vocabulary is mixed into one block, it becomes easy to copy contradictory or irrelevant markup and harder to audit the result line by line.
A tool that produces only the five foundational tags is narrow on purpose. The Meta Tag Generator handles only the basic document metadata that can be reviewed together: charset, viewport, title, description and optional author. Canonical links, robots meta tags, Open Graph properties and Twitter Cards each express separate page decisions, so they are deliberately excluded and have dedicated tools. Running the title and description through a minimal, browser-based generator first gives you an auditable starting block, and the same minimalist logic is the basis of the guide on getting a meta tag block without the SEO bloat. Specialized tags can then be added by their own generators once the foundational layer is confirmed.
The processing also stays in your browser. The tool does not send the title, description or author to any server, which matters when the metadata includes draft copy, internal product names or information that has not been published yet. You can iterate locally, paste the result into your CMS, and only after that point does the metadata travel anywhere on the public web.
How to create basic meta tags for your website
The exact steps to produce a clean basic head block with the Meta Tag Generator are short and reviewable. They map directly to the way the tool was designed to be used.
- Enter one accurate document title, a concise page description and an optional maintained author name. Write the title in the same human voice as the visible page heading, not as a keyword string. The description should distinguish the page from sibling pages in two or three sentences and avoid lists of keywords, duplicate descriptions across unrelated pages or promises the page does not fulfil. Leave the author field empty unless you maintain a meaningful byline for the document, because an invented or stale author name adds noise without adding value.
- Generate and copy the escaped basic head block without adding duplicate specialized metadata. The generator trims each value, enforces the length limits, rejects control characters and escapes ampersands, angle brackets and attribute quotes for the right HTML context. The copied block contains exactly five lines: a UTF-8 declaration, a viewport tag, a title element, a description meta tag, and an author meta tag when one was supplied.
- Insert it inside the document head, inspect the delivered source and remove conflicts added by themes, plugins or frameworks. Place the block high in the head element, immediately after any structural tags the CMS requires. View the page source after publishing and confirm there is only one <title> element and only one description meta tag. If a theme, plugin, SEO plugin or deployment platform has injected a duplicate, remove the older one.
That is the entire workflow for the basic block. Any canonical, robots, Open Graph or Twitter Card tag you need is added separately afterward, using the dedicated tool for that vocabulary.
What the Meta Tag Generator handles and what it omits
| Tag | Status in the basic block | Why |
|---|---|---|
| UTF-8 charset | Included | Defines how the browser reads every byte that follows. |
| Responsive viewport | Included (fixed value) | Matches the device width without disabling zoom. |
| Document title | Included | Required by the HTML standard; shown in tabs and used as one search input. |
| Page description | Included | Optional by spec, but commonly consumed as a page summary. |
| Author metadata | Optional | Included only when an accurate, maintained value is supplied. |
| Canonical link | Omitted | Carries a separate indexing decision; has its own generator. |
| Robots meta tag | Omitted | Combines indexing and snippet controls; has its own generator. |
| Open Graph properties | Omitted | Drives social-share appearance; has its own generator. |
| Twitter Card tags | Omitted | Drives X/Twitter share appearance; covered by the social-tag tool. |
Three length limits govern what the generator accepts. Any value longer than the cap is rejected before the block is generated, so there is no risk of an oversized title or description slipping through.
| Field | Maximum length | Required |
|---|---|---|
| Title | 200 characters | Yes |
| Description | 500 characters | Yes |
| Author | 120 characters | No |
These maxima exist to keep output bounded; they are not ranking targets. Practical title and description lengths for search snippets are usually well below these caps, and a search engine can rewrite either value before display. The Google title link documentation describes how the search system may replace, abbreviate or omit your title based on the query and on the page itself.
Deploying the block and removing duplicates from your CMS
Once you have the basic block copied, paste it inside the <head> element of the page, near the top. Every text value in the block is already escaped for its HTML context, so you do not need to re-edit ampersands, angle brackets or quote characters. Do not paste the lines as visible body text, and do not paste them into an editor that will re-escape the markup a second time — either action will break the output.
The next step is conflict detection, which is the part most teams skip. Open the rendered source of the live page in your browser, search for <title> and confirm there is exactly one match. Search for name="description" and confirm there is exactly one match. If your CMS, theme or SEO plugin has already inserted a title or description, the new block will sit alongside the old one and search systems may choose either at random. Remove the older entry — usually by editing the theme's header template or by disabling the conflicting plugin — and keep only the generator output.
Two specific gotchas deserve attention. First, some deployment platforms prepend a global title suffix in the theme, which produces a duplicate rather than a replacement. Disable that suffix or rewrite the template to use your generated title as the source of truth. Second, several SEO plugins store a default description that activates whenever a per-page description is empty, so a previously empty field may suddenly have a value after you save. Re-check the source after every plugin update.
Verifying your published metadata after launch
The generator produces valid syntax, not a ranking outcome. Once the block is deployed, three post-launch checks confirm that the metadata is reaching the public page the way you intended.
- Inspect the raw source. View the page source from a fresh browser session, not from a logged-in preview, and read the head element line by line. The UTF-8 declaration must appear before any textual content, the viewport tag must use the fixed responsive value, and the title and description must each appear exactly once.
- Check the HTTP response. Use your browser's developer tools, curl, or a header-inspection service to confirm that the server does not declare a conflicting character encoding in its Content-Type header. A conflicting header will override the meta charset and is invisible from the source alone.
- View the page at mobile width. Resize the browser to a phone width or open the page on an actual phone. Confirm that the layout responds to the device width and that user zoom is not disabled. The generator does not add maximum-scale or user-scalable restrictions because those can harm accessibility, so the published viewport should still allow pinch-to-zoom.
After the page has been recrawled, run the URL through your search engine's inspection tools to see which title and description the crawler actually indexed. Those tools sometimes surface a snippet that does not match your source, which is a useful signal that the search engine has chosen to rewrite your metadata based on the visible page content. When that happens, the fix is almost always to align the visible content with the metadata, not to edit the head block again.