Pillar Content Architecture
A senior content architect's playbook for designing content hubs that earn topical authority.
Most content programs accumulate accidentally. Pieces ship one at a time, internal linking happens (or does not) in editing, similar topics get covered by multiple pieces with no coordination, and six months later the team has a content set that looks like a sitemap but feels like a yard sale. Search engines see disconnected pages; AI engines see scattered citations; readers cannot tell which piece is the entry point and which is the reference.
This skill is the discipline of intentional hub architecture. It assumes you have decided which topic areas to invest in (see content-strategy) and have keyword data (see seo-keyword). It does not write any individual piece (see content-brief-authoring for per-piece work and content-and-copy for execution). What it does is design the structure: which topic gets a pillar, which subtopics get cluster pieces, how the pieces link to each other, where they live in the URL hierarchy, and what topical authority signals the architecture is engineered to produce.
When to use this skill: launching a new content hub, restructuring an existing content set into a hub, deciding whether a piece should be a pillar or a cluster, or auditing why a content area is not ranking despite individual piece quality.
What this skill is for
This skill spans hub-level content architecture. It composes with five sister and adjacent skills, and the distinction between them is what keeps each one sharp.
content-strategyis program-scope: multiple topic pillars, editorial calendar, governance, formats. Decides what topic areas to invest in across a quarter or year.seo-keywordis upstream-input: keyword research that surfaces candidate pillar topics with volume, difficulty, and intent data.- This skill is hub-scope: one pillar plus its cluster, the architecture that ties them together. The structural decisions, not the per-piece content.
content-brief-authoringis per-piece scope: brief for one content artifact. Each cluster piece (and the pillar itself) gets briefed via that skill.content-and-copyis execution scope: writing the piece itself.seo-content-gap-auditis audit-side: finds missing pieces in an existing content set after the fact. This skill prevents the gaps; that skill catches the ones that emerge.
The clean composition: content-strategy decides which topics, seo-keyword surfaces opportunities, this skill designs the hub, content-brief-authoring briefs each piece, content-and-copy writes each piece, seo-content-gap-audit later catches what slipped. Six skills, sequential.
The audience: SEO content strategists, content architects, in-house teams designing content hubs, agencies running topical authority programs. The voice is senior content architect to junior content marketer. Concrete, opinionated, honest about what makes a hub earn authority versus decorate the sitemap.
If required data is unavailable
This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.
Reference files
references/pillar-cluster-decision.md- Pillar vs cluster vs orphan decision tree with worked examples and the "everything is a pillar" anti-pattern.references/topic-selection-criteria.md- Five-criterion framework expanded with B2B SaaS, ecommerce, services, and media examples.references/cluster-planning-patterns.md- Facet sourcing methods, sequencing patterns, heterogeneity check.references/internal-linking-architecture.md- Top-down, bottom-up, lateral patterns; anchor text discipline; linking inventory; quarterly audit checklist.references/url-structure-patterns.md- Subfolder vs subdomain decision; slug conventions; breadcrumbs; the /blog/ trap.references/pillar-page-anatomy.md- Section-by-section anatomy; TL;DR placement; FAQ schema; internal-link callouts; schema choices; length calibration.references/cluster-piece-anatomy.md- Focused-question framing; pillar callout placement; lateral linking judgment.references/topical-authority-signals.md- SEO and AEO/GEO signals at hub level; two-engine optimization framing.references/content-refresh-patterns.md- Annual pillar refresh; triggered cluster refresh; cluster expansion and pruning; hub lifecycle.references/common-pillar-failures.md- Eleven-plus failure patterns with diagnoses and fixes.
Conditional methods
Before applying a method below, read its linked section. For a narrow task select only relevant methods; for a full audit/design use the framework and relevant failure patterns. Existing references remain available for deeper details.
- Pillar vs cluster vs orphan content: method.
- Topic selection for pillar pages: method.
- Cluster planning: method.
- Internal linking architecture: method.
- URL structure and information architecture: method.
- Pillar page anatomy: method.
- Cluster piece anatomy: method.
- Topical authority signals: method.
- Maintenance and refresh patterns: method.
- Common failure modes: method.
- The framework: 12 considerations for hub architecture: method.
- Closing: architecture is the moat: method.