Schema Markup Validator

Validate JSON-LD structured data offline. Paste JSON-LD or page HTML, check JSON syntax, @context, @type, URLs and required or recommended properties for Article, Product, Organization, LocalBusiness, WebSite, FAQPage, BreadcrumbList and Recipe, with exact JSON paths.

Web & SEO Runs client-side Free to use

Jump to the tool

About the Schema Markup Validator

Schema Markup Validator checks JSON-LD structured data in your browser. Paste JSON-LD directly, or paste a page’s HTML and the tool extracts every <script type="application/ld+json"> block from it safely, without running any script. It accepts a single object, an array of objects or a @graph.

Results are split into three parts so they are not confused: JSON syntax validity, local structural checks (@context, @type, basic URL, date, duration and price formats, and required and recommended properties for common types such as Article, BlogPosting, Product, Organization, LocalBusiness, WebSite, FAQPage, BreadcrumbList and Recipe), and a separate note about Google rich-result eligibility. Each message includes the JSON path, such as $["@graph"][1].offers. The tool does not cover every schema.org type or every search-engine rule, and it cannot guarantee indexing, rich results, rankings or how a result looks.

How to use

Choose JSON-LD or HTML page as the input type.
Paste your markup (or insert the sample).
Click Validate.
Review the syntax result, structural errors, warnings and passes, and the eligibility notes.
Expand the parsed data tree to inspect values, then copy or download the report.

Key features

JSON syntax check with line and column for errors.
Supports objects, arrays and @graph, and multiple script blocks.
Required and recommended property checks for nine common types.
Checks Offer price and currency, ISO 8601 dates and durations, and URLs.
Accurate JSON paths for every error, warning and pass.
Safely escaped, collapsible parsed tree.
Copy Report, Download Report, Reset and Back.

Best practices

Mark up only content that is visible on the page.
Use "@context": "https://schema.org" and a specific @type.
Use absolute https:// URLs for url, image, logo and item values.
Fix every error first, then add the recommended properties that fit your content.
Confirm eligibility with the search engine’s own testing tools before relying on a rich result.

Benefits

Finds syntax and structure problems quickly.
Keeps syntax, structure and eligibility clearly separate.
Works with unpublished markup because nothing is fetched.
Private: nothing is uploaded or stored.

Frequently asked questions

Does a pass here mean I will get a rich result?

No. A pass means the markup is valid JSON and has the properties this tool checks. Search engines apply their own checks, content policies and quality systems, so rich results, indexing and appearance can never be guaranteed.

Can I paste a whole HTML page?

Yes. Choose HTML page and the tool extracts the JSON-LD script blocks using the browser’s inert HTML parser. Other scripts in the page are ignored and never run.

What does a JSON path like $["@graph"][1].offers mean?

It shows exactly where the issue is: $ is the top of the JSON, ["@graph"] is the @graph property, [1] is its second item and .offers is the offers property of that item. With several script blocks, $1, $2 and so on identify the block.

Which schema types are checked?

Article, NewsArticle, BlogPosting, Product, Organization, LocalBusiness and common subtypes, WebSite, FAQPage, BreadcrumbList and Recipe. Other types still get syntax, @context, @type and URL checks.

Does it support Microdata or RDFa?

No. It validates JSON-LD only, which is the format most search engines recommend.

Why does it mention FAQ rich results are limited?

Google shows FAQ rich results only for a small set of authoritative sites, so valid FAQPage markup usually will not produce one. The note is there so you are not surprised.

Is my content uploaded or saved?

No. Everything runs in your browser. What you paste or type is not sent anywhere, no URL is fetched, and nothing is saved in browser storage. Reset clears it from the page.