Free Schema Markup Validator

Paste a URL or code to check your JSON-LD structured data for errors and missing fields that could block rich results.

Enter a page URL

or

Structured data tells Google exactly what a page is about, a product, an article, a recipe, an FAQ, so it can show richer results in search: star ratings, breadcrumbs, prices, and more. A single missing field or a JSON syntax error is enough to make Google ignore the whole block, often with no visible warning on the page itself.

This validator fetches a live URL, or accepts pasted JSON-LD or HTML directly, and checks every <script type="application/ld+json"> block it finds. It confirms the JSON parses correctly, checks that @context and @type are present, and for the most common schema.org types, Article, Product, LocalBusiness, FAQPage, Review, Recipe, Event, JobPosting, and more, checks for the specific fields Google documents as required or recommended for rich results.

Run it after adding new structured data, after a theme or template change, or as a routine check alongside Google Search Console's own Rich Results report.

Frequently Asked Questions

Frequently Asked Questions (FAQs) is a list of common questions and answers provided to quickly address common concerns or inquiries.

Is this the same as Google's Rich Results Test?

No. Google's tool checks eligibility for specific rich result features and can change its rules without notice. This validator checks the underlying JSON-LD against schema.org's vocabulary and Google's documented field requirements for the most common types, useful as a fast first check before running Google's own tool.

Why does it say a type is not deeply validated?

Schema.org defines hundreds of types. This tool includes detailed field checks for the types most sites actually use. For anything else, it still confirms the JSON is valid and the type is present, and tells you to cross-check the field list on schema.org directly rather than guessing.

Can I validate structured data before publishing a page?

Yes. Paste the raw JSON-LD or full HTML into the code box instead of entering a URL, useful for staging environments or pages that are not live yet.

What does a missing @context warning mean?

Every JSON-LD block should declare "@context": "https://schema.org" so crawlers know which vocabulary the @type values belong to. Without it, some parsers may not recognize the data as schema.org markup at all.
Share on Social Media:
Popular Tools