Guide

Structured data validation: test JSON-LD beyond syntax

About 3 min read Time to do it: 30-60 min Updated
Quick answerStructured data must be syntactically valid, describe the visible page and meet the requirements of the search feature you want to qualify for. Passing a parser is only the first check.
On this page
  1. When to use this guide
  2. Why this matters for SEO
  3. What can go wrong
  4. Step-by-step
  5. How to confirm it worked
  6. Mistakes to avoid
  7. Tools to use
  8. FAQ
  9. Related guides

Why this matters for SEO

Structured data must be syntactically valid, describe the visible page and meet the requirements of the search feature you want to qualify for. Passing a parser is only the first check.

Search visibility depends on several systems agreeing: the page must be reachable, discoverable, technically eligible to be indexed, useful for the query, and supported by a clear internal site structure. Fixing one symptom while another system is blocking the page can produce little or no improvement.

Use this guide as a focused workflow rather than a checklist to complete blindly. Confirm the actual page and response first, make the smallest defensible change, then re-test the same evidence after deployment.

When to use this guide

  • JSON-LD parses but no rich result appears.
  • A structured data report flags missing or invalid properties.

What can go wrong

  • The markup describes content not visible to users.
  • A type or property is used outside its supported meaning or eligibility rules.
Diagnosis order

Check access and HTTP status first, then robots and indexability directives, canonicalization, content/template quality, internal links and performance. This order prevents a low-priority content edit from hiding a technical blocker.

Step-by-step

  1. Identify the page and intended feature

    Choose the page type and confirm that the search feature is currently supported for that content.

  2. Validate JSON syntax

    Check commas, quotes, arrays, objects and data types. Keep JSON-LD valid JSON.

  3. Validate schema vocabulary

    Confirm type and property names against Schema.org definitions.

  4. Check search-engine feature rules

    Review the current Google documentation for required and recommended fields, content policies and eligibility.

  5. Compare markup with visible content

    Ensure names, dates, offers, ratings and other facts are accurate and present where required.

  6. Deploy and monitor

    Use the relevant rich-result testing and Search Console enhancement reports where available. Monitor after recrawl.

How to confirm it worked

The markup parses, uses appropriate vocabulary, matches visible page facts and satisfies the current feature-specific requirements. Eligibility is not a guarantee of display.

Verification should use the same URL and comparable conditions as the original test. Check the HTTP response, rendered/source markup and the relevant Google Search Console report where applicable. A successful technical change does not guarantee immediate indexing; crawling and indexing can take time and Google may still choose not to index a page it considers redundant or low quality.

Mistakes to avoid

  • Adding fake review markup to improve appearance.
  • Assuming Schema.org validity equals Google rich-result eligibility.
  • Leaving stale structured data after a page or product changes.

Tools to use

Schema Markup Generator

FAQ

Why does valid schema not show a rich result?

The page may not qualify for the feature, may not meet content policies, may not be selected, or may not yet have been recrawled. Valid syntax alone is insufficient.

Check your own site now. The free SeOMeter tools run these checks on your own URLs, no sign-up needed.

Open the SEO tools

Was something unclear or out of date? Tell us and we will improve this guide. SEO checks are diagnostic guidance, not a promise of rankings, traffic or indexing.