Structured Data Validator
Validate structured data JSON-LD and Schema.org. Detect errors before publishing.
Why use it
Correct rich snippets, more clicks on Google
Full Schema.org
Validates Article, Product, FAQ, LocalBusiness, Recipe and 800+ types.
Private
Data is validated in your browser. Never sent to any server.
Precise errors
Missing fields, wrong types, and format issues detected instantly.
Instant
Validation in milliseconds. No signup, no waiting.
How it works
Three steps, no hassle
Paste your JSON-LD or Microdata
Paste the structured data block from your page. Supports JSON-LD, Microdata, and RDFa.
Select the Schema.org type
Choose Article, Product, FAQ, LocalBusiness, Recipe, or another type for specific validation.
Review errors and warnings
The validator shows missing fields, wrong types, and suggestions for Google rich results.
FAQ
Got questions?
Structured data is machine-readable information added to a page's HTML to describe its content in a structured way. It allows search engines (Google, Bing) to understand the type of content (article, product, recipe, event, FAQ) and its specific properties (price, author, date, rating). The visible result is rich results or rich snippets: rating stars, expandable FAQs, product prices, and recipes in search results.
Google explicitly recommends JSON-LD (JavaScript Object Notation for Linked Data) as the easiest format to implement and maintain: it is added in a <script type='application/ld+json'> block without modifying existing HTML. Microdata requires adding itemscope, itemtype, and itemprop attributes directly in the HTML, mixing content and metadata. RDFa is similar to Microdata but more expressive, used mainly in academic and linked data environments. For practical SEO in 2025, JSON-LD is the correct choice.
For Article, required fields are: headline, datePublished, author (with @type Person and name). For Product: name, and at least one of offers, review, or aggregateRating. For FAQPage: mainEntity with @type Question, name (the question), and acceptedAnswer with @type Answer and text. Required fields vary by type and are defined by Google in its Search Central documentation, not Schema.org, as Google has stricter requirements for rich results than the full Schema.org vocabulary.
Google Rich Results Test (search.google.com/test/rich-results) lets you paste a URL or HTML directly to see what rich results the page can generate. It shows critical errors (preventing rich results) and warnings (reducing eligibility). Complementary to this, Google Search Console > Enhancements shows the structured data status of all indexed pages on the site, including errors the crawler has detected in production.
The most frequent errors are: (1) missing or incorrect @context — must be 'https://schema.org' exactly; (2) incorrect @type — 'article' in lowercase instead of 'Article'; (3) date fields in wrong format — must be ISO 8601 (2024-01-15T10:30:00+00:00); (4) relative URLs instead of absolute in fields like 'url' or 'image'; (5) aggregateRating with ratingCount of 1 — Google may reject ratings with very few reviews as unrepresentative.
Schema.org history and structured data for SEO
Schema.org was launched in June 2011 as a joint initiative by Google, Microsoft (Bing), Yahoo, and Yandex: the four major search engines agreed on a common vocabulary so webmasters could describe their content in a standard way. Before Schema.org there were fragmented vocabularies: Dublin Core (bibliographic metadata), microformats (hCard, hCalendar), and RDFa. Schema.org unified these efforts with a hierarchical vocabulary where Thing is the root class from which all others derive.
JSON-LD (JavaScript Object Notation for Linked Data) was designed by Manu Sporny and published as a W3C recommendation in 2014. The key to its adoption is separation of concerns: structured data is added in a separate <script> block without touching the content HTML, making implementation easier in CMS, JavaScript frameworks, and static site generators. Google began supporting JSON-LD for structured data in 2012 and in 2015 declared it its preferred format, accelerating mass adoption.
E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) is Google's quality evaluation framework that structured data helps signal. Author data (Person schema with sameAs pointing to verified profiles), update dates (dateModified), verified ratings (AggregateRating with significant ratingCount), and organization data (Organization with verified logo) directly contribute to E-E-A-T signals. Pages with correctly implemented rich results show CTR increases of 20–30% in documented case studies.