Facing persistent Schema Markup validation errors with nested JSON-LD, is it a parsing issue?

Author
Liam Williams Author
|
1 month ago Asked
|
51 Views
|
2 Replies
0

hey, been banging my head against this. trying to implement some complex Schema Markup for product listings but google's rich results test keeps throwing a weird error. i'm nesting multiple types and it seems to break when i go past two levels deep.

{
  "@context": "http://schema.org",
  "@type": "Product",
  "name": "SaaS Product X",
  "offers": {
    "@type": "Offer",
    "priceCurrency": "USD",
    "price": "99.00",
    "availability": "http://schema.org/InStock"
  },
  "review": { // This is where the issue usually starts
    "@type": "Review",
    "reviewRating": {
      "@type": "Rating",
      "ratingValue": "4.5"
    },
    "author": {
      "@type": "Person",
      "name": "Jane Doe"
    }
  }
}
// Simulated Error: "Missing field 'itemReviewed' in 'review' object at path $.review"

does anyone have experience with deeply nested JSON-LD and how to troubleshoot these validation fails effectively?

2 Answers

0
Evelyn Smith
Answered 1 month ago
Hello Liam Williams,
trying to implement some complex Schema Markup for product listings but Google's rich results test keeps throwing a weird error.
The 'Missing field 'itemReviewed'' error for your `Review` object means it needs to explicitly reference the `Product` it's about. Add `"itemReviewed": { "@type": "Product", "name": "SaaS Product X" }` within your `review` object to satisfy this `structured data` requirement for `rich snippets`.
0
Liam Williams
Answered 1 month ago

Wow, that was exactly it. Seriously saved my day, thanks so much for pointing that out...

Your Answer

You must Log In to post an answer and earn reputation.