When to use this check
Identify the page’s actual subject, then choose a type and verify that you have accurate property values. Do not choose schema solely for the appearance of a desired search result.
Know what you are checking.
Structured data describes content in a machine-readable form. JSON-LD can identify an article, product or breadcrumb hierarchy, but its claims must match the actual page.
A practical example
{"@context":"https://schema.org","@type":"Article","headline":"How to check a canonical URL","inLanguage":"en"}A common mistake
Valid JSON does not establish eligibility. Schema.org includes types without corresponding Google rich results. Do not invent reviews, authors or awards to fill fields.
Understand the result. Make the right change.
How to choose the right structured data type
A service page does not become a product offer because you want a price in search results. Identify the page’s main subject before choosing its schema.
- Describe the actual article and author on an article page.
- Make BreadcrumbList reflect the navigation hierarchy.
- For a product, use the genuine offer, currency and availability.
How to check syntax, accuracy and rich result eligibility
Valid JSON does not establish factual accuracy or eligibility for a particular rich result. Each question needs its own check.
- Use a parser to check syntax, including commas and quotes.
- Compare declared properties with the visible page content.
- Check the intended feature’s own policies and required properties.
How to fix conflicting markup from themes and plugins
A theme may emit one Product while a plugin emits another with an old price. Multiple declarations are not automatically wrong, but contradictory properties need a shared source of truth.
- Inspect every JSON-LD block and any other markup formats.
- Derive price and availability from the data used by the visible offer.
- After an update, check the public response outside the administration cache.
Why valid markup does not guarantee a rich result
A successful test does not order a rich result. Google decides how to display supported features; invented reviews are never a legitimate way to complete fields.
- Fix errors relevant to the type you actually use.
- Add a recommended property only when you have an accurate value.
- After deployment, monitor the relevant Search Console report where available.
Primary reference: developers.google.com ↗
Frequently asked questions
Why did valid JSON-LD not produce a rich result?
Valid syntax, eligibility for a supported feature, and actual display are separate outcomes. Check Google’s requirements for the specific feature and match visible content. Never invent ratings, prices, or authors. Adding FAQ markup to an ordinary commercial website does not establish eligibility for an FAQ rich result.
When the task is complete
JSON-LD parses, describes the actual page, and agrees with visible information. Use the appropriate test for supported features; Google still decides whether to display them.