How to nest JSON-LD objects

1. 01

   Identify the relationship

   For example, an Article has an author and publisher, or an Offer references a Product.

2. 02

   Use a nested object or @id reference

   Choose based on whether the entity is defined locally or reused.

3. 03

   Use the expected value type

   Review the property definition and consumer documentation.

4. 04

   Avoid excessive duplication

   Keep repeated organization and person details connected.

5. 05

   Validate the graph

   Check syntax, type, property, and visible consistency.

Validate the final production output in layers: JSON syntax, Schema.org vocabulary, current feature-specific requirements, visible content, and crawl access.

• Define the purpose and expected result of json-ld objects.
• Capture the current state using visible entities, page purpose, JSON-LD graphs, identifiers, relationships, required properties, and consumer-specific eligibility.
• Identify the source template, component, plugin, content owner, and release path that controls the output.
• Prepare a test case, approval path, backup or rollback method, and post-release verification plan.

• Parse the deployed json-ld, validate the graph, compare it with visible content, and test any target consumer requirements.
• Check representative page types and edge cases instead of confirming only the example used during implementation.
• Confirm the change did not create publishing properties that are unsupported, hidden, stale, or inconsistent with visible content.
• Record the implementation date, owner, release reference, evidence, and next review trigger.