Content Architecture: Designing for Search, Not Readers
How page structure, relationships, and hierarchy signal system coherence to Google.
Published Jan 25, 2024
The Confusion
Most sites structure content for readers: chronological blogs, category pages, tag archives. Google doesn't care about your user experience structure. It cares about semantic structure.
Content architecture, in Google's eyes, is: How do pages relate to each other? What's the hierarchy? What entities do they discuss?
The Three Layers
Layer 1: Topic Structure
What is your site about? Create a pillar structure: pillar pages (comprehensive guides) and cluster pages (supporting content). Each cluster page links to relevant pillars.
Layer 2: Entity Relationships
Within your content, define entities and their relationships. "Entity X relates to Entity Y in context Z." This signals topical coherence to Google.
Layer 3: Internal Link Graph
How you link pages together. Pillar pages link to cluster pages. Cluster pages link back to pillars. All pages in a topic link to related pages in that topic.
Bad Architecture vs Good Architecture
Bad
- All pages are /blog/post-title
- No internal linking between posts
- Random topics mixed together
- No pillar pages
- Homepage links to 100+ random posts
Good
- /topic/subtopic/article structure
- Pillar pages at /topic/ level
- Cluster pages at /topic/subtopic/ level
- Internal linking follows hierarchy
- Homepage links only to pillar pages
How to Audit Yours
- Map your current URL structure. Is it semantic or chaotic?
- Identify your pillar topics (what are you truly authoritative on?)
- Group content by pillar. What content belongs under each?
- Identify gaps. What subtopics should exist but don't?
- Plan your internal linking. How should pages relate?