How to Test and Validate Schema Markup (Free Tools and Common Errors)
Learn how to effectively test and validate your schema markup using free tools and discover common errors with our comprehensive schema markup validator guide.
schema markup validator | Updated October 2026 | hyperank Editorial Team | 30-60 minutes | Beginner
What You'll Learn
To test and validate schema markup, run the page through Google's Rich Results Test to see which Google rich results it qualifies for, then through the Schema Markup Validator at validator.schema.org to check every schema.org type, including ones Google doesn't use for rich results. Fix errors first, since they block rich results, then decide which warnings are worth fixing. This guide, How to Test and Validate Schema Markup (Free Tools and Common Errors), covers both free tools, how to check live pages and competitors' pages, and the errors you're most likely to see.
- Pick the right schema markup validator: Know when to use Google's tool and when to use Schema.org's.
- Test live pages and code: Check published URLs and snippets before you deploy them.
- Read the results: Separate errors that block rich results from warnings that don't.
- Fix common problems: Resolve the structured data errors that come up most often.
Prerequisites: A page with structured data (or a JSON-LD snippet), a browser and, for site-wide checks, access to Google Search Console.
Why Schema Markup Testing Matters in 2026
Schema markup is structured data, usually in JSON-LD format, that describes a page's content to search engines: a product's price, an article's author, a business's address. When it's broken, Google ignores it, and you lose eligibility for rich results such as product stars, prices and event dates.
Testing matters more now because Google's support keeps changing. In June 2025, Google announced it was phasing out several structured data features, including Book Actions, Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement and Vehicle Listing. FAQ rich results, already limited to government and health sites since 2023, stopped appearing in Google Search in May 2026. Markup that "worked" a year ago may no longer produce anything, and only testing tells you what still counts.
Structured data also helps beyond Google's rich results. Clean, accurate markup gives other search engines and AI systems an unambiguous description of your products, prices and organization.
Key Takeaway: Valid schema is the price of entry for rich results, and Google's list of supported types has shrunk, so test against today's rules.
The Process at a Glance
| Step | Action | Time | Outcome |
|---|---|---|---|
| 1 | Choose the two validators to use | 2 minutes | Know which tool answers which question |
| 2 | Compare Rich Results Test and validator | 5 minutes | Understand what each one checks |
| 3 | Check schema markup on a live page | 5-10 minutes per page | Detected items, errors and warnings listed |
| 4 | Check another website's schema | 5 minutes per page | See how competitors mark up pages |
| 5 | Sort errors from warnings | 10 minutes | A prioritized fix list |
| 6 | Fix the common schema errors | 15-30 minutes | Valid markup with no critical errors |
| 7 | Generate clean markup to start with | 10 minutes per template | Fewer errors on new pages |
Total time: About 30-60 minutes for a handful of key templates; site-wide fixes depend on how many templates you have.
Step 1: Choose the Two Validators to Use
What You're Doing
Most confusion about schema testing comes from using one tool to answer the other tool's question. Start by matching each schema markup checker to the question it actually answers.
How to Do It
- Use the Rich Results Test for Google: Google's Rich Results Test tells you which Google rich results a page can generate and flags problems with them. Google's own structured data guide recommends starting here.
- Use the Schema Markup Validator for everything else: The Schema Markup Validator checks all schema.org markup against the vocabulary, without Google-specific rules.
- Retire the old tool from your workflow: Google's Structured Data Testing Tool no longer exists in its old form; Google removed its Google-specific checks and moved it to validator.schema.org.
What Done Looks Like
Both tools are bookmarked, and you know that "Will Google show a rich result?" goes to the Rich Results Test while "Is my schema.org markup valid?" goes to the validator.
Step 2: Compare the Google Rich Results Test and the Schema.org Validator
What You're Doing
A clean result in one tool and silence in the other is normal, once you know what each covers. This comparison keeps you from misreading either.
How to Do It
| Feature | Google Rich Results Test | Schema Markup Validator |
|---|---|---|
| Main question | Can this page get Google rich results? | Is this schema.org markup valid? |
| Types checked | Only Google-supported rich result types | All schema.org types |
| Formats | JSON-LD, Microdata, RDFa | JSON-LD, Microdata, RDFa |
| Input | URL or code snippet | URL or code snippet |
| Rendering | Fetches as Google-InspectionTool, smartphone or desktop | Reads the fetched page or pasted code |
| Severity labels | Errors (invalid) and warnings (non-critical) | Errors and warnings against the vocabulary |
| Best for | Product, Article, Event, Recipe, Job Posting and other supported features | Organization, FAQPage, custom or less common types |
Common Mistakes
- Expecting FAQ results in Google's tool: Google ended FAQ rich results in May 2026 and removed FAQ support from the Rich Results Test, so check FAQPage markup in the Schema Markup Validator instead.
- Assuming "no items detected" means broken: The Rich Results Test only lists types Google supports; valid Organization markup may simply not appear there.
What Done Looks Like
You can explain why a page passes one tool and shows nothing in the other.
Step 3: Check Schema Markup on a Live Page
What You're Doing
Now put the tools to work on a real page. Test the version Google actually sees, including markup added by JavaScript, plugins or tag managers, because that's where surprises hide.
How to Do It
- Run the Rich Results Test: Paste the full URL, keep the default smartphone crawler and click Test URL.
- Read the summary: Note each "Detected structured data" item and whether it shows as valid, valid with warnings or invalid.
- Open the rendered HTML: Use "View tested page" to confirm the markup appears in the rendered code, which catches JavaScript that fails to run.
- Run the same URL in the validator: Check that every schema.org type parses, including ones Google doesn't use.
- Check site-wide in Search Console: In Google Search Console, the rich result reports under Enhancements show valid and invalid items across all pages of a type, and URL Inspection shows detected structured data for one URL.
Example
| Page | Rich Results Test | Validator | What it means |
|---|---|---|---|
| Product page | Product snippet: valid with 2 warnings | Product, Offer, Organization: no errors | Eligible; warnings are optional fields |
| Blog post | Article: invalid (missing headline) | Article: no errors | Valid schema.org, but fails a Google requirement |
| About page | No items detected | Organization: no errors | Fine; Organization isn't a rich result type here |
What Done Looks Like
For each key template, you've recorded which items Google detects, their status and whether the validator agrees.
Step 4: Check Another Website's Schema Markup
What You're Doing
Once your own pages are tested, borrow some ideas. Checking how competitors mark up similar pages is a quick way to see which properties you're leaving out.
How to Do It
- Test any public URL: Both tools accept pages you don't own, as long as they're publicly accessible.
- View the source: In your browser, open the page source and search for
application/ld+jsonto read the JSON-LD directly. - Compare properties: Note fields a competitor includes that you don't, such as
brand,aggregateRatingorshippingDetailson products. - Copy structure, not content: Use their markup as a pattern, but every value in yours must describe your own page.
Common Mistakes
- Copying markup for content you don't show: Google's structured data policies require markup to match what users can see on the page; marking up reviews or prices that aren't visible can lead to a manual action.
What Done Looks Like
You have a short list of properties worth adding, taken from two or three well-marked-up competitor pages.
Step 5: Sort Errors From Warnings and Fix in the Right Order
What You're Doing
A results screen full of yellow and red can look alarming, but only some of it matters. Google's Rich Results Test help explains that errors make structured data invalid, while warnings are non-critical and the item can still work.
How to Do It
- Fix all errors first: An error on a required property makes the item ineligible for that rich result.
- Triage warnings by value: A missing recommended property, such as
reviewon a product, won't block eligibility, but adding it can make the result richer. - Ignore warnings you can't support honestly: If you have no reviews, don't invent them to clear a warning.
- Fix templates, not pages: Most errors come from a shared template, so one fix resolves hundreds of URLs.
Example
| Issue | Type | Priority | Why |
|---|---|---|---|
| Missing field "name" on Product | Error | Fix now | Blocks the rich result |
| Invalid value in "priceCurrency" | Error | Fix now | Price can't be shown |
| Missing field "aggregateRating" | Warning | Fix if you have real ratings | Optional enhancement |
| Missing field "shippingDetails" | Warning | Fix soon for e-commerce | Adds useful detail to results |
What Done Looks Like
Your fix list is ordered: every error first, then the warnings you can fill with accurate data.
Step 6: Fix the Most Common Schema Errors
What You're Doing
The good news: most failed tests come down to a handful of formatting and missing-field errors, and each has a predictable fix.
How to Do It
- Unparsable structured data: Usually a JSON syntax problem, such as a missing comma, an extra trailing comma or unescaped quotation marks. Paste the JSON-LD into the validator to find the line.
- Missing required field: Add the property the error names, such as
headlineon Article ornameon Product, using Google's documentation for that feature. - Invalid date format: Use ISO 8601, for example
2026-10-19or2026-10-19T09:00:00-05:00. - Invalid price or currency: Use a plain number for
price(49.99, not "$49.99") and a three-letter code such as USD forpriceCurrency. - Product with no offer, review or rating: Google's product snippet needs at least one of
offers,revieworaggregateRating. - Markup missing after rendering: If the validator sees markup in your code but the Rich Results Test doesn't, the script that injects it may be blocked or failing; check the rendered HTML.
In practice, most "schema problems" are one broken template, a plugin conflict that outputs two Product blocks, or a price field that someone formatted for humans instead of machines.
What Done Looks Like
Re-testing shows no errors on your key templates, and Search Console's rich result reports start moving items from invalid to valid as Google recrawls.
Step 7: Generate Clean Markup to Start With
What You're Doing
The cheapest error is the one you never publish. Start new templates from valid JSON-LD instead of hand-typing it each time.
How to Do It
- Use a generator: hyperank's free schema markup generator builds JSON-LD for common types from a form.
- Validate before publishing: Paste the generated code into the Rich Results Test's Code tab and the Schema Markup Validator.
- Add it to the template: Place the JSON-LD in a
<script type="application/ld+json">tag in your page template, filled with dynamic values. - Re-test after launch: Test one live URL per template, then monitor Search Console.
What Done Looks Like
Each page template has validated JSON-LD, and new pages pass both tools on the first test.
What to Do After You Validate Your Schema
- Phase 1, monitor (weeks 1-4): Watch Search Console's rich result reports for new invalid items, especially after site or plugin updates.
- Phase 2, expand (months 1-3): Add supported types you're not using yet, such as Product shipping details or Organization markup on your homepage, and keep the rest of the page healthy with an on-page SEO checker.
- Phase 3, check how AI describes you (ongoing): Structured data gives machines clear facts, but AI answers still vary. hyperank helps brands see what AI says about them by aggregating daily insights from six major AI engines and capturing the qualitative answers and trends, not just rankings, so you know how your brand stacks up and what AI gets right or wrong, such as an outdated price. hyperank believes understanding and influencing how AI engines represent your brand is now critical, and it gives brands and agencies transparency and control over that AI-driven reputation.
Resources You'll Need
| Resource | Role | Status | Price |
|---|---|---|---|
| Google Rich Results Test | Check Google rich result eligibility | Required | Free |
| Schema Markup Validator | Validate all schema.org markup | Required | Free |
| Google Search Console | Site-wide rich result reports and URL Inspection | Recommended | Free |
| hyperank schema markup generator | Create valid JSON-LD to start from | Optional | Free |
| hyperank | Track what AI engines say about your brand | Optional | Plans quoted per team |
Troubleshooting Common Issues
The Rich Results Test says "No items detected"
Likely cause: The page uses a type Google doesn't support for rich results, the markup is injected by a script that didn't run, or the markup is missing. Fix: Run the URL in the Schema Markup Validator; if it finds the markup, the type is simply unsupported or rendering failed.
The test passes but no rich result appears
Likely cause: Valid markup makes a page eligible, not guaranteed; Google decides when to show rich results. Fix: Make sure the page is indexed, the markup matches visible content and the feature is still supported.
Search Console shows errors the test doesn't
Likely cause: Reports reflect the last crawl, which may be older than your fix. Fix: Use "Validate fix" in the report and wait for Google to recrawl.
The tool can't fetch the page
Likely cause: The page is behind a login, firewall or robots.txt block. Fix: Test the code snippet directly, or allow Google-InspectionTool to reach the page.
Conclusion
Key Takeaways
- Outcome: Use the Rich Results Test for Google eligibility and the Schema Markup Validator for full schema.org validity.
- Key insight: Errors block rich results; warnings don't. Fix templates, not individual pages.
- Next action: Test one URL from each page template today and log every error.
FAQ
How do I test and validate schema markup with free tools, and what are the common errors?
Test the page in Google's Rich Results Test to see which Google rich results it qualifies for, then in the Schema Markup Validator at validator.schema.org to check all schema.org markup. Both are free and accept a URL or a code snippet. Fix errors first, since they block rich results. Common errors are unparsable JSON, missing required fields like headline or name, non-ISO dates, prices with currency symbols and products without offers, reviews or ratings.
What is the best schema markup validator?
Use two: Google's Rich Results Test for Google rich result eligibility and the Schema Markup Validator for general schema.org validity. Neither replaces the other.
How do I check schema markup on my website?
Test key URLs in the Rich Results Test and the Schema Markup Validator, then use Search Console's rich result reports to see valid and invalid items across your whole site.
How do I check the schema markup of another website?
Paste its public URL into either tool, or view the page source and search for application/ld+json to read its JSON-LD.
What happened to Google's Structured Data Testing Tool?
Google removed its Google-specific checks and moved the tool to validator.schema.org as the Schema Markup Validator. For Google features, use the Rich Results Test.
Do schema warnings matter?
Warnings are non-critical: the item can still be eligible for rich results. Fix them when you can supply accurate data, such as real ratings or shipping details.
Can I still test FAQ schema in the Rich Results Test?
No. Google stopped showing FAQ rich results in May 2026 and removed FAQ support from the tool, so use the Schema Markup Validator to check FAQPage markup.
Methodology: Tool behavior, severity labels and supported features are based on Google Search Central documentation, the Rich Results Test help page and Google's June 2025 announcement on simplifying search results, plus Schema.org's validator, checked in October 2026. Google changes supported rich result types periodically; confirm in its documentation before relying on a feature.
See where your brand stands
How six AI engines describe you, next to your competitors. About two minutes.