Relationship Schema Between Entities

Entities do not exist in isolation. A person works for an organization. An organization has a founder. A brand has sub-brands. A consultant collaborates with other professionals. These relationships define how search engines understand your place in the knowledge graph.

Schema.org provides a rich vocabulary for declaring these inter-entity relationships. When you implement them correctly, you create a mini knowledge graph on your own properties, one that search engines can directly ingest and use to build your entity profile.

Types of Entity Relationships

Schema.org supports several categories of inter-entity relationships. Each one creates a different kind of edge in the knowledge graph.

Bidirectional Declarations

The strongest relationship signals come from bidirectional declarations. When your Person schema says worksFor: Organization X and your Organization schema says employee: Person Y, both sides confirm the relationship. This is not redundant. It is validation.

In this example, the Person and Organization entities are connected through multiple relationship types. The Organization has a sub-brand. The Person has educational and professional affiliations. The Organization sponsors an event. Each arrow is a declared, machine-readable relationship.

Using @id for Cross-Page References

Relationship schema works best when entities are referenced by @id rather than redeclared on every page. Define your Person entity once with a canonical @id (typically on your About page or homepage), then reference that @id from Article schemas, Organization schemas, and Event schemas across your site.

// On your About page:
{
  "@type": "Person",
  "@id": "https://yoursite.com/#jane-smith",
  "name": "Jane Smith",
  "worksFor": { "@id": "https://yoursite.com/#smith-seo" }
}

// On your homepage:
{
  "@type": "Organization",
  "@id": "https://yoursite.com/#smith-seo",
  "name": "Smith SEO",
  "founder": { "@id": "https://yoursite.com/#jane-smith" }
}

// On a blog post:
{
  "@type": "Article",
  "author": { "@id": "https://yoursite.com/#jane-smith" },
  "publisher": { "@id": "https://yoursite.com/#smith-seo" }
}

The @id is the glue that connects schema across pages into a coherent entity graph. Without it, each page's schema is an isolated fragment. With it, Google can traverse the relationships and build a consolidated entity profile.

Mapping Your Entity Relationships

Before you implement relationship schema, map every entity relationship that applies to your situation. Consider these categories:

• Person to Organization: Employment, founding, board membership, advisory roles
• Organization to Organization: Parent/subsidiary, partnerships, sponsorships
• Person to Institution: Education, certifications, professional associations
• Entity to Event: Speaking, organizing, sponsoring, attending
• Entity to CreativeWork: Authoring, publishing, contributing

Every relationship you identify is a candidate for schema implementation. Prioritize relationships where both sides have a web presence, because that allows for bidirectional validation. A worksFor declaration pointing to an organization with its own schema is stronger than one pointing to an organization with no web presence at all.

Further Reading

• Organization Type: Relationship Properties (Schema.org)
• Documentation for memberOf, worksFor, alumniOf (Schema.org GitHub)
• Organization Schema: Advanced JSON-LD and @id Patterns (Squin)
• SEO with Nested JSON-LD Schema (WHO Digital Strategy)