7 min read · AI Visibility · Last updated July 2026
Quick answer: Structured data validation tests your JSON-LD schema markup for errors that would prevent Google and AI systems from reading it correctly. The primary validation tools are Google’s Rich Results Test and Schema.org’s Schema Markup Validator. Validation should run after every schema implementation and quarterly thereafter to catch regressions.
Introduction
You implement schema markup to signal structured data to search engines and AI systems. But if the markup contains errors — malformed JSON, missing required properties, incorrect URLs — search engines cannot read it, and all the implementation effort is wasted.
Structured data validation is the quality gate between schema implementation and schema benefit. It is a mandatory step, not an optional one.
What you’ll learn:
– The three primary validation tools and when to use each
– What validation errors mean and how to fix them
– Common schema mistakes caught by validators
– The validation workflow for new implementations and maintenance
– Testing schema in staging before publishing
Table of Contents
- The Three Validation Tools
- Google’s Rich Results Test
- Schema Markup Validator (schema.org)
- Google Search Console Schema Reports
- Common Validation Errors and Fixes
- Validation Workflow
- Testing Schema Before Going Live
- Frequently Asked Questions
The Three Validation Tools
Tool 1 — Google Rich Results Test (search.google.com/test/rich-results)
Purpose: Tests whether a page is eligible for specific Google rich results (FAQ, Article, Product, etc.)
When to use: After implementing any schema intended to generate rich results
What it shows: Which schema types are detected, eligibility for specific rich result types, errors and warnings
Tool 2 — Schema Markup Validator (validator.schema.org)
Purpose: Tests schema markup against schema.org specification for technical validity
When to use: For schema types not covered by Rich Results Test, or for technical validity checking
What it shows: Whether the schema is technically valid according to schema.org definitions
Tool 3 — Google Search Console (Enhancement Reports)
Purpose: Shows schema errors and warnings across your entire site at scale
When to use: Ongoing monitoring; catching regressions after site updates
What it shows: Site-wide errors by schema type, affected pages, error descriptions
Google’s Rich Results Test
The Rich Results Test is the most commonly used validation tool for marketing and SEO purposes. Here is how to use it:
Step 1: Navigate to search.google.com/test/rich-results
Step 2: Enter either:
– A URL (tests the live page as Google sees it)
– Code snippet (paste JSON-LD directly for testing)
Step 3: Review the results panel:
– Detected items: Which schema types were found
– Eligible for rich results: Whether the schema qualifies for enhanced display
– Errors: Problems that prevent schema from working (must fix)
– Warnings: Issues that reduce effectiveness but do not break functionality
What each status means:
| Status | Meaning | Action Required |
|---|---|---|
| Valid item | Schema is correct | None — schema is working |
| Warning | Non-critical issue | Fix if possible, but not urgent |
| Error | Critical problem | Must fix — schema will not function |
| Not detected | Schema type not found | Check implementation |
Rich result type coverage:
The Rich Results Test validates: Article, Breadcrumb, Carousel, Course, Dataset, Event, FAQ, HowTo, JobPosting, LocalBusiness, Organization, Person, Product, QAPage, Recipe, Review, Sitelinks Searchbox, SoftwareApp, Speakable, Video.
Schema Markup Validator (schema.org)
For schema types not covered by the Rich Results Test, or for deeper technical validation:
URL: validator.schema.org
How it differs from Rich Results Test:
– Tests schema against the schema.org specification
– Does not predict Google rich result eligibility
– More comprehensive for uncommon schema types
– Useful for validating custom or complex schema implementations
When to use:
– Testing WebSite schema with sitelinks search box
– Testing SpeakableSpecification schema
– Testing complex nested schema structures
– Validating schema types not in the Rich Results Test
Google Search Console Schema Reports
Google Search Console provides site-wide schema monitoring under the “Enhancements” section:
How to access:
Search Console → Enhancements → [Schema Type]
Available enhancement reports:
– Breadcrumbs
– FAQs
– Articles
– Products
– Reviews
– HowTo
– Events
– Video
– SiteLinksSearchBox
What to monitor:
– “Error” count — schema implementations that are completely broken
– “Valid with Warnings” count — schema that works but has minor issues
– “Valid” count — correctly implemented schema pages
Trend monitoring:
If the error count increases after a site update, that indicates a deployment broke schema on affected pages. Use the affected URL list to debug specific pages.
Common Validation Errors and Fixes
Error 1 — Missing required property:
Error: "Missing field 'image' in 'VideoObject'"
Fix: Add the missing required property. Refer to schema.org for each type’s required vs. recommended properties.
Error 2 — Wrong value type:
Error: "Expected type URL, got Text for 'image'"
Fix: The image property requires a URL (https://…), not plain text. Correct the value format.
Error 3 — Malformed JSON:
Error: "JSON parse error"
Fix: The JSON-LD block has a syntax error. Use a JSON validator (jsonlint.com) to find and fix the malformed JSON before re-testing.
Error 4 — Duplicate entities:
Warning: "Multiple JSON-LD blocks with same @type"
Fix: Consolidate multiple same-type JSON-LD blocks into a single block, or ensure each block has a unique @id.
Error 5 — URL not accessible:
Warning: "Cannot access URL specified in 'url' property"
Fix: The URL in the schema is returning a 404 or redirect. Update to the correct canonical URL.
Error 6 — Rating value out of range:
Error: "ratingValue must be between worstRating and bestRating"
Fix: Ensure your rating value (e.g., 4.8) falls between your worstRating (1) and bestRating (5).
Validation Workflow
Schema Validation Workflow
Follow this process for every schema implementation
Frequently Asked Questions
Q: How often should I run schema validation?
A: After every schema implementation (immediately) and after any major site deployment. Additionally, run quarterly audits on your most important pages — CMS updates, theme changes, and plugin conflicts can corrupt schema markup silently.
Q: Does a validation warning mean my schema is broken?
A: No. Warnings indicate non-critical issues — the schema functions but is missing recommended (not required) properties. Fix warnings when practical to maximize schema benefit, but they do not prevent schema from working.
Q: My schema validates but no rich results appear in Google. Why?
A: Several reasons: Google needs 2-4 weeks to crawl and process newly implemented schema. Google’s rich result eligibility depends on page quality as well as schema — a low-quality page may not receive rich results even with valid schema. Google does not guarantee rich results for all valid schema implementations.
Conclusion
Schema validation is a mandatory quality gate, not an optional optimization step. Valid schema that AI systems can read accurately is worth far more than broken schema that generates no signal at all. Build the 8-step validation workflow into your standard schema implementation process, and run quarterly audit checks on your most important pages.
Get AI-Ready with Ignited Nepal
We implement, validate, and monitor complete schema stacks — ensuring your structured data is error-free and working hard for AI visibility.
→ Request an AI Visibility Audit
Written by the Ignited Nepal AI Visibility team. ignitednepal.com