Schema Validator

Three separate layers, reported separately. First, strict JSON syntax: real JSON rules with line and column numbers, unescaped control characters rejected, and duplicate keys flagged. Second, a typed pass over your JSON-LD: text fields must actually be text, dates must be real calendar dates, currencies must be active ISO 4217 codes; a nested object can never satisfy a field that requires a string. Third, DevDome-maintained Google feature profiles, each stamped with a version date and a link to the official documentation it was written from.

No, and it does not pretend to be. Google's tool is authoritative for Google features and renders JavaScript; this tool validates your markup locally against dated profiles and tells you to confirm in the Rich Results Test before relying on the result. A local pass is a strong signal your markup is well-formed and complete, never a guarantee Google will show anything.

Because it is true and most validators have not caught up. Google stopped showing FAQ rich results on May 7, 2026, after limiting them to government and health sites in 2023, and removed the documentation the following month. Tools that still report FAQPage as an eligible rich result are reporting a feature that no longer exists. Your FAQPage markup is still valid Schema.org vocabulary and this tool validates it as such, clearly labeled retired for Google.

The profiles checked here as of the current profile version: Article, Product snippets (name plus at least one of review, aggregateRating or offers), Breadcrumbs, Organization, Local business, and Event. Others exist (Recipe, Job posting, Video and more) and can be validated as vocabulary here; each profile in the results links the exact official documentation page with the date we last reviewed it.

No, and validators that hard-require both create false alarms. Google's current product snippet documentation requires a name plus at least one of review, aggregateRating or offers; an image is recommended, not required, for the snippet. Merchant listing experiences, which put products in shopping surfaces, have stricter requirements including price and availability. This tool checks the snippet profile and says so explicitly.

The initial HTML response of the page, fetched server-side with strict security limits, from which JSON-LD script blocks are extracted. It does not execute JavaScript, so structured data injected by scripts or tag managers will not appear; Google does render JavaScript. If your markup is JS-injected, paste the rendered output instead, or use Google's Rich Results Test which renders the page.

Because JSON parsers silently keep only the last value when a key repeats, and different consumers may disagree about which one wins. A duplicated "name" or "offers" key usually means a template merged two versions of the markup, and the value you see winning in one tool may lose in another. It is legal JSON with an SEO hazard inside, which is exactly what a warning is for.

Not yet; this tool validates JSON-LD, which is also the format Google recommends. Microdata and RDFa markup on a fetched page is currently invisible to it, so a page could carry conflicting formats this tool does not see. If you maintain Microdata or RDFa, use the official Schema.org Markup Validator alongside this one.