Structured Data Viewer

What it's for

See the structured data a page gives search engines: the schema.org items (products, articles, events, recipes, FAQs, breadcrumbs…) written as JSON-LD, microdata or RDFa. Each item is shown as a tree, properties that Google’s rich results need are checked, and everything is given back as JSON-LD.

For example, when a page has stopped showing star ratings or prices in search results, paste its HTML to see whether the product markup is still there and what it’s missing.

How to use it

Paste a page’s HTML (from View Source), or just its JSON-LD. Every <script type="application/ld+json"> block is read, an @graph is split into its items, and elements with itemscope (microdata) or typeof (RDFa) become items too, with their properties taken from itemprop or property. schema.org addresses are shortened, so https://schema.org/Product shows as Product.

The list at the top shows JSON that won’t parse, items with no @type or @context, and missing properties for Article, Product, Offer, FAQPage, BreadcrumbList, Event and Recipe: required ones as problems, recommended ones as notes. As JSON-LD has every item, microdata and RDFa converted, ready to copy.

Example

Press Try an example: a JSON-LD product and a microdata breadcrumb. The message says 2 items found, with 1 problem listed below. The problem is that the Product has no offers, review or aggregateRating, which Google lists as required for its rich result, and a note suggests adding a description. The breadcrumb’s ListItem has its item, name and position.

Good to know

Passing these checks doesn’t mean a rich result will show: Google decides that, and its requirements change, so confirm with its Rich Results Test. Only the common types above are checked, and values aren’t (a price of free passes). Markup that a page’s scripts add after it loads isn’t in View Source; copy the HTML from the developer tools’ Elements panel instead. RDFa is read in its Lite form (vocab, typeof, property), without prefixes other than schema:.