Schema Validator

Validate JSON-LD structured data, enforce required properties for popular schema.org types, and surface missing fields before you deploy markup.

Pro Tip: Use "Auto-detect" mode to automatically identify schema types, or select a specific type to validate against its required properties.

Schema Input

Paste the JSON-LD snippet or blob you want to validate.

Drop your JSON file here or click to browse

Supports .json and .jsonld files

Upload a .json or .jsonld file with structured data markup.

Validation Settings

Optional: enforce a specific schema type when validating.

Supported Schema Types

  • Article: News, blog posts, stories
  • Product: E-commerce products
  • LocalBusiness: Physical locations
  • Organization: Companies, brands
  • FAQPage: FAQ content
  • Event: Events, webinars
  • Recipe: Cooking recipes

Schema Validator Tutorial

What This Tool Does:

The Schema Validator helps you ensure your JSON-LD structured data is properly formatted and contains all required properties for Google's rich results:

  • Validates JSON Syntax: Catches malformed JSON before deployment
  • Checks Required Fields: Verifies schema.org required properties are present
  • Auto-Detects Types: Automatically identifies @type from your markup
  • Detailed Feedback: Shows exactly which fields are missing and why

How to Use:

  1. Paste JSON-LD: Copy your structured data into the text area, or upload a .json file
  2. Select Schema Type: Choose a specific type or use "Auto-detect" mode
  3. Click Validate: The tool will check your markup against schema.org requirements
  4. Review Results: Fix any missing required fields before deploying

Common Schema Types:

Type Use Case Key Required Fields
Article Blog posts, news articles headline, author, datePublished, image
Product E-commerce products name, image, offers (price, availability)
LocalBusiness Physical business locations name, address, telephone
FAQPage FAQ content mainEntity (Question + acceptedAnswer)
Event Events, webinars, concerts name, startDate, location

Best Practices:

  • Test Before Deploy: Always validate schema before pushing to production
  • Use Google's Tool Too: Cross-check with Google's Rich Results Test
  • Include Images: Most rich results require image properties
  • Keep Updated: Schema.org requirements change - revalidate periodically