About the Schema Markup Validator
Broken structured data usually fails quietly: a stray comma stops a whole block from parsing, or a missing price makes a product ineligible for merchant listings. This schema markup validator checks JSON syntax, @context and @type, then compares each entity with the required and recommended properties for the Google features it can support. It also spots duplicate or conflicting entities, such as two Organization blocks with different logos, and draws the schema graph as a tree so you can see how items connect.
You can paste code or enter a URL; URL checks fetch public pages only. Treat errors as must-fix and recommended-property warnings as opportunities. A clean result means the markup is well formed and complete, but Google still decides whether to show a rich result, so confirm important pages in Search Console's enhancement reports.
How to use it
- Enter a public page URL or paste your JSON-LD code.
- Run the validation and fix any syntax errors first.
- Review missing required and recommended properties for each entity.
- Check the tree view for duplicate or conflicting entities, then re-test.
Frequently asked questions
How is this different from Google's Rich Results Test?
Google's Rich Results Test is the final word on whether Google can read your markup for its own features. This validator adds a quick second view: a tree of the whole schema graph, duplicate and conflicting entity checks, and plain explanations of missing properties. Use both when a page matters.
What is the difference between an error and a warning?
An error means the markup is broken or missing a property that a Google feature requires, so the page is not eligible for that feature. A warning flags a recommended property that is absent. Warnings do not block eligibility, but filling them in gives Google more complete information.
Why are duplicate schema entities a problem?
When a theme, a plugin and a manual snippet each add their own Organization or Product block, search engines see several versions of the same thing, sometimes with different names, prices or logos. That makes the data less trustworthy. Keep one authoritative block per entity and remove or merge the rest.