JSON-LD without @context or @type

Blocks written by hand from an example that was cut short, or plugins that output a partial object.

• Start every block with "@context": "https://schema.org" and the "@type" of the thing it describes — Product, Article, Organization.
• If a plugin writes the block, update or reconfigure it rather than editing its output by hand.
• Test the page again in the Schema.org validator; it should list the item with its type.

Open the JSON-LD in the page source and check its first lines: "@context" and "@type" should be there.

Warning JSON-LD without @context or @type.

The block exists but does not say what it describes, so it is ignored. (An example shop; the numbers are illustrative.)

STRUCT-003 is a warning in the structured data category, and weighs moderately in that category’s score. When it appears on many pages built from the same template, the report shows it once, with the number of pages it covers — because one change in the template fixes all of them.

If the finding is deliberate on your site, it can be accepted as intentional in the report. It then leaves the list and the score, and comes back on its own if what it shows changes.

• The page has no structured data · STRUCT-001
• Invalid JSON-LD · STRUCT-002
• Product without price or availability · STRUCT-004
• Article without headline or date · STRUCT-005
• Home page without Organization · STRUCT-006
• Deep page without a breadcrumb · STRUCT-007

A Trakis audit runs this check and the other 65 on your site, and tells you on how many pages each one sits. Or go back to all the rules.