Structured Data Checker

To see what structured data a page has, paste its URL into the free Structured Data Checker above, or paste the HTML or JSON-LD. It finds every JSON-LD block, Microdata item and RDFa element, and lists every schema.org type, including nested ones. It reports JSON syntax errors with their position, and checks the required and recommended properties Google uses for common rich results such as Product, Article, LocalBusiness, Event, Recipe, Video and Breadcrumb. You can check up to 20 pages at once and export the summary as a CSV.

Last updated: 6 November 2026. Written by Saad Raza.

Key takeaways

• Structured data tells search engines and AI systems what a page is about in a machine-readable way: the product, its price, the business, its address, the author of an article.
• One invalid JSON character, such as a trailing comma, stops the whole JSON-LD block from being read. Syntax errors are the first thing to fix.
• Each rich result type has required properties. Missing one means no rich result for that item, even if the rest is perfect.
• Markup must describe content that visitors can see on the page. Marking up hidden or invented content breaks Google’s guidelines.

What structured data is and why presence matters

Schema markup is a shared vocabulary, schema.org, written into a page in one of three formats. JSON-LD is a script block, Google’s preferred format and the easiest to maintain. Microdata and RDFa are attributes woven into the HTML. My comparison of JSON-LD vs Microdata vs RDFa explains the trade-offs. Many sites have a mix without knowing it: a theme adds Microdata, an SEO plugin adds JSON-LD, and a reviews widget adds its own.

That is why a presence check comes before a quality check. You need to know what is on the page, in which format, and whether two sources describe the same thing differently, before you can fix it. Google has retired its old Structured Data Testing Tool; my note on what replaced it covers the official options, and this checker adds bulk checking across many pages.

How to use the Structured Data Checker

1. Paste one URL, or up to 20 with one per line. Mix templates: home page, a product, a blog post, a location page.
2. Or paste HTML or raw JSON-LD into the second box to test code before it goes live.
3. Run the check. The summary shows, for each page, the formats found, the top-level types, and the number of errors and warnings.
4. Open each page’s section for every item, nested items marked with a corner symbol, the problems found and the recommended properties that are missing.
5. Fix the errors, then confirm important pages in Google’s Rich Results Test.

What the checker tests

The checker understands context. An Offer only needs a price when it is the offer of a product, app, event or course; an Offer inside a business’s catalogue of services does not. A Review nested inside a Product does not need its own itemReviewed. That avoids the false errors that simpler checkers report on well-built pages.

A worked example with real pages

I checked four pages on 6 November 2026.

• The SEO tools hub on this site has two JSON-LD blocks: a Yoast graph and an FAQ block. The checker found WebPage, CollectionPage, BreadcrumbList, WebSite, Person, Organization, ProfessionalService, ItemList and FAQPage at the top level, with dozens of nested items such as the WebApplication entry for each tool. It reported no errors or warnings, and a note that FAQ rich results are now limited to government and health sites.
• MDN Web Docs uses no JSON-LD. Its breadcrumb is marked up in RDFa, so the checker lists a BreadcrumbList with nested ListItem and WebPage elements.
• BBC News has one JSON-LD block describing a WebPage with a NewsMediaOrganization as publisher.
• example.com has no structured data at all.

A broken page looks very different. A test page with a product priced as "Rs. 2,500" in currency "Rupees", a rating of 6 with no review count, a second JSON-LD block with a trailing comma and an event dated “next friday” produced nine errors. Every one came with the fix.

How to fix common structured data problems

• Syntax errors: paste the block into the JSON-LD validator, which points to the exact character. Watch for trailing commas and curly quotes pasted from word processors.
• Prices and currencies: use digits only for price and a three-letter code for priceCurrency. The product schema generator converts prices such as “Rs. 4,500” for you.
• Missing required properties: check the type’s requirements in my guides to Product schema, Article schema and Organization schema.
• Duplicate sources: if a theme and a plugin both output Product or Organization markup, switch one off so they do not contradict each other.
• Errors in Search Console: my guide to fixing structured data errors in Search Console explains each report.

To create markup from scratch, use the schema markup generator, or the dedicated breadcrumb and FAQ generators for bulk work.

Limits

The checker reads the HTML our server receives. Structured data injected by JavaScript, for example through Google Tag Manager, is not seen, although Google can often render it. Rules cover the most common rich result types and their key properties, not every type in schema.org, and Microdata and RDFa are listed by type without property checks. Passing every check does not guarantee a rich result: Google decides based on quality and eligibility, and some types, such as HowTo, no longer produce rich results at all. Up to 20 pages are checked per run within the fair-use limit.

Questions about the Structured Data Checker

If your site needs structured data planned and implemented properly, my technical SEO services cover schema across all templates, and you can ask for a free audit. You can also browse the other free schema markup generators.