SEO glossary
What is a Relationship?
Learn what a relationship is—a typed connection between concepts or entities in semantic modeling—and how relationships differ from attributes, taxonomies, and database entity-relationship diagrams.
Definition
A relationship is a typed semantic connection between two or more concepts or entities—such as authorOf, partOf, or integratesWith—that expresses how distinct units of meaning relate, beyond simple hierarchical classification or scalar properties.
Relationship: the typed edge between two meanings
A relationship connects two distinct things with a named type. Jane Doe authorOf Crawl Budget Guide. Crawlox integratesWith Google Search Console. Crawl Budget broaderThan Render Budget as a conceptual link. Relationships are not scalar attributes like price or color—they are semantic edges in a graph.
For semantic SEO, relationships turn isolated pages into a navigable knowledge network. Search engines infer site expertise partly from whether your internal links mirror real-world connections between entities and concepts—not only from keyword overlap.
Relationship vs attribute vs taxonomy parent-child
| Construct | What it connects | Example |
|---|---|---|
| Relationship | Two nodes with a verb-like type | Product —compatibleWith→ Platform |
| Attribute | Node to literal value | Product —price→ 49 USD |
| Taxonomy broader/narrower | Category to subcategory | SEO → Technical SEO |
| Keyword co-occurrence | Words in queries/copy | crawl budget + log analysis |
Hierarchy is one relationship family (broaderThan / narrowerThan). Rich ontologies add dozens more.
Common semantic relationship types for publishers
Authorship & attribution
author, contributor, publisher—Person to CreativeWork.
Membership & ownership
parentOrganization, department, brand—org trees.
Composition
isPartOf, hasPart—guides within series or products in suites.
Topic binding
about, mentions—content to concepts and entities.
Functional fit
integratesWith, requires, supersedes—product ecosystem edges.
Relationships in Schema.org
Object properties express relationships as linked nodes:
{
"@type": "Article",
"headline": "Monitoring crawl budget in Crawlox",
"author": {
"@type": "Person",
"name": "Alex Kim",
"url": "https://www.example.com/authors/alex-kim"
},
"about": {
"@type": "DefinedTerm",
"name": "Crawl Budget"
},
"isPartOf": {
"@type": "WebSite",
"name": "Example SEO Blog"
}
}
Each property name is the relationship type; URIs identify target nodes.
Semantic relationships vs entity-relationship (ER) modeling
Entity-relationship diagrams—common in database design—model tables, primary keys, and foreign keys for transactional storage. Cardinality (1:N, M:N) optimizes normalization and query performance.
Semantic relationship modeling for SEO and knowledge graphs optimizes meaning for crawlers and users:
| ER modeling focus | Semantic relationship focus |
|---|---|
| Storage integrity | Factual assertions on the public web |
| Join performance | Disambiguation and rich results |
| Internal schema | Shared vocabularies like Schema.org |
| Application-bound | Cross-site corroboration in Google's Knowledge Graph |
Both use the word "entity," but ER diagrams rarely appear in marketing copy—semantic edges do, through links and structured data.
Building a relationship map for your site
Inventory node types
Person, Product, Article, DefinedTerm—from your ontology.
List allowed predicates
Which relationship types each pair may use.
Encode in templates
Author bios auto-link; products link to integrations.
Publish sameAs bridges
Connect instances to external authority URLs.
Audit orphans
Nodes with no inbound typed relationships.
Entity SEO programs often fail here: rich Organization schema but no author relationships from articles to real people.
Relationships and internal linking
Treat internal links as published relationships:
| Weak pattern | Semantic pattern |
|---|---|
| "Related posts" widget with random recency | Case study about product linked in first paragraph |
| Footer keyword soup | parentOrganization from subsidiary to brand hub |
| Orphan glossary entries | Concept broaderThan links among glossary pages |
Anchor text should reflect the relationship type naturally—"Crawlox integrates with Search Console" beats "click here."
Relationship mistakes
- Using generic 'related' without a typed predicate
- Linking every page to every product—graph noise
- Schema author URLs that 404 or point to home
- Confusing hierarchical taxonomy with integratesWith edges
- Asserting competitor relationships without factual basis
Relationship myths
- Myth: "Internal links are not relationships." Reality: they are the crawlable surface of your semantic graph.
- Myth: "Only JSON-LD counts." Reality: visible citations and lists also signal relations.
- Myth: "ER diagrams are enough for SEO." Reality: storage models must publish to HTML and schema.
The practical takeaway
A relationship is a typed connection between two concepts or entities—distinct from attributes and broader than taxonomy parent-child links. Model relationships in your ontology, express them in copy and Schema.org, and distinguish semantic graph work from database entity-relationship design.
Related terms
Frequently asked questions
What is the difference between a relationship and an attribute?
Attributes describe one node with a value—price, color, foundingDate. Relationships connect two distinct nodes—Article author Person, Product partOf Category.
How is semantic relationship modeling different from entity-relationship diagrams?
ER diagrams model database tables and keys for storage. Semantic relationships model meaning on the web—authorship, membership, compatibility—for humans, search, and knowledge graphs.
Where do relationships appear in Schema.org?
As object properties—author, isPartOf, parentOrganization, about—with URIs or nested objects pointing to other entities.
Can taxonomies express relationships?
Taxonomies primarily express broader/narrower hierarchy. Ontologies and knowledge graphs add many other relationship types.
Do relationships affect internal linking?
Yes. Typed relationships should drive contextual links—case studies about products, guides explaining concepts—not random related posts.
References
Explore authoritative guidance and frameworks related to relationship.
Explore every glossary definition
Return to the glossary to search by term, alias, starting letter, or category.