Schema Validation
Session 5.10 · ~5 min read
Why Validation Matters
Invalid schema is worse than no schema. When your JSON-LD has syntax errors, Google ignores the entire block. When it has property errors, Google may misinterpret your entity data. When it has policy violations, Google may issue manual actions that suppress your search visibility. Validation is not an optional final step. It is the checkpoint between implementing schema and deploying it.
A single missing comma in JSON-LD silently breaks the entire block. Google will not tell you. Your entity signals disappear, and you will not know unless you test.
The Three Validation Tools
Google and the Schema.org community provide three complementary tools. Each catches different types of problems:
| Tool | URL | What It Checks | When to Use |
|---|---|---|---|
| Rich Results Test | search.google.com/test/rich-results | Google-specific rich result eligibility | Before deployment and after changes |
| Schema Markup Validator | validator.schema.org | General schema.org compliance | For comprehensive syntax and type validation |
| Google Search Console | Enhancements section in GSC | Ongoing monitoring of indexed pages with schema | Weekly check after deployment |
The Validation Workflow
(jsonlint.com)"] B --> C{"Valid
JSON?"} C -->|No| D["Fix Syntax Errors
(commas, brackets, quotes)"] D --> B C -->|Yes| E["Step 2: Schema Markup Validator
(validator.schema.org)"] E --> F{"Valid
Schema?"} F -->|No| G["Fix Schema Errors
(types, properties, nesting)"] G --> E F -->|Yes| H["Step 3: Rich Results Test
(Google)"] H --> I{"Eligible for
Rich Results?"} I -->|Yes| J["Deploy to Production"] I -->|Errors| K["Fix Google-Specific Issues"] K --> H J --> L["Step 4: Monitor in GSC
(Enhancements tab)"]
Common Errors and Fixes
| Error Type | Example | Fix | Tool That Catches It |
|---|---|---|---|
| JSON syntax | Trailing comma: "name": "Arsindo",} |
Remove the comma before closing brace | jsonlint.com |
| Wrong @type | "@type": "Organziation" (typo) |
Use exact schema.org type names | Schema Markup Validator |
| Invalid property for type | openingHours on Organization (should be LocalBusiness) |
Check which type supports the property | Schema Markup Validator |
| Missing required properties | Product without name |
Add all required properties per Google's docs | Rich Results Test |
| URL format issues | Logo URL without protocol: "logo": "yoursite.com/logo.png" |
Always use full URLs with https:// | Rich Results Test |
| Mismatched visible content | FAQ schema with questions not visible on page | Schema must match what users can see | Manual review (Google may catch during crawl) |
Monitoring in Google Search Console
After deployment, the Enhancements section in Google Search Console is your ongoing monitoring dashboard. It shows:
- Valid items: Pages where Google successfully processed your schema
- Items with warnings: Schema works but has issues that should be fixed
- Items with errors: Schema is not being processed correctly
Check this section weekly after deployment. New errors can appear when Google recrawls pages, especially if your CMS or template generates schema dynamically and something changes.
Your Pages"] Crawl --> GSC["Search Console
Enhancements"] GSC --> Valid["Valid Items
(working correctly)"] GSC --> Warn["Warnings
(fix recommended)"] GSC --> Error["Errors
(fix required)"] Error --> Fix["Fix and
Revalidate"] Fix --> Crawl
The Validation Checklist
Before deploying any schema to production, confirm:
- JSON syntax is valid (no trailing commas, all brackets closed, double quotes only)
- All @type values are spelled correctly and exist in schema.org
- All @id values are consistent across pages that reference the same entity
- All URL values use full, canonical URLs with correct protocol
- All sameAs URLs resolve to live, correct pages
- Schema content matches visible page content
- Rich Results Test shows expected rich result types as eligible
- No errors in Schema Markup Validator
Further Reading
- Schema Markup Testing Tool - Google Search Central's Rich Results Test entry point.
- Schema Markup Validator - The official Schema.org validation tool for comprehensive compliance checking.
- Schema Validation: How to Test Your Markup - Aruntastic's guide to the full validation workflow.
- How to Check Schema Markup - Aubrey Yung's practical guide to schema testing and monitoring tools.
Assignment
- Run every page that has structured data through both the Rich Results Test and the Schema Markup Validator.
- Create a spreadsheet with columns: Page URL, Schema Types on Page, Errors, Warnings, Rich Results Eligible.
- Fix every error. Address warnings where possible.
- Retest after fixes until all pages pass clean on both tools.
- Set a weekly calendar reminder to check Google Search Console's Enhancements section for any new schema errors.