What is the best JSON-LD testing tool?

No single tool is best, so use two. Google's Rich Results Test shows whether your JSON-LD can qualify for Google's rich results and lists errors that block them. The Schema Markup Validator at validator.schema.org checks any schema.org markup for syntax and vocabulary mistakes. Run the Rich Results Test first for Google, then the validator for everything else.

Why it matters

JSON-LD is a block of data inside your page that describes it to search engines. One missing comma can make the whole block unreadable, and the page itself will look fine. A test catches it before search engines do.

How to check

Open the Rich Results Test at search.google.com/test/rich-results.
Choose the URL tab and enter the live page address, or choose the code tab and paste your JSON-LD to test it before publishing.
Read the detected items. Each one is a type Google understands, such as Article or Product, with a count of errors and warnings.
Fix every error first. Errors mean the item is not eligible for the rich result. Warnings mark optional properties and do not block it.
Open validator.schema.org and test the same page or snippet. This tool checks the schema.org vocabulary itself, including types Google does not turn into rich results.
Test again after each change.

A minimal block that should pass both tools looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Co",
  "url": "https://www.example.com/"
}
</script>

Google Search Console's Enhancements reports show markup problems across the whole site, not only on one tested page.

Common mistakes

Testing only in one tool and assuming the other agrees. Their jobs differ.
Reading a passing result as a promise of a rich result. A pass shows eligibility, not that Google will display anything.
Pasting code with curly quotation marks copied from a word processor. JSON needs straight quotes.
Marking up details that are not visible on the page. Markup should describe what visitors can actually see.
Leaving a trailing comma after the last property, which breaks the block.

Crawvix's scan checks that structured data on your pages is valid, so a broken block is reported alongside your other launch checks.

Frequently asked questions

Is the old Structured Data Testing Tool still available?

Google retired it in 2021. Its general-purpose role moved to the Schema Markup Validator, and its Google-specific role moved to the Rich Results Test.

Can I test JSON-LD before the page is live?

Yes. Use the code tab in the Rich Results Test, or paste the snippet into the Schema Markup Validator. Neither needs a public URL.

Why does the tool find no items on my page?

The markup may be missing, injected by JavaScript the tool could not run, or written with a type Google does not support for rich results. View the page source to confirm the block is there.

Want to see how your own pages look? Try the free website sample.