HTML Checking for Large Sites
Rocket Validator automatically checks your pages on the W3C Validator.
The “itemprop” attribute was specified, but the element is not a property of any item.
An itemprop
attribute has been found in the document, but it cannot be associated to any item. Most probable cause is the lack of an itemscope
attribute defining an item.
Microdata allows nested groups of properties, which must be scoped to the item they belong to, as in this example:
<div itemscope>
<p>My name is <span itemprop="name">Liza</span> and I'm <span itemprop="age">48</span> years old.</p>
</div>
Related W3C validator issues
A <meta>
element without a content
, itemprop
or property
attributes has been found in an unexpected place.
Check its attributes and context - depending on the section of the document (<head>
or <body>
), the <meta>
element allows different attributes.
Learn more:
A <meta>
element without a itemprop
or property
attributes has been found in an unexpected place.
While the <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 itemprop
or property
, and a content
attribute, and it can’t have a http-equiv
or charset
attribute.
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>
Learn more:
Still checking your large sites one page at a time?
Save time using our automated web checker. Let our crawler check your web pages on the W3C Validator.