Clearly link multiple entities on one page
Multiple entities need stable IDs and precise relationships. A JSON-LD graph shows what the main subject, provider, author, or location is.
For SEO teams and developers, "Uniquely Linking Multiple Entities" shows the difference between "Unique Primary Entity" and "One Definition per ID." "Duplicate Organization" is the typical warning sign.
Published: 3 min read · Author: Sebastian Geier
How do you connect multiple entities on a page without ambiguous relationships?
The webpage names its main subject using `mainEntity`, while `author`, `provider`, `brand`, and `location` express the respective roles. Recurring entities are not copied but referenced by ID; visible content and page type determine which relationship actually applies.
Business-appropriate role
Number of multiple defined real entities, undefined ID references, and conflicting roles per page template.
Percentage of pages tested with a unique mainEntity and visible correspondence of all essential relationships.
Working example: "Duplicate organization"
A course page contains WebPage, Course, Offering Organization, and Instructor. Course is the main subject, referring to the provider and instructor, while the WebPage mentions the publisher separately; the same Organization ID is not generated again as a new entity.
One definition per ID
Capture all real-world entities on the page, including their identity, role, and visible correspondence, in a small graph sketch.
Reuse stable IDs, define the primary entity, and connect secondary entities only via relevant business properties.
Check the rendered graph for duplicates, loops, undefined references, and inconsistencies with the visible content.
Dual organization
Dual organization Publisher and provider are defined with different IDs, even though they represent the same real-world organization.
Incorrect Main Entity – A global organization becomes the main entity of a technical article, displacing the actual article from the page model.
Unsubstantiated Relationship – A person is linked as a contributor or author, even though this role is not visibly verifiable on the page.
Clear Main Entity
Test criterion
Clear Main Entity
The main subject of the page is clearly named and separated from the publisher, author, and incidentally mentioned entities.
Test criterion
One definition per ID
Every real entity has a complete definition in the graph; further occurrences refer to the same identifier.
Business-appropriate role – Properties such as provider, brand, worksFor, or location correspond to the real, visible relationship between the involved entities.
What Follows "Uniquely Linking Multiple Entities"
Use sameAs references selectively instead of indiscriminately Expands on the "Unique Primary Entity" checkpoint. The guiding question is: Which external profiles are suitable for a credible sameAs reference?
A complementary perspective is offered Using Schema.org cleanly and completely for LocalBusinessIt answers the question: "Which LocalBusiness details belong on a real location page and must match?"
If you want to practically implement "Uniquely Linking Multiple Entities," you can refer to Robust Website Systems This focuses on "Entity Identity and Relationships" and "Unique Primary Entity."
Conclusion: Uniquely Linking Multiple Entities
An entity graph gains clarity through relationships, not through as many types as possible. Unique IDs and roles make it clear which subject the page represents and who is involved.
Sources and Further Information
The classification of "Uniquely Linking Multiple Entities" is based on the following official documentation and standards.
Organization structured data – Google Search CentralOfficial recommendations for real organization data, matching subtypes, and online and physical presence.
Schema.org DocumentationPrimary documentation of the vocabulary and its type and property relationships as the basis for a consistent entity model.
Introduction to structured data markup – Google Search CentralOfficial explanation of structured entities, JSON-LD, sameAs, and the distinction between Google features and general schema.org vocabulary.
Key Thesis
Each entity is defined once with its own ID and referenced via appropriate properties. The page clearly names its primary subject and assigns sub-entities to their respective subject areas.
What This Is Not About
Multiple unconnected JSON-LD blocks or repeated organizational entries do not automatically explain how the page, author, provider, and offer are related.
What it's about
Each real-world object is defined once with a stable ID and referenced via appropriate properties in a clear graph.
Structured data & entity SEO
Modeling corporate relationships between brand, operator, and location.
"Uniquely linking multiple entities" includes, as a separate test step, the question: How are the relationships between brand, operator, and location correctly modeled?
Structured data & entity SEO
Consistently assigning entity IDs for locations, services, and brands
Adds a separate decision to "Uniquely link multiple entities": How do you assign consistent entity IDs for locations, services, and brands?
Insights Overview
All VELUNO Insights at a Glance
Further analyses on Website Systems, digital visibility, and robust working models.
One definition per ID: concrete next decision
A complex template should first be modeled on paper as five to seven nodes. Any duplicate ID or relationship without a clear meaning will be clarified before implementation.