Free Schema Markup Validator

How this tool computes its result

Parses pasted JSON-LD and runs a fixed set of shallow checks: warns if @context is missing, not a string, or not an http(s) URL; warns if @type is missing, and separately warns if @type is present but outside an 11-item whitelist (Organization, LocalBusiness, WebSite, Article, BlogPosting, FAQPage, Product, Review, BreadcrumbList, Person, Event). Only 3 of those types get deeper checks: Organization needs a name, Article/BlogPosting need headline and datePublished, and FAQPage.mainEntity must be an array where each item has @type "Question" and an acceptedAnswer. Two generic checks apply regardless of type: url must be a string, and an image value (string or ImageObject) should be an absolute URL.

Worked example

Pasting {"@type":"FAQPage","mainEntity":"Question"} -- mainEntity as a bare string instead of an array -- produces one error, "FAQPage mainEntity must be an array," which sets valid: false. Pasting the same object without @context only produces a warning (missing @context), which does not flip valid to false, since warnings and errors are tracked and reported separately.

When not to use this tool

Only 3 schema types (Organization, Article/BlogPosting, FAQPage) get any property-level validation; everything else on the whitelist -- WebSite, Product, Review, BreadcrumbList, Person, Event -- is accepted with just a generic "schema type" info note and no structural checks. This is not a substitute for testing actual rich-result eligibility in Google Search Console.

Common mistakes

• - Assuming a schema that passes here is guaranteed to earn rich results -- the checks confirm presence and rough type, not full Schema.org compliance or Google's specific rich-result requirements.
• - Pasting a Product or Event schema and expecting field-level warnings like the Article/FAQPage checks -- those types only get the generic @context/@type checks, no deeper validation exists for them in this tool.
• - Not noticing that a missing @context alone still reports "Schema is Valid!" -- @context absence is a warning, not an error, so the top-level valid/invalid banner can say Valid while warnings are still listed underneath.

Related tools