What this check inspects
Shipwork fetches the page and extracts every application/ld+json block. It parses each one, walks every node that declares a type, including nodes nested under @graph or under ProductGroup hasVariant, and checks the recommended properties for known types such as Product, Offer, Article, FAQPage, BreadcrumbList and Organization. It reports blocks that are not valid JSON, blocks with no @context, and missing recommended properties.
What a failure means
No JSON-LD blocks at all is an error: there is nothing for a machine to read. An unparseable block is an error and it takes the whole block with it, so a Product can vanish while the page still shows a price. Missing recommended properties are warnings, and repeated types outside the ones that repeat by design are informational.
How to fix it
- View the page source, not the inspector, and search for application/ld+json. The inspector shows markup injected after scripts run, which a raw fetch never sees.
- Validate the JSON. One trailing comma or a stray character makes an entire block invisible.
- Read the type inside the block. A Product should carry name, and each Offer should carry price and priceCurrency.
- If you use ProductGroup, make sure each variant under hasVariant carries its own offer rather than relying on the parent.
A typical failure, worked through
The setupA store hand-edits its product template and adds a second JSON-LD block for returns. The edit leaves a trailing comma in the first block.
What the check reportsThe check reports that block 1 is not valid JSON and no Product node is found, even though the page visibly shows a price and the block looks almost correct.
The pointJSON is all or nothing per block. One character failure removes the entire structured data, and nothing on the rendered page gives it away.