Structured Data Viewer
Enter a URL to extract every JSON-LD block on the page, formatted and checked for syntax errors.
What the viewer shows
Structured data is a machine-readable description of the page: this is an article, written by this person, published on this date. On most sites it lives in one or more <script type="application/ld+json"> elements, minified and hard to read in view-source. The viewer pulls out each block and gives you:
- The schema.org types it contains, including entities nested in
@graphor in a top-level array, and entities with several types. - The JSON, formatted with indentation, ready to copy or download.
- The exact parser message when a block is not valid JSON. One trailing comma is enough for Google to ignore the whole block.
- A note when microdata (
itemscope) or RDFa (typeof) attributes are also present, since duplicate descriptions in two formats tend to drift apart.
Field hints
For six common types the tool checks the basics from Google's rich result documentation:
- Article (also NewsArticle and BlogPosting): headline, image, datePublished, dateModified and author are recommended.
- Product: name is required, plus one of offers, review or aggregateRating. An offer needs a price.
- FAQPage: mainEntity with questions that each have a name and an acceptedAnswer with text.
- BreadcrumbList: itemListElement where every ListItem has a position and a name, and all but the last have an item URL.
- Organization: name, url, logo and sameAs are recommended.
- LocalBusiness: name and address are required. Telephone, opening hours and geo are recommended.
These are hints, not a full validation. Nested objects are not checked in depth, and the requirements for each rich result change over time, so confirm important pages in Google's Rich Results Test.
Common mistakes
- Markup that describes content users cannot see on the page. Google treats that as a guideline violation.
- Two plugins that both output an Organization or Product, with different values.
- Relative URLs in
image,logoorurl. Use absolute URLs.
Need to write markup from scratch? Use the schema markup generator. Structured data is only read when the page is crawled, so first confirm the page can be indexed with the indexability checker. TurboIndex can then ask Google to recrawl it.
Questions and answers
Does this replace Google's Rich Results Test?
No. This tool is for reading and debugging: it shows every block quickly, formats it and points out syntax errors and the most common missing fields. Google's Rich Results Test is the authority on whether a page qualifies for a specific rich result, and it also renders JavaScript, which this tool does not.
Why does the tool find no structured data when Google's test does?
Your markup is probably injected by JavaScript, for example through a tag manager or a client-side framework. This tool reads the HTML response only. Google can pick up injected JSON-LD after rendering, but markup in the initial HTML is processed sooner and more reliably.
What is @graph?
It is a JSON-LD keyword that holds a list of entities inside one block. SEO plugins use it to describe the WebSite, WebPage, Organization, Article and BreadcrumbList together and link them with @id references. The viewer lists each entity in the graph separately.
Will valid structured data guarantee rich results?
No. Valid markup makes a page eligible. Google decides per query whether to show a rich result, and it requires that the markup matches content users can see on the page.
JSON-LD, microdata or RDFa: which should I use?
Google supports all three and recommends JSON-LD, because it sits in one script block and is easier to maintain than attributes spread across the HTML.