← Back to SEO LearnNOTABIS SEO / LEARN

Structured data · 16 September 2026

Microdata: What It Is and How to Validate It

NOTABIS records microdata-present when measured HTML contains an itemscope element. The check confirms presence only; it does not validate schema vocabulary, properties, or rich-result eligibility.

Quick answer

Microdata embeds structured information in HTML attributes such as itemscope, itemtype, and itemprop. NOTABIS records microdata-present when it measures one or more elements with itemscope. Presence only confirms that the format exists; it does not validate the vocabulary, values, or eligibility for a search feature.

What the issue means

A simple Microdata item looks like this:

<div itemscope itemtype="https://schema.org/Product">
  <span itemprop="name">Example trail shoe</span>
</div>

The attributes connect visible page content to a vocabulary. Microdata is one structured-data format; JSON-LD and RDFa can express similar information through different markup.

Why it matters for SEO

Accurate structured data can help a search engine understand entities and may support a supported feature when all requirements are met. It is not a ranking guarantee, and an attribute count does not prove valid or useful markup. The values should match the visible page and the page’s purpose.

How NOTABIS detects it

The microdata-present rule is a page-level passed check created when the measured DOM contains at least one [itemscope] element. NOTABIS does not validate itemtype, nested properties, required fields, vocabulary URLs, or search-feature policies. A page without Microdata is not an error; it simply has no pass record for this format.

How to check it yourself

Inspect the DOM and View Source for itemscope, itemtype, and itemprop. Trace each property to visible content, then validate the intended schema type with a feature-specific testing tool. Check that the item is not duplicated, hidden, or contradicted by another structured-data format.

How to fix it

Use a supported vocabulary, keep properties accurate, and generate attributes from the same content source as the visible page. Remove stale or misleading Microdata rather than adding fields solely to satisfy a validator. If JSON-LD is easier to maintain, migrate deliberately and remove duplicate representations after testing.

When this is intentional or does not need fixing

A site may use JSON-LD, RDFa, or no structured data at all. Microdata is optional, and a page without it can still be fully indexable. Keep markup only when it describes visible, current content and supports a real consumer.

Related issues

Compare valid JSON-LD, invalid JSON-LD, and RDFa. Google’s structured-data policies apply regardless of the syntax you choose.

Run a NOTABIS audit

NOTABIS confirms when Microdata is present in measured HTML and leaves vocabulary and feature eligibility for independent structured-data validation.

Measure before you change

See which issues affect your site.
Run a NOTABIS audit ↗