How to fix schema errors and warnings

1. 01

   Identify the validator

   Separate JSON parsing, Schema.org vocabulary, and consumer-specific reports.

2. 02

   Reproduce the rendered markup

   Inspect the exact production page and script.

3. 03

   Fix critical syntax first

   Resolve invalid JSON, missing required values, wrong value types, and inaccessible pages.

4. 04

   Review warnings for completeness

   Add recommended values only when accurate and supported.

5. 05

   Retest after the template fix

   Confirm other pages using the same component were not damaged.

Validate the final production output in layers: JSON syntax, Schema.org vocabulary, current feature-specific requirements, visible content, and crawl access.

• Define the purpose and expected result of schema errors and warnings.
• Capture the current state using visible entities, page purpose, JSON-LD graphs, identifiers, relationships, required properties, and consumer-specific eligibility.
• Identify the source template, component, plugin, content owner, and release path that controls the output.
• Prepare a test case, approval path, backup or rollback method, and post-release verification plan.

• Parse the deployed json-ld, validate the graph, compare it with visible content, and test any target consumer requirements.
• Check representative page types and edge cases instead of confirming only the example used during implementation.
• Confirm the change did not create publishing properties that are unsupported, hidden, stale, or inconsistent with visible content.
• Record the implementation date, owner, release reference, evidence, and next review trigger.