A webpage is not always broken because of a large mistake. Small details can produce exactly this problem: debugging: metadata outside the document head. This guide shows you what to look for, a concrete fix, and how to check that it worked.
The Idea in Plain English
Most document metadata belongs in head, not among the visible contents of body.
You can test this using a small local HTML file. Change one part at a time and check the result in the browser before adding more code.
A Working Example
The first part shows a problem. The second part shows a safer or more accurate version. Compare them before reading the explanation.
<!-- Problem -->
<body><meta name="description" content="My article"></body>
<!-- Corrected example -->
<head>
<meta charset="utf-8">
<meta name="description" content="My article">
<title>Article</title>
</head>What Each Part Does
- The meta element supplies machine-readable settings; its name or charset decides which setting.
- The title gives the document a name in tabs and other browser surfaces.
- The body contains the material a visitor normally sees.
- name identifies a field in submitted form data or a named metadata entry.
- content supplies the value of a meta declaration.
- charset identifies the character encoding used by the document.
Before the fix, the browser can behave incorrectly or report a warning. After the change, test the exact failure rather than assuming the page is fixed.
Try It Yourself
Inspect head in the DOM and run a validator to check placement.
Common Beginner Mistakes
- Check the underlying cause before changing unrelated tags.
- Changing several parts of the example at once, making it difficult to see which part caused a different result.
- Choosing a tag only because its default appearance looks right, without checking whether it describes the content correctly.
Key Takeaways
- Most document metadata belongs in head, not among the visible contents of body.
- Before the fix, the browser can behave incorrectly or report a warning. After the change, test the exact failure rather than assuming the page is fixed.
- Test the markup in a browser, and check accessibility and real-world behavior where relevant.