Why You Must Validate Schema Markup

A small error in your JSON-LD, a missing comma, an incorrect field name, or a mismatched value — can silently prevent Google from reading your schema entirely. You won't get an error message on your website. The page will look perfectly normal. But the rich results you expected will simply never appear.

This is why validation is not optional. Every piece of schema markup you add should be validated before publishing and monitored regularly after. Google's tools make this straightforward, and the process takes under 5 minutes per page.

â„šī¸
Three-layer validation: The most thorough approach uses three tools in sequence: Schemify Validator (code-level check), Google's Rich Results Test (rich result eligibility), and Google Search Console (ongoing monitoring). This guide covers all three.

The 3 Tools You Need

✅
Schemify Validator
Instant JSON-LD validation without a live URL. Checks syntax, detects schema type, and identifies missing required fields.
Open Validator →
🔍
Google Rich Results Test
Google's official tool. Tests live URLs or raw code to confirm rich result eligibility. The definitive source for what Google will show.
Open Tool →
📊
Google Search Console
Ongoing monitoring for all schema on your live site. Shows errors, warnings, and valid items across every page updated weekly.
Open Console →

Step 1: Validate with Schemify Validator (Before Publishing)

The first validation step happens before your page is live. Use the Schemify Validator to check your JSON-LD code for errors instantly; no URL needed.

1
Generate your schema markup

Use any Schemify generator to create your JSON-LD. Fill in the form fields and click Generate Schema. Copy the output using the Copy button.

2
Paste into the Schemify Validator

Go to the Schemify Schema Validator and paste your JSON-LD into the text area, including the script tags if you copied them. Click Validate Schema.

The validator will instantly show you:

  • Whether your JSON syntax is valid
  • Which schema type was detected
  • All fields present in your schema (shown in green)
  • Any missing required fields (shown in yellow)
  • Specific error messages with explanations
3
Fix any errors before continuing

If the validator shows errors, fix them before moving on. Go back to the relevant Schemify generator, correct the fields, regenerate the schema, and re-validate. Only proceed to the next step when the Schemify Validator shows a green "Schema is Valid" result.

Validate your schema now for free

Instant JSON-LD validation: no URL required, no signup needed

Open Schemify Validator →

Step 2: Test with Google's Rich Results Test (After Publishing)

Once your page is live, use Google's official Rich Results Test to confirm Google can read your schema and that it qualifies for rich results. This is the most important validation step for rich result eligibility.

1
Open Google's Rich Results Test

Go to search.google.com/test/rich-results. You can test two ways:

  • URL tab: Enter your live page URL. Google fetches and analyses the page
  • Code tab: Paste your JSON-LD directly as useful before publishing
2
Understand the results

Google's Rich Results Test shows one of three outcomes:

Page is eligible for rich results. Your schema is valid, and Google can generate rich results from it. This is the outcome you want. Note that eligible does not guarantee rich results will appear; Google still decides based on content quality and relevance.
Page is not eligible for rich results with warnings. Your schema has warnings. Warnings don't prevent rich results but may limit them. Common warnings include missing recommended fields like images or descriptions. Fix warnings to maximise your rich result potential.
Page is not eligible for rich results with errors. Your schema has critical errors that prevent rich results. The error list tells you exactly what's wrong. Fix each error, republish your page, and re-test.
3
Fix errors and re-test

For each error shown, click on it to see the full error message. Common errors include:

  • Missing field "name": The name property is required for this schema type
  • Either "offers," "review," or "aggregateRating" should be specified. The Product schema needs at least one of these
  • Missing field "author": Article/BlogPosting schema requires an author
  • Invalid value in field "datePublished". Date must be in ISO 8601 format (YYYY-MM-DD)

Fix each error, update your page, and run the test again. Repeat until you see the green "eligible for rich results" message.

💡
Pro tip: Use the "Code" tab in Rich Results Test to test schema before your page is live. This lets you catch errors during development rather than after publishing to your live site.

Step 3: Monitor with Google Search Console (Ongoing)

After your page is live and validated, Google Search Console becomes your ongoing monitoring dashboard. It shows schema performance across your entire site, including errors that appear after Google recrawls your pages.

1
Access the Enhancements section
  1. Log in to Google Search Console
  2. Select your property (website)
  3. In the left sidebar, scroll down to Enhancements
  4. You'll see a list of rich result types detected on your site FAQs, products, articles, events, etc.
  5. Click any type to see its detailed report
