Schema Markup Validator & Rich Results Tester

Validate JSON-LD, Microdata, RDFa, and page URLs for schema health and rich result eligibility.

Schema Markup Validator & Rich Results Tester

Validate JSON-LD, Microdata, RDFa, and page URLs for schema health, required fields, and rich result eligibility.

What Is a Schema Markup Validator & Rich Results Tester?

A schema markup validator checks structured data code and explains whether it is complete enough for rich result eligibility. It looks for syntax problems, missing required fields, recommended properties, unsupported schema types, and markup that may be too weak for search engines to understand confidently.

What This Tool Tests

This validator supports page URLs, JSON-LD code, Microdata, and RDFa. It detects common schema types including Article, BlogPosting, FAQPage, Product, Review, Organization, LocalBusiness, Event, Recipe, VideoObject, BreadcrumbList, WebSite, Service, Course, and JobPosting.

How to Use This Tool

  1. Use URL Test to fetch a live page and extract all structured data.
  2. Use Code Test to paste JSON-LD, Microdata, or RDFa directly.
  3. Review the schema overview, detected schema types, and health score.
  4. Fix errors first, then review warnings and recommended properties.
  5. Export the results as JSON or TXT for your developer or content team.

Why Schema Validation Matters

Invalid schema does not help search visibility and can create Search Console warnings. Even when markup is syntactically valid, missing required fields may prevent rich results such as articles, breadcrumbs, products, reviews, recipes, events, and job postings. A good validation workflow catches these issues before publishing.

Best Practices

Match visible content: Structured data should describe content users can actually see on the page.

Prefer JSON-LD: Google recommends JSON-LD because it is easier to manage and less likely to break page HTML.

Use complete entities: Add authors, publishers, dates, images, prices, ratings, and locations where relevant.

Retest after edits: Schema can become outdated when prices, dates, FAQs, or page templates change.