Schema validator
Enter a URL to extract its JSON-LD structured data and check each block parses correctly.
Run a full graded audit for the whole site.
Enter a URL to extract its JSON-LD structured data and check each block parses correctly.
A schema validator checks JSON-LD structured data on any web page to spot syntax errors and missing properties that prevent rich results. Enter your page URL and instantly see what markup was found, what's valid, what's broken, and what's needed for Google search features.
Schema validation is the process of checking structured data markup for correctness and completeness. Structured data uses standardized vocabularies like Schema.org to label information in HTML so search engines understand what your content means. When a search engine crawls your page, it looks for this markup and uses it to enable rich results—those enhanced search listings showing ratings, prices, recipes, FAQs, and other detailed previews.
A validator extracts the JSON-LD schema markup from your page's HTML and tests it against the Schema.org specification. It checks for two critical things: whether the markup is syntactically valid (properly formatted JSON with correct brackets, quotes, and commas), and whether it includes the properties search engines expect for the type of content you're marking up.
Schema.org is maintained by a consortium including Google, Microsoft, Yandex, and Apple. It defines hundreds of types—Article, Product, Organization, Event, Recipe, LocalBusiness, and many more. When Google says 'your page is eligible for rich results,' it means your schema passed structural validation AND included the required properties Google specified for that rich result type. Without valid schema, your page stays as plain text in search results.
The validator checks what's on your live page right now. If you've recently published updates, they need to be live on your server for the validator to see them. The tool reads the HTML your server sends on the initial request, giving you immediate feedback on what's actually deployed.
Schema validators report several categories of problems. Understanding what each means helps you fix issues and qualify for rich results.
Schema.org has hundreds of types, but a few are most common for unlocking Google rich results:
| Type | When to Use | Rich Result It Powers |
|---|---|---|
| Article | Blog posts, news articles, guides, tutorials | Article preview with headline, date published, and image |
| Product | E-commerce listings, product pages | Shopping results with star ratings, price, and availability |
| Organization | Company homepage, corporate footer | Knowledge panel candidate, company logo in search |
| LocalBusiness | Retail locations, service providers | Local pack results with address, phone number, hours |
| Recipe | Cooking content, food blogs | Recipe card with cook time, servings, ratings, and ingredients |
| Event | Conferences, concerts, webinars | Event listing with date, location, and ticket information |
| FAQPage | FAQ sections on any page | FAQ accordion expanding answers directly in search results |
| BreadcrumbList | Navigation hierarchy, site structure | Breadcrumb trail shown in search snippet for context |
| VideoObject | Embedded or hosted videos | Video rich results with duration, thumbnail, and description |
| ReviewRating | Product reviews, rating content | Star ratings displayed in search results for products or articles |
Google's supported schema types and their required properties change over time. The validator will check any type against the official Schema.org specification, but to confirm your schema qualifies for a specific Google rich result, check Google's structured data gallery or test with Google's own Rich Results Test.
When you run the validator, the report shows each schema block discovered on the page, its type, and every property it contains. A single page can have multiple schema items. A homepage might have Organization schema (company information), LocalBusiness schema (address and hours), and Article schema (featured blog post)—the validator lists all of them so you can review the complete markup.
Parse errors appear at the top of results and are critical. They indicate malformed JSON—missing commas between properties, unclosed braces, quote characters breaking the structure. When JSON is malformed, search engines cannot read it at all, so no properties can be evaluated. These must be fixed first. Common fixes: add missing commas, close all braces properly (check that every { has a matching }), ensure strings are wrapped in double quotes.
Missing property warnings appear after parse errors are resolved. Your schema might be valid JSON-LD but incomplete for Google's rich result requirements. For example, a Product schema without a price property is readable but incomplete. The validator shows you exactly which properties are absent so you can add them to your schema.
The report also shows all properties that ARE present, so you can verify they have the right values and formats. This helps catch type mismatches (a price listed as text instead of a number) or format errors (a date in the wrong format) that might not trigger a parsing error but still break rich results.
Google offers its own Rich Results Test, which is the official tool for checking if your page qualifies for specific Google search features. This validator and Google's test serve different purposes. This validator is a general Schema.org checker—it validates markup against the full specification without Google-specific rules. It's fast and works instantly with no account required.
Google's Rich Results Test is narrower and more prescriptive. It tells you whether your page qualifies for a specific Google search feature and shows you a preview of what your rich result will look like. It's the authority for Google eligibility. Use this validator first for general schema health: Is the markup syntactically correct? Are common properties present? Use Google's Rich Results Test after validation to confirm your schema qualifies for the specific features you're targeting.
Think of it this way: this validator confirms your schema is well-formed and follows Schema.org standards. Google's test confirms it's eligible for Google's specific features. Both are useful—start with this one for quick feedback, then graduate to Google's test before assuming rich results will appear.
Once the validator reports errors, fix them in your HTML or template and run validation again to confirm the fixes worked. When parse errors are resolved and missing properties are added, re-validate to see a clean report.
After validation passes, use Google's Rich Results Test to check eligibility for the specific rich result type you want. If Google's test reports issues your validator didn't catch, it's usually because Google has stricter requirements than Schema.org—for example, requiring a specific image size or format.
Make schema validation part of your regular QA process. After redesigns, CMS migrations, template changes, or updating your site generator, validate again. Broken schema often indicates a code issue elsewhere. Finally, once your schema is live and valid, monitor it occasionally—especially if you use a page builder or plugin that generates schema, since updates can sometimes break markup.
A schema validator is a tool that checks the structured data markup on web pages for correctness and completeness. It extracts JSON-LD schema from your page's HTML and verifies whether the markup is valid JSON, uses correct Schema.org types and properties, and includes the properties search engines need to display rich results. It reports parse errors (malformed JSON) and missing properties immediately.
Enter your page's full URL into the validator form. The tool fetches your live page, extracts any JSON-LD schema markup it contains, and checks it for errors. The report shows all schema items found, any syntax errors, and which properties are missing. If errors appear, fix them in your HTML source code and validate again to confirm the fixes worked.
Enter the website's URL into this validator and it will extract and display all schema markup found on that page. The report shows each schema item, its type, and its properties. If no schema appears, the validator confirms no markup was found. You can also manually view page source (Ctrl+F or Cmd+F for 'schema'), but a validator automates this and shows you what's valid versus what's broken.
A validation error means your schema markup has a problem. Parse errors mean the JSON is malformed—usually a missing comma, unclosed bracket, or broken quote—and search engines cannot read it at all. Missing property errors mean your markup is readable but incomplete for Google rich results eligibility. Both require fixing, but parse errors are critical and must be addressed first since they prevent any markup from being read.