2
Understand the Enhancement report

Each Enhancement report shows three categories of pages:

Valid: Pages with valid schema that are eligible for rich results. This is what you want all pages to show.
Valid with warnings: Pages with valid schema but missing recommended fields. Rich results may still appear but could be limited.
Error: Pages with schema errors that prevent rich results. Click the error to see which pages are affected and what the specific issue is.
3
Fix errors and request re-indexing

When you fix a schema error and republish a page, you can ask Google to recrawl it immediately:

  1. In Search Console, go to the URL Inspection tool (top of left sidebar)
  2. Enter the URL of the page you fixed
  3. Click "Request Indexing"
  4. Google will recrawl the page within hours and update your Enhancement report

You can also go back to the enhancement report, and click "Validate Fix" on any error row.This prompts Google to recheck all affected pages at once.

Bonus: Schema.org Validator

For the most technically thorough validation, use the Schema.org Validator at validator.schema.org. This tool checks your schema against the full Schema.org specification, which is broader than Google's Rich Results requirements.

ToolWhat it ChecksNeeds Live URL?Best For
Schemify ValidatorJSON syntax + required fieldsNoBefore publishing
Google Rich Results TestGoogle rich result eligibilityOptionalAfter publishing
Google Search ConsoleSitewide ongoing monitoringYesOngoing
Schema.org ValidatorFull Schema.org spec complianceOptionalDeep validation

Troubleshooting: Schema Valid But No Rich Results

This is the most common frustration with schema markup. Your schema passes all validation tests but rich results still don't appear in Google. Here are the most common reasons and fixes:

  • Google hasn't recrawled your page yet. Rich results typically appear 1–4 weeks after Google recrawls a page. Submit your URL in Search Console's URL Inspection tool to speed this up.
  • Your page has low authority. Google prioritises showing rich results for pages with established credibility. Build backlinks and improve your site's overall authority to increase eligibility.
  • Content quality is too low. Google's Helpful Content guidelines apply to rich results too. Pages with thin, low-quality content are less likely to be shown with enhanced listings.
  • Schema doesn't match visible content. Google cross-checks schema against page content. If your FAQ schema has different questions than what's visible on the page, Google will suppress the rich result.
  • The query doesn't trigger rich results. Not all searches show rich results even for eligible pages. Test your page for multiple relevant queries to see if rich results appear.
  • Your schema type doesn't support rich results. Some schema types (like Person, Organization, WebSite) provide entity signals but don't generate visual rich results in search. Check which types are eligible on Google's rich results overview page.
âš ī¸
Important: Never add fake or misleading schema to try to force rich results. Google's Rich Results Test passing is not a guarantee of rich results, and manipulative schema can lead to manual penalties that are far harder to recover from than simply waiting for valid schema to be recognised.

Generate valid schema with one click

15+ free generators: every schema comes out valid, every time

Browse All Generators →

Frequently Asked Questions

Use Google's Rich Results Test at search.google.com/test/rich-results. You can test by entering your live page URL or by pasting your JSON-LD code directly in the Code tab. Google will show you whether your schema is valid and which rich results it qualifies for usually within seconds.
Google's Rich Results Test checks whether your schema qualifies specifically for Google's rich result features, FAQ dropdowns, star ratings, recipe carousels, etc. The Schema.org validator checks whether your schema follows the broader Schema.org specification. A schema can pass Schema.org validation but still not qualify for Google rich results if it's missing Google-specific required fields.
A valid schema does not guarantee rich results. Google also considers page authority, content quality, whether schema accurately reflects visible content, and whether the search query is one that triggers rich results for that schema type. Rich results typically appear 1–4 weeks after Google recrawls the page. Submit your URL in Search Console to speed this up.
Use Google Search Console. In the left sidebar, scroll to the Enhancements section; you'll see reports for each rich result type detected on your site. Each report shows valid pages, warnings, and errors. Click any error to see which specific pages are affected and what needs to be fixed.
After you update your schema and republish a page, Google needs to recrawl it before the changes are reflected. This typically takes 1–4 weeks organically. To speed it up, use the URL Inspection tool in Google Search Console and click "Request Indexing"; this usually triggers a recrawl within hours to a few days.