A trailing comma
JSON allows no comma after the last property. One stray comma and Search Console reports "Unparsable structured data" for the whole block.
JSON-LD · free · no signup
Schema markup validator
Validate schema markup from a URL or pasted code. See every type on the page, the properties rich results still need, and the facts that are in the markup but not on the page.
or paste the markup
What the validator checks
7 checks, in the order a problem costs you: markup that does not parse earns nothing, and markup that parses but is incomplete earns nothing either.
- Syntax. Every JSON-LD block parses. A broken one is shown with its line, its column and the mistake that usually causes it.
- Types. Which schema.org types the page declares, in JSON-LD or microdata.
- Rich result requirements. The properties Google needs for Article, NewsArticle, BlogPosting, Product, FAQPage and BreadcrumbList.
- Local business. A LocalBusiness block with a name, an address and a phone number.
- Markup against the page. The phone number and price in the markup also appear in the text, and match the page's tel: links.
- Identity. sameAs links, or links to the business's own social profiles.
The mistakes that break it most often
A Product without an offer
A product needs an offer with a price and currency, a review or a rating before Google shows any of it. A name alone earns nothing.
Facts only in the markup
A price or phone number that visitors cannot see goes against Google's guidelines, and AI assistants reading the page never see it at all.
An Article without a date
Headline, image and datePublished are the three an article needs. The date is the one templates most often leave out.
Questions about schema markup
How do I test schema markup?
Paste the JSON-LD block, or the page's whole HTML, into the box above, or enter the page's address. The validator checks that every block parses, that articles, products, FAQs and breadcrumbs have the properties rich results need, and that facts such as the phone number and price also appear on the page.
What does "unparsable structured data" mean?
Google found a JSON-LD block it could not read as JSON, usually because of a trailing comma, a missing comma between two properties, or a quote inside a value that is not escaped. The whole block is ignored, not only the broken line. The validator shows which block fails, on which line, and what the mistake usually is.
How is this different from the Schema.org validator and Google's Rich Results Test?
The Schema.org validator checks the markup against the whole vocabulary, and the Rich Results Test only shows the types Google turns into rich results. This validator sits between them: it names the properties rich results require for articles, products, FAQs and breadcrumbs, and it also compares the markup with the page, which neither of the other two does.
Does schema markup help with AI search?
Not measurably. A 2025 Ahrefs study of 1,885 pages found no effect of structured data on AI citations, and AI assistants that fetch a page live do not read JSON-LD. Add it for Google's rich results, and keep the facts visible in the page text for everything else.
Does it read microdata as well as JSON-LD?
It lists the microdata types it finds, but it checks properties in JSON-LD only. JSON-LD is the format Google recommends, and it is the one the checks above judge in full.