What breaks when you nest schema incorrectly?
- Published November 6, 2026
- Linked from 1 answer
- In a cluster of 5
What breaks is the relationship between facts. Nesting is how structured data says which thing a property belongs to: this price belongs to this offer, this offer to this product, this author to this article. Put a property under the wrong parent and the fact ends up attached to the wrong thing, or to nothing Google uses, and the page can lose eligibility for the feature the markup was meant to support. The markup may still look tidy, and parts of it may still validate.
Three nesting mistakes and what they cause
| Mistake | Example | Result |
|---|---|---|
| Property under the wrong parent | <!–INLINECODE0–> placed directly on the Product instead of inside its <!–INLINECODE1–> | The product has no valid offer, so required offer information is missing |
| Wrong type for the value | A SKU or a formatted string such as "$19.99" where a numeric price belongs | The value may be ignored or flagged as invalid |
| Child that should be nested sits beside its parent | An <!–INLINECODE2–> as a separate top-level item with no link to the product it rates | The rating describes nothing in particular |
Google’s merchant listing documentation lists the price and currency among the required properties of an Offer, and its structured data policies make items without their required properties ineligible for rich results. A misplaced price is therefore not a cosmetic slip; it removes a required piece.
Several top-level items are normal
A page can carry more than one top-level item, for example Organization, BreadcrumbList, and Article on a blog post. That is not an error by itself. The problem starts when two items describe the same thing in conflicting ways, such as two Product blocks with different prices for one product, because then the markup contradicts itself. If your CMS and a plugin both output markup for the same entity, keep one source.
When items need to refer to each other, JSON-LD lets you give an item an @id and point to it from elsewhere in the same graph, so an article can name its publisher without repeating the publisher’s details. Use it to connect pieces you deliberately split, not to patch duplicates.
How to check nesting
- Run the page through the Rich Results Test and expand each detected item. Each property should appear under the parent you intended.
- Compare the marked-up values with what the page shows: the same price, the same rating, the same author.
- If a feature you expect is not detected at all, look for the required property that went missing in the nesting, then compare with the cases in why valid schema sometimes never shows a rich result.
Fix nesting in the template, not page by page, because a template error repeats on every page that uses it.
Add a comment