Check a page's structured data field by field: fetch any URL (or paste markup) and see exactly which required and recommended schema properties are missing.
How it works
The validator pulls every application/ld+json block from the page, including entities nested inside @graph and arrays. It parses each block and checks every recognised type against the same field catalog our Schema Markup Generator uses. A missing required field is an error. A missing recommended field is a warning. Each finding shows the exact property path to add.
Types outside the 15-type catalog are detected and checked for valid syntax, and labelled as such. Fix what is missing in our Schema Markup Generator, paste the result back here, and ship it clean.
What the results show
- Summary line
- Where the markup came from, how many JSON-LD blocks and entities we found, and the total errors and warnings. Blocks that are not valid JSON are counted separately.
- Entity card
- One card per entity, with its
@typeand a status badge: Valid, Warnings, Errors, or Detected for a type outside the catalog. - Missing required
- A field the type needs to qualify for its rich result, with the property path and a plain-English label.
- Missing recommended
- A field that is optional but strengthens the markup. Add these when you can.
Frequently asked questions
How do I validate schema markup?
Enter a page URL and click Validate URL. We fetch the page once, pull out every JSON-LD block, and check each entity for missing required and recommended fields. Or paste HTML or raw JSON-LD instead. Pasted markup is checked in your browser and never leaves it.
What is JSON-LD?
JSON-LD is the format Google recommends for structured data. It is a small block of JSON inside a <script type="application/ld+json"> tag, usually in the page head. It describes what the page is about, such as a product, a recipe or an event, using the shared vocabulary at schema.org. Search engines read it to show rich results.
What do errors and warnings mean?
Errors are missing required fields. Without them, the type is usually not eligible for its rich result. Warnings are missing recommended fields. The markup is still valid, but adding them improves eligibility and lets Google show more. Each finding names the exact property path to add.
Which schema types are checked in depth?
The 15 types our Schema Markup Generator builds: Article (including NewsArticle and BlogPosting), Breadcrumb, Course, Event, FAQ Page, Job Posting, Local Business, Organization, Person, Product, Recipe, Review, Software Application, Video and WebSite. Other types are still detected and checked for valid syntax, and the card says so. We do not pretend to validate them in depth.
Does it check microdata and RDFa too?
No, JSON-LD only. It is the format Google recommends and nearly every modern site uses. If your site still uses microdata, consider moving over. Our Schema Markup Generator outputs JSON-LD ready to paste.
Is this the same as Google's Rich Results Test?
No, the two go together. Google's test tells you whether Google will grant a rich result today. This validator gives you a fast field-by-field checklist against the documented requirements. It works on drafts you paste before publishing, and it pairs with our generator to fix what is missing. For final sign-off, run Google's test as well.
Why did it find no structured data on my page?
Either the page has no application/ld+json blocks, or JavaScript adds them after the page loads. We validate the HTML the server sends, which is also what crawlers read most reliably. View the page source and search for ld+json to confirm.
Are there limits?
Validating a live URL uses one unit of your daily page-fetch allowance, shown in the quota banner. Pasted markup has no limit, because nothing touches the server.