Result model

Schema Checker result model

A schema report should explain whether JSON-LD exists, whether it parses, and which content types are declared.

Severity ladder

Every report separates blockers, warnings, and healthy confirmations.

This is the reporting model behind the live tools, so operators know what to fix first instead of reading a flat list.

Critical

Fix these before relying on the current setup for monetization, indexing, or language targeting.

Warning

The page or file is reachable, but there is still technical risk worth reducing quickly.

Healthy

Public signals look aligned. Keep this state stable while you scale content or ads.

Signals included

  • Presence of JSON-LD blocks in the HTML
  • Parse validity and readable structure
  • Detected `@type` values and missing-schema warnings

Operator actions

  • Match the structured data to visible page content.
  • Fix invalid JSON or mixed objects inside JSON-LD blocks.
  • Add the most relevant schema type instead of generic noise.
01

Run the public check

Use the live checker to see what is publicly reachable and technically visible today.

02

Fix the highest severity first

The result model is intentionally ordered so blockers come before informational clean-up.

03

Re-run after deployment

These tools are built for before-and-after verification, not one-time screenshots.