Advanced Schema Markup for multi-entity relationships
Please purchase this course, or sign in if you’re already enrolled, to access the course content.
Lesson overview
Most content strategies stop at topic clusters: a pillar page and a set of supporting articles. Language models, however, reason about entities such as people, products, concepts and organisations, and about the relationships between them. This lesson shows how to turn clusters into entity networks and how to build the core schema markup that makes those networks machine-readable.
What this lesson covers
- Why implementing schema is an essential step
- Turning a topic cluster into a network of related entities
- Building accurate Organization markup as the starting point
- Using sameAs to connect social and external profiles
- Adding Person markup for founders and leaders
- Why a consistent ID system is the most important technical element
The lesson uses a topic such as cybersecurity for small businesses to show the shift. Within the topic you identify product entities, the people who are experts in the field and the organisations involved. You then connect them with relationship properties such as isPartOf, isRelatedTo, knowsAbout and certifiedBy. That turns a flat content structure into something closer to a knowledge graph.
The practical part starts with company markup, because it tells AI systems who you are. The advice is to start simple and accurate: the organisation type, exact name, website, logo, a clear description and a complete postal address. Attributes can be added later. Next, the sameAs property lists the profiles that represent the company, with LinkedIn singled out as the most important, plus meaningful external listings. Only profiles you control should be included. This helps systems verify the company is real and tell it apart from others with similar names. Person markup for the founder or CEO follows, with a job title and a worksFor property pointing back to the organisation.
The lesson then explains why IDs matter so much. Without them, the same company described on several pages may look like several companies. With a unique ID defined once and referenced everywhere else, every mention points to the same entity. Reciprocal links, such as the organisation naming its founder and the founder working for the organisation, create a graph structure that search engines and AI systems can traverse.
This lesson sits in Module 2, Brand Entity Development and Recognition, after relationship mapping and before the practical audit template. It helps SEOs and developers who need to implement connected organisation and person markup correctly from the start.