How to use multiple schema types on one page

1. 01

   Identify each visible entity

   Page, website, organization, author, product, service, event, breadcrumb, and media may all be relevant.

2. 02

   Choose one primary page focus

   The main entity should match the page's purpose.

3. 03

   Connect related objects

   Use @id rather than isolated duplicate blocks.

4. 04

   Avoid irrelevant markup

   More objects do not create more eligibility when they do not represent the page.

5. 05

   Validate consumer requirements separately

   A valid graph can include types a particular search feature does not use.

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 multiple schema types on one page.
• 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.