Schema Markup and Structured Data Validator
Check the structured data of up to 500 URLs: detects JSON-LD and Microdata, verifies @context and @type, and flags the required properties missing from each type.
What this validator checks
It downloads the HTML of each URL, extracts every structured data block and validates four things per block: that the JSON is syntactically correct, that it declares an @context pointing at schema.org, that it declares an @type, and that the properties Google requires for that type are present. It also detects whether the page uses Microdata alongside JSON-LD.
@context is the one most often overlooked. A block without it can have every property perfect and Google still will not read it as structured data, so it is flagged as an error rather than a warning.
How to check your page's schema step by step
You need no access to the site and nothing to install: the URL just has to be reachable from the internet.
- 1
Paste the URLs you want to verify, one per line. You can enter up to 500 depending on your plan and they are all checked at once.
- 2
Run the analysis. Each URL returns all of its blocks separately, because a page usually has several: Organization, BreadcrumbList and the main type.
- 3
Start with the red errors. A missing @context or invalid JSON voids the whole block, so fixing properties before that achieves nothing.
- 4
Then review the warnings: these are recommended properties that do not break the markup but leave the rich result thinner.
If you are validating a template, check two or three URLs of the same type rather than one. Template faults repeat across all of them, which confirms it is the template and not that particular page.
The types it checks and what each one requires
For these types the validator knows the properties Google asks for and flags any that are missing. Types outside this list are still validated for syntax, @context and @type, but without property checks.
Article / BlogPosting
Activates the news carousel in Google News and improves presentation in editorial content searches.
Product
Shows price, availability and ratings directly in the SERP. Essential for e-commerce.
Recipe
Generates rich results with image, preparation time, calories and rating. High visibility in recipe searches.
Event
Shows event name, date, location and price in results. Ideal for ticketing and cultural listings.
FAQPage
Expands questions and answers directly in the SERP, taking up much more visual space than a standard snippet.
HowTo
Shows numbered steps in the SERP for 'how to' queries. Very effective for tutorials.
LocalBusiness
Strengthens local search presence with name, address, phone and hours. Complements Google Business Profile.
VideoObject
Activates video thumbnails in the SERP and enables indexing in Google Videos with timestamps.
JSON-LD, Microdata and RDFa: what the validator detects
The validator extracts and fully checks JSON-LD blocks, the format Google recommends, and also reports whether the page uses Microdata. That last part matters because mixing formats on one page is a common source of duplicated data.
JSON-LD
Independent script in the '<head>'. Easy to maintain, does not modify visible HTML. Recommended by Google.
✓ Google recommended formatMicrodata
HTML attributes within the actual content (itemscope, itemprop). Harder to maintain but integrated with the DOM.
RDFa
Similar to Microdata but using RDFa attributes (typeof, property). Common in sites with semantic CMS.
How to read the result
Each block is shown with its type, its status and the issues found. A valid block looks like this: note that @context and @type come first, because those two decide whether Google even reads the rest.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Product",
"name": "Product Name",
"description": "Product description.",
"image": "https://example.com/image.jpg",
"offers": {
"@type": "Offer",
"price": "29.99",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
},
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.5",
"reviewCount": "89"
}
}
</script>Frequently asked questions about schema markup
Guides on schema markup
The validator tells you what is broken. These guides explain why it breaks and how to fix it.
What Is Schema Markup and How It Improves SEO
Schema markup is the code that allows Google to understand your page content and display it as rich results in search. Learn what types exist, how they are implemented, and what real benefits they deliver.
Read guideSchema Markup for Ecommerce: Product, Offer, and Review
Product schema markup delivers the highest direct ROI for online stores: it shows price, availability, and star ratings in search results. Learn how to implement it correctly with all required fields.
Read guideFAQPage and HowTo Schema: How to Take Up More Space in the SERPs
FAQPage and HowTo are the schema types with the greatest visual impact in search results. Learn how to implement them correctly so Google displays your questions and steps directly in the SERP.
Read guideSchema Markup in WordPress: Plugins and Step-by-Step Configuration
How to implement schema markup in WordPress with Yoast SEO, Rank Math, and Schema Pro. What each plugin generates automatically, what you need to add manually, and how to verify that Google processes it correctly.
Read guideLocalBusiness Schema: Complete Guide for Local Businesses
LocalBusiness schema helps Google display your business in local searches with hours, phone number, and ratings. Learn how to implement it correctly for restaurants, stores, clinics, and any business with a physical address.
Read guideHow to Debug Schema Errors: Rich Results Test and Other Tools
Your schema can be technically valid but still not generate rich results. Learn how to use the Rich Results Test, the Schema.org validator, and Google Search Console to identify and fix exactly what is failing.
Read guide