Rocket Validator automatically checks your pages on the W3C Validator.
HTML issues tagged as body.
<meta> element without a
property attributes has been found in an unexpected place.
<meta> element is commonly used within the
<head> section of the document, it can also be used within the
<body> section, for example in the context of defining microdata, as in this example:
<div itemprop="offers" itemscope itemtype="http://schema.org/Offer"> Price: $<span itemprop="price">1.00</span> <meta itemprop="priceCurrency" content="USD" /> </div>
When used within the
<body> section, the
<meta> element is required to have a
property, and a
content attribute, and it can’t have a
A common cause for this issue is including a
<meta> element that was intended for the
<head> section (for example one containing a
http-equiv attribute in the
<body> , for example:
<meta http-equiv="content-type" content="text/html; charset=UTF-8"> <form> ... </form>
</body> tag has been found, but there are unclosed elements before it. For example this has an unclosed
<body> <section> </body>
<meta> tags, used for defining metadata about HTML documents, must appear within the
<head>...</head> section, but it has been found out of place. Check the document structure to ensure there are no
<meta> tags outside the head section.
A common cause of this issue is having a duplicated, out of place
<head>...</head> section. Ensure that this section appears in its proper place and is the only container for
An end tag has been found after the closing
</body> tag, which breaks the expected HTML document structure.
Check out the document structure, a basic example follows:
<!DOCTYPE html> <html lang=""> <head> <title>Test</title> </head> <body> <p></p> </body> </html>
<body> tag has been found in an incorrect place. Check that it appears only once in the document, right after the closing
</head> tag, and that the whole document content is contained within
50,000 Accessibility and HTML checks per month. Fully automated.
Let our automated scanner check your large sites using Axe Core and W3C Validator.