Repair workflow
- Choose a schema type supported by the visible content.
- Include only real properties that the page shows or substantiates.
- Keep JSON syntax valid and stable.
- Validate eligibility with the relevant official testing tool.
Issue library · 6 structured data checks
JSON-LD and structured data issues
Keep structured data valid, visible, truthful, and relevant to the page content people can actually access.
Direct answer
Structured data should parse correctly and describe visible page content using a supported type. It can clarify meaning and eligibility, but it cannot guarantee a rich result or ranking.
Why this area matters
Invalid or unsupported markup creates false confidence. Markup that disagrees with the page can also create trust and eligibility problems.
Verification checklist
- Parse every JSON-LD block.
- Compare properties against visible content.
- Use Google Rich Results Test where the type is supported.
Exact findings explained
FAQ markup does not match visible questions
FAQPage schema exists without enough visible question headings.
What to do
Make the questions and answers visible and materially consistent, or remove unsupported FAQ markup.
How to verify
Compare every structured question and answer with the rendered page.
Invalid JSON-LD
At least one structured-data block cannot be parsed.
What to do
Correct JSON syntax before reviewing schema meaning or eligibility.
How to verify
Parse the exact rendered block and confirm no syntax errors remain.
No JSON-LD detected
The page has no valid JSON-LD block; this is only an opportunity when a relevant supported type exists.
What to do
Add structured data only when it truthfully describes visible content and serves a documented use.
How to verify
Validate the type and confirm every important property is supported by the page.
Structured data parses
The JSON-LD syntax is valid, but syntax alone does not prove accuracy or rich-result eligibility.
What to do
Review the detected types, required properties, visible content, and official documentation.
How to verify
Run the appropriate validator and manually compare markup with the page.
Long-form page lacks Article-family markup
The page has schema but no Article, BlogPosting, or NewsArticle type.
What to do
Use an Article-family type only when the page is genuinely editorial and required properties are real.
How to verify
Confirm visible headline, author, and date details match the markup.
Deep page lacks breadcrumb markup
A nested URL has no BreadcrumbList type.
What to do
Add visible breadcrumbs and matching markup when hierarchy helps the reader navigate.
How to verify
Click every breadcrumb and compare its visible labels and URLs with JSON-LD.