Schema.org Validator

Inspect and validate data used by search engines and the semantic web.

The Schema.org vocabulary is widely used by search engines and data services to quickly understand key aspects of web sites. We carefully audit structured data embedded in web pages, including:

Property-specific Validators such as GTIN/ISBN checksums, Schema.org-specific syntax (e.g. opening hours specifications), traditional regular expressions, and controlled vocabularies matches.
Scope and Typo Checks to ensure properties are used within expected "thing" types and Schema.org terms are correctly spelled.
Optional Normalization to prefer structured types compared to plain strings (e.g. Action short-hands to PropertyValueSpecification; Country strings to things).

Usage

We automatically process Schema.org-related data, so there's nothing special you need to do to get started. Try it out using one of our tools below.

Playground – edit, validate, and visualize structured data using your browser.

Command Line – validate files and web pages, via the terminal, using the schemamarkup command.

Developer API – build your own solutions for publishing high-quality structured data.

Anonymous access is subject to usage limits. Refer to the pricing page for more details.

Messages

The following list represents the potential messages that may be produced during processing. Each link details common causes, recommendations, code examples, and technical properties that may be helpful when building custom integrations.

Unknown Term — e.g. schema:ExampleUnknown is not a defined term.
Unexpected Class — e.g. Vehicle class is not expected for an author property.
Unexpected Value — e.g. DateTime value is not valid for a Boolean property.
Unexpected Property — e.g. vehicleEngine property is not expected within an ImageObject node.
Actions: Unbound Constraint — e.g. query-input property is not valid within a CreativeWork node.
Actions: Invalid Textual Constraint Key — e.g. optional is not a valid short-hand key.
Roles: Unpropagated Property — e.g. OrganizationRole of a member must itself include a member.

We also do our best to resolve some properties against well-known vocabularies to detect potential typos and improper property usages. For example:

Country Codes — e.g. addressCountry resolves to a known country.
Currency Codes — e.g. priceCurrency resolves to a known currency.
Regional Codes — e.g. addressRegion is a known country-region reference.
Units of Measurement — e.g. unitCode is a standard UN/CEFACT code.

Resources

schema.org – the official website and documentation for the vocabulary.
Release 30.0 – the latest specification version we validate against.