On-page
Schema Validator
Validate JSON-LD schema markup. Check syntax, required fields, data types, and Google rich results eligibility instantly.
0 characters •
0 lines
📚 Example Schemas
Article
Blog posts, news articles
Product
E-commerce products
LocalBusiness
Local shops, restaurants
FAQ
Frequently asked questions
🎯 What This Validator Checks
- JSON Syntax: Valid JSON-LD format and structure.
- Schema Type: Recognized schema.org type.
- Required Fields: All mandatory properties present.
- Property Names: Valid schema.org vocabulary.
- Data Types: Correct formats (URL, Date, Number).
- Nested Schema: Valid nested objects.
- Google Requirements: Rich results eligibility.
- Common Errors: Missing @context, typos, deprecated fields.
How to Use Schema Validator to Check JSON-LD Markup
Validate schema markup instantly. Check JSON-LD syntax, required fields, data types, and Google rich results eligibility. Supports Article, Product, LocalBusiness, FAQ, and 10+ schema types. Free schema.org validator tool.
Getting Started
Validate schema markup in seconds.
- Paste Schema: Copy your JSON-LD code and paste it in the text area.
- Click Validate: Tool analyzes syntax, structure, and requirements instantly.
- Check Results: See if schema is valid, with errors highlighted.
- Review Errors: Red errors must be fixed, yellow warnings are optional.
- Check Google Eligibility: See if schema qualifies for rich results.
- Fix Issues: Follow specific recommendations to correct problems.
- Revalidate: Paste updated code and check again until valid.
- Implement: Add validated schema to your website HEAD or BODY.
What Gets Validated
Comprehensive schema checking.
- JSON Syntax: Checks if code is properly formatted valid JSON.
- Schema Type: Verifies @type is present and recognized.
- Required Fields: Checks all mandatory properties for schema type.
- Property Names: Validates against schema.org vocabulary.
- Data Types: Checks URLs, dates, numbers are correct format.
- Nested Schema: Validates nested objects like Person, Organization.
- Google Requirements: Checks rich results eligibility criteria.
- Common Errors: Detects missing @context, typos, deprecated fields.
Supported Schema Types
Multiple schema.org types validated.
- Article: Blog posts, news articles, editorial content.
- Product: E-commerce products with prices and reviews.
- LocalBusiness: Physical stores, restaurants, service businesses.
- Organization: Companies, brands, nonprofits.
- Person: Individual profiles, authors, team members.
- Recipe: Cooking recipes with ingredients and instructions.
- Event: Concerts, conferences, webinars, meetups.
- FAQ: Frequently asked questions and answers.
- HowTo: Step-by-step tutorials and guides.
- VideoObject: Video content for video search.
- BreadcrumbList: Breadcrumb navigation trails.
- Review: Product reviews and ratings.
JSON Syntax Validation
First validation check performed.
- Parser: Uses JavaScript JSON.parse() for accurate checking.
- Error Detection: Catches missing commas, brackets, quotes.
- Line Numbers: Shows exactly where syntax errors occur.
- Common Issues: Trailing commas, unescaped quotes, missing brackets.
- 100% Accurate: JSON parsing is deterministic and precise.
- Quick Feedback: Instant syntax error reporting.
- Formatted Display: Shows error message and location.
- Must Pass: Cannot proceed to schema validation until JSON is valid.
Required Fields Check
Schema type specific requirements.
- Article Requires: headline, image, datePublished, author.
- Product Requires: name, image, offers with price.
- LocalBusiness Requires: name, address with postal details.
- Recipe Requires: name, image, recipeIngredient, recipeInstructions.
- Event Requires: name, startDate, location.
- Person Requires: name at minimum.
- Based on Schema.org: Official documentation standards.
- Google Requirements: Separate check for rich results eligibility.
Data Type Validation
Format checking for different field types.
- URL Validation: image, url, logo must be valid http/https URLs.
- Date Format: datePublished, startDate must be ISO 8601 (YYYY-MM-DD).
- Price Validation: Offers price must be numeric value.
- Rating Values: AggregateRating must have valid ratingValue (0-5).
- Email Format: Email fields must be valid email addresses.
- Telephone: Phone numbers should follow E.164 format.
- Pattern Matching: Regular expressions validate formats.
- Type Checking: Ensures correct data type (string, number, object).
Nested Schema Support
Validates complex nested structures.
- Author Object: Person or Organization nested in Article.
- Address Object: PostalAddress nested in LocalBusiness.
- Offers Object: Offer nested in Product schema.
- Publisher Object: Organization nested in Article.
- Image Object: ImageObject with url property.
- Rating Object: AggregateRating nested in Product.
- Recursive Validation: Checks nested objects at all levels.
- Type Checking: Validates @type in nested objects.
Google Rich Results
Eligibility for enhanced search appearance.
- Rich Snippets: Additional information displayed in search.
- Article Rich Results: Image, date, author shown in results.
- Product Rich Results: Price, rating, availability displayed.
- Recipe Rich Results: Image, rating, cooking time shown.
- Event Rich Results: Date, location, ticket info displayed.
- FAQ Rich Results: Questions expanded directly in search.
- Eligibility Check: Validates Google specific requirements.
- Not Guaranteed: Passing validation doesn't guarantee rich results.
Common Schema Errors
Frequent mistakes detected by validator.
- Missing @context: Must include "https://schema.org".
- Missing @type: Required to identify schema type.
- Wrong Property Names: Typos like "headling" instead of "headline".
- Invalid URLs: Missing http/https or malformed URLs.
- Wrong Date Format: Using "May 17, 2024" instead of "2024-05-17".
- Missing Required Fields: Forgetting mandatory properties.
- Incorrect Nesting: Missing @type in nested objects.
- String vs Number: Using string "29.99" instead of number 29.99 for price.
Error vs Warning
Understanding validation severity.
- Errors (Red): Must be fixed or schema is invalid.
- Warnings (Yellow): Recommended fixes for better results.
- Errors Block: Prevent Google from understanding schema.
- Warnings Reduce: Rich results eligibility but not invalid.
- Fix Errors First: Required to have working schema.
- Then Warnings: Improve SEO and rich snippet chances.
- Example Error: Missing required "headline" field.
- Example Warning: Missing recommended "dateModified" field.
Property Name Checking
Validates against schema.org vocabulary.
- Schema.org Standard: Official property name list.
- Typo Detection: Flags "iamge" should be "image".
- Unknown Properties: Warns about non-standard fields.
- Case Sensitive: Property names must match exactly.
- Suggestions: Tool suggests correct property names.
- Custom Properties: Schema.org allows extensions with namespaces.
- Deprecated Fields: Warns about outdated properties.
- 95% Accurate: Based on documented schema.org vocabulary.
How to Fix Errors
Step-by-step error resolution.
- Read Error Message: Tells you exactly what is wrong.
- Check Example Code: Validator shows correct format.
- Add Missing Fields: Include all required properties.
- Fix Data Types: Convert strings to numbers or URLs where needed.
- Correct Typos: Fix property name spelling.
- Add @context: Include schema.org context at top.
- Validate Nested Objects: Ensure all nested schema have @type.
- Revalidate: Test again after each fix until clean.
FAQ
Is this validator as accurate as Google's tool?
This tool is 85-90% accurate for schema validation. It checks JSON syntax (100% accurate), required fields (95%), and data types (90%). For Google-specific rendering preview, use Google's Rich Results Test as final verification.
Can I validate schema on my live website?
No, browser security (CORS) prevents fetching from external sites. Instead: view your page source, copy the JSON-LD schema code, and paste it here for validation.
What if my schema type is not in the list?
Tool validates 12 common types but works with any valid schema.org type. If yours isn't listed, you'll get a warning but validation still checks JSON syntax, @context, @type, and basic structure.
Do I need to fix all warnings?
Errors (red) must be fixed. Warnings (yellow) are recommended but optional. Warnings improve rich results chances but schema works without them. Prioritize Google required fields for rich snippets.
Why does my valid schema not show rich results?
Validation doesn't guarantee rich results. Google decides based on relevance, competition, and quality. Valid schema is required but not sufficient. Also check: structured data guidelines compliance, manual actions, indexing status.
Can I validate multiple schemas at once?
Yes, if they're in a JSON array. Wrap multiple schemas in brackets: [{schema1}, {schema2}]. Tool validates array structure and checks each schema individually.
What is the difference between @context and @type?
@context defines the vocabulary (schema.org). @type defines what kind of thing it is (Article, Product). Both required. Think: @context is the language, @type is the word.
Should I use JSON-LD or Microdata?
JSON-LD is recommended by Google. It's easier to implement, maintain, and validate. This tool only validates JSON-LD format. Microdata requires different validation approach.
How accurate is the Google eligibility check?
85% accurate based on Google's published documentation. Checks required fields for rich results. For 100% certainty, use Google Search Console Rich Results report after implementing on live site.
Can schema hurt my SEO if implemented wrong?
Invalid schema is ignored by Google - doesn't hurt rankings but wastes opportunity. Misleading schema (wrong info) can trigger manual actions. Spammy schema can cause penalties. Always validate before publishing.
Related tools
Pro tip: pair this tool with URL SEO Score Checker and Subheading Quality Checker for a faster SEO workflow.