Skip to content

Schema Markup Validator

Check JSON-LD for syntax errors and missing properties.

How to use the schema validator

Three steps, all in your browser.

  1. 1

    Paste your markup

    Paste a JSON-LD block or the HTML of a page that contains it.

  2. 2

    Fill in the details

    Describe what's on your page. The result updates as you type.

  3. 3

    Copy the result

    Copy what you need in one click. Nothing is saved or sent anywhere.

Schema Markup Validator: what to know

The schema validator checks JSON-LD structured data in your browser. Paste a JSON-LD block, or a whole page's HTML and it finds the application/ld+json script tags for you, and it reports JSON syntax errors with their position, a missing or wrong @context, missing @type, and common properties that are missing for well-known types.

Most broken structured data is broken JSON: a trailing comma after the last property, smart quotes pasted from a word processor, an unescaped quote inside a string, or a missing closing brace. Search engines skip a block that doesn't parse, so one stray comma can silently remove all of a page's markup. The validator points at the line where parsing stopped.

This is a syntax and basics check, not Google's eligibility check. It doesn't fetch your page, render JavaScript or know every Google policy. After the markup passes here, test the live URL with Google's Rich Results Test to see which rich results it's eligible for, and watch Search Console's enhancement reports for errors across the site.

Popular uses

  • Finding why structured data isn't detected
  • Checking hand-written JSON-LD before deploying
  • Reviewing markup output by plugins and templates
  • Auditing every JSON-LD block in a page's source

Tips for the best result

  • Paste the rendered HTML if your markup is added by JavaScript.
  • Fix syntax errors first; later warnings may disappear once the JSON parses.
  • Use https://schema.org as @context; http:// works too, but https is the current form.

Learn more

Read how JustYourSEO works and our privacy details. Text, HTML and images you use here are processed in your browser and are never sent to our server.

Frequently asked questions

No. This checks your JSON-LD in the browser: that it parses, has @context and @type, and includes the basic properties for common types. Only Google's Rich Results Test can say which rich results a live page is eligible for.

Usually a JSON syntax error: a trailing comma, a missing quote or brace, or smart quotes pasted from a document. The validator points at the line where parsing stopped.

No, only JSON-LD, the format Google recommends. If your site uses Microdata or RDFa, use Google's Rich Results Test or the Schema Markup Validator at schema.org.

No. The text, HTML, files and images you paste or open are processed on your device and are not sent to our server or stored. The five URL tools (SEO audit, indexability checker, redirect checker, HTTP header checker and broken link checker) are the exception: they send the URL you enter to our server, which requests that public page (and, for the broken link checker, each link on it) and returns what it received to your browser to check. The URL and the page aren't stored or logged. The optional Import from URL in the meta tag, Open Graph and Twitter card generators works the same way.

Yes. Every tool is free with no sign-up and no limits on use. Clearly labeled ads keep it that way.

They help you get the details right: tags that are complete and valid, previews that read well, files crawlers can parse. No tool can guarantee rankings; those depend on your content, your site and how search engines evaluate them.