Schema markup validator
Enter a URL and we extract every JSON-LD and microdata item, check required and recommended fields, and hand you a corrected JSON-LD block.
How it works
- 1
We read the served HTML
We extract JSON-LD blocks (including @graph) and microdata exactly as a crawler receives them, without running JavaScript.
- 2
We check each type
Organization, WebSite, Product, Article, FAQPage, BreadcrumbList, LocalBusiness and SoftwareApplication are checked for required and recommended properties.
- 3
We build a corrected block
Missing properties are filled with clearly marked REPLACE placeholders so you can paste a complete block into your page.
Why it matters for AI search
Structured data tells machines who you are and what a page is about without guessing. Organization markup with sameAs links helps AI systems tie your site to the right entity. Broken JSON-LD is ignored silently, so errors cost you without any warning.
Frequently asked questions
Is this the same as Google's Rich Results Test?
No. This is a markup check against the properties each type needs. It does not claim Google rich result eligibility, which only Google's own tool can confirm.
Why does it only see markup in the raw HTML?
Most AI crawlers do not run JavaScript. Markup injected by scripts after load is invisible to them, so we validate what the server actually sends.
What are the REPLACE placeholders?
They mark values we cannot know, like your logo URL. Replace each one with the real value before publishing.
Does FAQPage markup still matter?
Google limited FAQ rich results to a small set of sites, but the markup remains valid and gives AI systems clean question and answer pairs.
Where should JSON-LD go?
In a script tag of type application/ld+json in the head or body of the page, rendered on the server.