Expected page has no JSON-LD block
ShipReady found no supported JSON-LD script block on a route its route heuristic expects to have structured data.
Why it matters
This is a static markup signal that helps review how the page is presented.
How ShipReady detects it
What it inspects
ShipReady searches eligible HTML for a script with type=application/ld+json and applies its route expectation helper.
What triggers a finding
The block is absent and the route is in ShipReady's expected structured-data set.
What the evidence shows
The inspected expected page lacked ShipReady's JSON-LD script pattern.
Limits of this check
ShipReady does not validate JSON-LD contents, test schema eligibility, rich results, or AI citations.
How to fix it
Add route-appropriate JSON-LD
For the affected route, add a JSON-LD script block only when a schema type accurately describes that page. Keep its data consistent with the visible content; ShipReady does not select a type or validate the schema contents.
How to verify the change
Inspect the returned JSON-LD block
Fetch the affected route and confirm its returned HTML contains the intended application/ld+json script block. Validate the authored JSON and schema separately.
Expected: The returned HTML contains the intended JSON-LD script block.