Schema.org Property Checker
Checks each property in your JSON-LD against the Schema.org vocabulary for the type it sits on. Misspelled, misplaced and superseded properties are flagged with a suggested fix.
Use the tool
Why this tool exists
A property that Schema.org does not define for a type is ignored by every consumer, so a typo such as adressLocality quietly removes data. This tool knows which properties belong to which type, including those inherited from parent types, and suggests the closest valid name.
It also catches properties that exist but are on a different type, like price on a Product instead of on its Offer, and properties marked as superseded by a newer one. It checks names and placement only. It does not judge the values, and it does not know what Google requires; the eligibility checker covers that.
How to use it
- Paste your JSON-LD or the HTML containing it.
- Read each finding with its path, for example $.address.adressLocality.
- Fix the name, or move the property into the type that defines it.
- Run again to confirm the list is empty.
Frequently asked questions
Does it check nested objects?
Yes, any nested object that has an @type is checked against that type. Nested objects without an @type are skipped because the tool cannot know what they are.
Why is a property called unknown when I see it on schema.org?
It may be in the pending or extension area, or newer than version 29.2, or it may be on another type. The message says where it is defined when it is in the vocabulary.
Are custom properties allowed?
Prefixed names such as ex:foo are listed as information and not checked.
Does passing mean Google will show a rich result?
No. Valid names are only the first step; use the eligibility checker for Google requirements.