Schema Markup Validator – Test Structured Data & Rich Results
Validate schema.org structured data for any URL or JSON-LD snippet. Find errors and warnings that break rich results, search enhancements and SEO performance.
Please include https:// or http:// for more accurate results.
Syntax Check
Validate JSON-LD structured data syntax and schema.org vocabulary compliance.
Rich Snippets
Enhance your visibility in search results with rich snippets for articles, products, and more.
Error Detection
Identify missing required properties and fix validation errors to ensure proper indexing.
The Schema Markup Validator helps you understand how search engines see your structured data. By analyzing a URL or raw JSON-LD, it highlights errors, warnings and missing fields that may prevent your pages from being eligible for rich results.
Instead of manually reading JSON-LD or microdata in the source, you get a clear, human-readable report you can share with developers, SEO teams and stakeholders.
What the Schema Markup Validator does
This tool inspects your structured data implementation and checks it against schema.org types and common search engine requirements.
It can:
Detect JSON-LD, microdata and RDFa structured data on a page
Parse multiple schema types on a single URL (for example
Article,Product,BreadcrumbList,FAQPage,Organization)Highlight syntax errors and invalid property values
Surface missing required and recommended fields for rich result eligibility
The result is a detailed breakdown of what your schema is telling search engines and what you need to fix.
Why schema markup matters for SEO
Structured data does not guarantee rankings, but it strongly influences how your pages can appear in search results.
Well-implemented schema can:
Unlock rich results (stars, prices, FAQ dropdowns, breadcrumbs, sitelinks, etc.)
Improve click-through rates by making snippets more informative and visual
Help search engines understand your content type, entity relationships and context
Support features like Knowledge Panels, carousels and enhanced product listings
On the other hand, broken or misleading markup can cause validation errors, manual actions or loss of rich results. The Schema Markup Validator helps you keep your implementation clean and compliant.
What this tool helps you identify
By running a URL or JSON-LD snippet through the Schema Markup Validator, you can quickly see:
Whether your structured data is valid JSON and follows schema.org syntax
Which schema types are detected on the page and how they connect to each other
Errors that break the markup entirely (missing required fields, invalid types, malformed JSON)
Warnings and missing recommended properties that may reduce eligibility for search features
Conflicting or duplicate schema types that send mixed signals to search engines
This visibility makes it easier to prioritize fixes that will have the biggest impact on your SERP appearance.
How to use the Schema Markup Validator
Enter a URL you want to analyze, or paste your JSON-LD snippet directly into the tool.
Start the validation to let the tool fetch and parse all structured data on the page (or in your snippet).
Review the list of detected schema types and their key properties.
Check the errors and warnings section to understand what is invalid, missing or risky.
Apply fixes in your CMS, template or tag manager, then re-run the test to confirm that the issues are resolved.
You can repeat this for templates such as product pages, articles, recipes, events, local business pages, FAQs and more.
Interpreting the results
When reading the report, focus on three layers:
Errors – Issues that make your structured data invalid or unusable (for example, missing required properties, invalid JSON, wrong data types). These should be fixed first.
Warnings – Missing recommended properties or non-critical issues. They may not block rich results entirely, but fixing them often improves eligibility and robustness.
Coverage – Whether all key templates and entities you care about (products, organization, local branches, blog posts) are covered with appropriate schema.
If a page has multiple schema types, make sure that the main entity of the page is clearly identified and that nested entities (like Offer, AggregateRating, Review) are correctly linked.
Best practices for schema implementation
Use the Schema Markup Validator alongside these structured data best practices:
Mark up the primary content of the page, not hidden or irrelevant information.
Use the most specific schema types available (
Productinstead ofThing,BlogPostinginstead of genericArticle, etc.).Keep real data and schema data consistent (prices, availability, ratings and dates should match the visible content).
Avoid spammy or misleading markup; only add schema for content that users can actually see on the page.
Implement schema at the template level, so new pages automatically inherit valid markup.
Re-test important templates regularly after theme, CMS or tracking changes.
Following these principles helps your structured data remain stable even as your site evolves.
When to use this tool in your workflow
The Schema Markup Validator is particularly useful when:
Setting up schema for a new site, template or content type
Debugging lost rich results or sudden changes in SERP appearance
Auditing third-party themes, plugins or apps that output structured data
Validating bulk schema updates implemented through a tag manager or custom script
Preparing for large content or e-commerce launches where rich results matter for CTR
By including this validator in your technical SEO and QA checklists, you can catch issues early and maintain high-quality structured data across your entire site.
FAQ
Does valid schema guarantee rich results?
No. Valid markup is a prerequisite, not a guarantee. Search engines also consider content quality, eligibility guidelines and overall site trust signals when deciding whether to show rich results.
Can I mark up content that is not visible on the page?
You should not. Structured data should reflect the content users can see. Marking up hidden or non-existent content can be considered misleading and may result in manual actions.
Should I use JSON-LD, microdata or RDFa?
JSON-LD is generally preferred because it is easier to implement and maintain. However, the Schema Markup Validator can analyze any supported format, helping you keep all of them valid and consistent.