pillar-content-architecture
How to design a content hub that earns topical authority. Pillar topic selection, cluster planning, internal linking architecture, URL structure, pillar and cluster page anatomy, topical authority signals for SEO and AEO/GEO, and the maintenance discipline that distinguishes intentional hubs from accidental orphans. Triggers on pillar content, content hub, topic cluster, topical authority, content architecture, hub and spoke, pillar page, cluster page, content silo, internal linking strategy. Also triggers when a content set is not ranking despite individual piece quality, when a pillar was la
Profile →npx skills add rampstackco/claude-skills --skill pillar-content-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Designs hub architectures at the content level, deciding which topic gets a pillar, how clusters link to it, and how the URL hierarchy and internal links reinforce topical authority. It outlines pillar vs cluster roles, and how to maintain and refresh hubs over time. It also provides guidance on when to use the skill to launch a new hub, restructure an existing set, or audit underperforming topics.
How it works
The skill prescribes:
- Selecting pillar topics and designing cluster plans (cluster size, facets, heterogeneity, sequencing).
- Establishing internal linking architecture: pillar-to-cluster, cluster-to-pillar, and cluster-to-cluster links; anchor-text discipline; maintaining a linking inventory and quarterly audits.
- Defining URL structure and information architecture: subfolder vs subdomain, hub URL pattern, slug conventions, and breadcrumbs.
- Outlining pillar page anatomy (hero, TL;DR, comprehensive body, use cases, common mistakes/FAQ, closing, schema) and pillar length expectations.
- Outlining cluster piece anatomy (hero, pillar callout, focused body, lateral callouts, closing).
- Identifying topical authority signals (SEO and AEO/GEO) and related content-gap/audit considerations.
- Maintenance and refresh patterns (annual pillar refresh, cluster refresh triggers, expansion, pruning, hub lifecycle).
When to use it
Use when launching a new content hub, restructuring to a hub, deciding pillar vs cluster roles, or auditing why a content area isn’t ranking despite quality pieces.
What it can touch
The skill references internal-linking architecture, URL structure, pillar and cluster page anatomy, and topic-authority signals as factors to implement within hub design. It discusses maintenance patterns and signals, but does not execute per-piece writing.
Caveats
The content describes governance and maintenance requirements, hub lifecycles, and directional linking patterns. It does not specify per-piece content creation or guarantee ranking outcomes.
# 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
What does the pillar-content-architecture skill do?
How to design a content hub that earns topical authority. Pillar topic selection, cluster planning, internal linking architecture, URL structure, pillar and cluster page anatomy, topical authority signals for SEO and AEO/GEO, and the maintenance discipline that distinguishes intentional hubs from accidental orphans. Triggers on pillar content, content hub, topic cluster, topical authority, content architecture, hub and spoke, pillar page, cluster page, content silo, internal linking strategy. Also triggers when a content set is not ranking despite individual piece quality, when a pillar was la
How do I install it?
Run `npx skills add rampstackco/claude-skills --skill pillar-content-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rampstackco/claude-skills, a repository with 515 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.