Structured Data Validator: Check Schema Markup Before Google Does

Structured data describes a page in a vocabulary machines understand: this is a product, this is its price, this is the author, this is the shop’s address. Search engines use it to understand entities and, for some types, to show rich results such as prices, review stars, recipe details or event dates.

This schema markup validator extracts every JSON-LD, microdata and RDFa item on a page, lists the types it finds, catches JSON syntax errors and checks the properties Google requires or recommends for Article, Product, Organization, LocalBusiness, BreadcrumbList, Event, Recipe, VideoObject, JobPosting, Review and SoftwareApplication.

How to validate schema markup

1. Enter the page URL

   Use a live page that carries the markup you want to test, such as a product, article or event page.

2. Review the detected types

   Each JSON-LD, microdata or RDFa item is listed with its type and properties, plus any syntax error.

3. Fill the gaps

   Add missing required properties first, then the recommended ones, and run the check again.

Valid markup vs eligible markup

There are two levels of correctness for structured data. Syntax and vocabulary: the JSON parses, and the types and properties exist on schema.org, which is what the Schema Markup Validator checks. Search feature eligibility: the item has the properties Google requires for a rich result, as listed in Google’s structured data gallery.

A missing required property makes the item ineligible for its rich result. A missing recommended property keeps it eligible, with less information shown. Even eligible markup isn’t a guarantee: Google decides query by query whether to show rich results.

The JSON-LD errors we see most

• A trailing comma after the last property, or a missing comma between two.
• Curly “smart” quotes pasted from a word processor instead of straight quotes.
• An unescaped double quote inside a value, such as a size in inches; write \".
• A misspelled type: Organisation instead of Organization.
• A price with a currency symbol or thousands separator instead of a plain number plus priceCurrency.
• Dates that aren’t in ISO 8601 format; write them like 2026-10-30 or 2026-10-30T19:00:00+01:00.

A clean Product block with an offer looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Trail Running Shoe 2",
  "image": "https://www.example.com/img/trail-shoe-2.jpg",
  "offers": {
    "@type": "Offer",
    "price": "89.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}
</script>

More patterns are in our schema markup guide and the JSON-LD glossary entry.

Which rich results still exist in 2026

Google has trimmed the list over the years. HowTo rich results were removed in 2023, and FAQ rich results stopped appearing for all sites in May 2026. FAQPage and HowTo remain valid schema.org types, so existing markup does no harm, but it no longer earns a special result in Google. The types this validator checks are all still documented by Google for search features.

Two policies explain many “valid, but nothing shows” cases. Review stars aren’t shown for reviews a business publishes about itself in its own LocalBusiness or Organization markup. And markup must describe content that visitors can actually see on the page (structured data guidelines).

Tips for markup that validates and shows

• Use JSON-LD where you can; Google recommends it, and it is easier to maintain than microdata woven through the HTML.
• Look for duplicates: a theme and an SEO plugin often both output Organization or Product markup with conflicting values.
• Keep prices, availability and ratings in the markup in sync with what the page shows; mismatches can lead to manual actions.
• Fix required properties first, then recommended ones such as image, brand or aggregateRating.
• After fixing, watch the matching enhancement report in Search Console for new errors over the following weeks.

Limits to keep in mind

We read the HTML your server sends and don’t run JavaScript, so markup injected by Google Tag Manager or client-side code won’t be found, even though Google may see it after rendering. Property checks follow Google’s documented rules for the types listed above; other types get syntax and type detection only. A clean result doesn’t guarantee a rich result. To test code before it is published, paste it into Google’s Rich Results Test, or build it with the schema markup generator.

Last updated Oct 30, 2026 by the Yes SEO team.