The Entity-First Site Architecture Mindset
Session 8.1 · ~5 min read
Most websites are organized around what the business sells. The homepage lists services. The navigation groups pages by offering category. The blog covers topics the marketing team thinks will attract traffic. This is a sales-first architecture. It works for conversion. It fails for entity clarity.
An entity-first architecture starts with a different question: "Does every page on this site help Google understand who we are?" Not what we sell. Not what keywords we target. Who we are. The distinction matters because Google's Knowledge Graph does not store pages. It stores entities and their relationships. Your site architecture either reinforces those relationships or scatters them.
Traditional vs. Entity-First Architecture
A traditional site architecture mirrors a sales funnel. Top-of-funnel content attracts visitors. Middle-of-funnel content nurtures them. Bottom-of-funnel content converts them. The organizing principle is the buyer's journey. The entity, the organization itself, is an afterthought. It gets a single about page, buried in the footer navigation.
An entity-first architecture flips this. The organizing principle is the entity. Every page serves a role in declaring, reinforcing, or contextualizing the entity. The about page is not a footnote. It is the foundation. Service pages do not just describe offerings. They explicitly connect those offerings to the entity via structured data. Blog posts do not just target keywords. They build topical associations that define what the entity is known for.
(sales pitch)"] --> T2["Services
(what we sell)"] T1 --> T3["Blog
(traffic bait)"] T1 --> T4["About
(afterthought)"] T1 --> T5["Contact
(form only)"] end subgraph Entity["Entity-First Architecture"] direction TB E1["Homepage
(entity declaration)"] --> E2["About
(entity identity doc)"] E1 --> E3["Services
(entity-offering links)"] E1 --> E4["Content Hub
(entity-topic authority)"] E1 --> E5["Contact
(entity verification)"] E2 -->|"reinforces"| E3 E2 -->|"reinforces"| E4 E3 -->|"links back"| E2 E4 -->|"links back"| E2 end style T1 fill:#222221,stroke:#8a8478,color:#ede9e3 style T2 fill:#222221,stroke:#8a8478,color:#ede9e3 style T3 fill:#222221,stroke:#8a8478,color:#ede9e3 style T4 fill:#222221,stroke:#8a8478,color:#ede9e3 style T5 fill:#222221,stroke:#8a8478,color:#ede9e3 style E1 fill:#222221,stroke:#c8a882,color:#ede9e3 style E2 fill:#222221,stroke:#6b8f71,color:#ede9e3 style E3 fill:#222221,stroke:#c8a882,color:#ede9e3 style E4 fill:#222221,stroke:#c8a882,color:#ede9e3 style E5 fill:#222221,stroke:#c8a882,color:#ede9e3
Notice the difference. In the traditional model, pages exist independently. In the entity-first model, pages are interconnected, and the about page sits at the center. Every service page links back to the entity identity document. Every content piece reinforces the entity's topical authority. The contact page is not just a form. It is a verification hub with NAP data, a map embed, and contactPoint schema.
Page Types and Their Entity Purpose
Every page on your site serves one of four entity purposes. Some pages serve multiple purposes simultaneously, but every page should serve at least one. If a page does not serve any entity purpose, ask yourself why it exists.
| Page Type | Entity Purpose | Key Entity Signals | Priority |
|---|---|---|---|
| About page | Identity declaration | Organization/Person schema, founding date, founders, description, sameAs links | Critical |
| Contact page | Entity verification | NAP data, contactPoint schema, embedded map, physical address | Critical |
| Homepage | Entity summary | Primary Organization schema, tagline, core offering summary | Critical |
| Service/Product pages | Entity-offering association | Service/Product schema with provider property linking to entity | High |
| Team/Author pages | Entity-person association | Person schema with worksFor/memberOf linking to organization | High |
| Blog/Content pages | Entity-topic authority | Article schema with author and publisher, topical relevance | Medium |
| Case studies | Entity credibility | Mentions of real clients, outcomes, industry context | Medium |
| Legal pages (privacy, terms) | Entity legitimacy | Registered business name, jurisdiction, compliance signals | Low (but required) |
The Entity Core
Every entity-first site has what we call the entity core: the three pages that together form the minimum viable entity declaration. These are the homepage, the about page, and the contact page. If Google can crawl only three pages on your site, these three should be enough to establish your entity identity.
The homepage declares the entity and summarizes what it does. The about page provides the full identity document with history, founders, credentials, and external references. The contact page verifies the entity's real-world existence with physical address, phone number, email, and map.
Key concept: The entity core (homepage, about, contact) must be internally linked from every page on your site. These three pages are the foundation of your entity declaration. If any page on your site does not link to at least one of them, that page is architecturally disconnected from your entity.
Auditing Your Current Architecture
Before restructuring anything, you need to understand what you have. Open your site in a new tab and answer these questions:
- Can you reach the about page from every page on the site in one click?
- Does every service page explicitly mention the organization name?
- Does the homepage contain Organization or Person schema with a complete set of properties?
- Are blog posts connected to the entity via author attribution and publisher schema?
- Is the contact page linked in the main navigation or only in the footer?
If you answered "no" to any of these, your current architecture has entity clarity gaps. That is normal. Most sites were not built with entity architecture in mind. The rest of this module will show you how to close those gaps, page by page.
The Mindset Shift
Traditional SEO asks: "What keywords does this page target?" Entity-first architecture asks: "What does this page tell Google about who we are?" The two questions are not mutually exclusive. A service page can target commercial keywords and reinforce entity identity at the same time. But the entity question must come first. If a page ranks well for its target keyword but does nothing to reinforce entity identity, it is a missed opportunity.
This is not abstract philosophy. Google's systems increasingly rely on entity understanding to evaluate content quality, determine relevance, and assign trust. A site with clear entity architecture gives Google's systems less work to do. Less inference. More confidence. Better treatment.
Further Reading
- Google: SEO Starter Guide (Site Structure)
- Search Engine Journal: Site Architecture for SEO
- Schema.org: WebSite Type
- Semrush: Website Structure Guide
Assignment
Map your current site architecture from an entity perspective.
- List every page on your site and classify it into one of the eight page types from the table above.
- For each page, write one sentence describing its current entity purpose. If you cannot articulate an entity purpose, mark it as "entity-disconnected."
- Identify your entity core (homepage, about, contact). Check whether each of these pages is accessible in one click from every other page on the site.
- Count how many pages are entity-disconnected. This number is your entity architecture gap score.