Structured data source
Add structured data to begin
Validate a URL, raw JSON-LD, or pasted HTML to see schema types, rich result readiness, and fixes.
What is Schema Markup?
Schema markup is structured data that helps search engines understand the entities on a page, such as articles, products, FAQs, breadcrumbs, organizations, events, recipes, videos, courses, jobs, reviews, and how-to content. This validator checks JSON-LD markup, highlights missing properties, and estimates rich result readiness without sending pasted JSON-LD or HTML away from the browser.
How to use
1. Choose URL, JSON-LD, or HTML input mode. 2. Paste a page URL, raw JSON-LD, or HTML containing application/ld+json scripts. 3. Review detected schema types, required fields, recommended fields, invalid URLs or dates, and the Rich Results score. 4. Open the tree or raw JSON preview, then copy the JSON report when you need to share validation details.
JSON-LD vs Microdata
JSON-LD keeps structured data in a script tag and is usually easier to maintain than inline Microdata attributes. This MVP focuses on JSON-LD extraction from pasted JSON, pasted HTML, and fetched page HTML. Microdata and RDFa are planned for a later phase.
Common errors
Frequent schema problems include missing required properties, relative image or URL values, dates that are not ISO 8601 compatible, Product markup without offers, Article markup without author or datePublished, and FAQPage markup without mainEntity questions. The issue list includes practical suggestions for each missing or invalid field.
Supported schema types
The validator currently recognizes Article, BlogPosting, NewsArticle, Product, FAQPage, BreadcrumbList, Organization, LocalBusiness, WebSite, WebPage, Person, Event, Recipe, VideoObject, SoftwareApplication, JobPosting, Course, Review, AggregateRating, and HowTo. It can detect unsupported JSON-LD types in the same document, but scoring and required-property checks are only applied to the supported schema types.
Rich Results limitations
The score is a developer-friendly readiness estimate based on required fields, recommended fields, and format quality. It does not guarantee Google will show a rich result, because eligibility also depends on page content, search policies, crawlability, rendering, indexing, and the visible user experience.