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 ac…
Install / Use
npx skills add rampstackco/claude-skills --skill pillar-content-architectureInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of pillar-content-architecture
pillar-content-architecture scores 86/100 on our quality scale, 412th of 642 Marketing skills we index.
Its SKILL.md is 22 KB long, well organised into 16 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 902 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so pillar-content-architecture is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
pillar-content-architecture compared with similar skills
All 4 of these similar skills score higher than pillar-content-architecture; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| pillar-content-architecture (this skill)by rampstackco | 86 | 902 | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install pillar-content-architecture?
- Run
npx skills add rampstackco/claude-skills --skill pillar-content-architecture. The install tabs above show the steps for each supported agent. - Which AI agents does pillar-content-architecture work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is pillar-content-architecture safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is pillar-content-architecture still maintained?
- The repository was last updated about 2 months ago, so pillar-content-architecture is actively maintained.
Skill content
View source on GitHubname: pillar-content-architecture description: "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 launched without a cluster, or when content has accumulated without an architecture." category: content catalog_summary: "Hub-level content architecture: pillar topic selection, cluster planning, internal linking, URL structure, pillar and cluster page anatomy, topical authority signals, refresh discipline" display_order: 1
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.
Pillar vs cluster vs orphan content
The keystone distinction. Three categories of content in any program.
Pillar. Comprehensive piece covering a major topic area. 2,500 to 5,000 words plus. Anchors the topical authority claim for the topic. Receives links from cluster pieces; links out to cluster pieces selectively, not as a footer dump. The pillar is the entry point for the topic and the reference the cluster orbits.
Cluster. Narrower piece covering a specific facet of the pillar topic. 800 to 2,000 words. Links up to pillar; may link sideways to other clusters in the same hub when a connection is natural. Each cluster answers one specific question within the pillar's scope.
Orphan. Piece that does not connect to a pillar or cluster. May rank or convert on its own merits, but does not compound into topical authority. Some orphans are fine by design (release-note pages, customer stories, one-off campaigns); most orphans are accidents.
The pathology. Most content programs are 80% orphans, 15% accidental clusters, 5% accidental pillars. The discipline is moving toward 70% intentional clusters, 20% intentional pillars, 10% standalone-by-design. Same total content volume; different architectural outcome.
The reading model. Search engines and AI engines both read internal-link graphs to infer topical authority. A pillar with 12 well-linked cluster pieces signals depth on a topic. 12 orphans on the same topic signal scattered, less-authoritative coverage. The architecture is the signal.
Detail and decision tree in references/pillar-cluster-decision.md.
Topic selection for pillar pages
Not every topic deserves a pillar. The five-criterion selection framework:
- Search volume justifies the investment. Pillar topic has enough monthly volume to support a 3,000 to 5,000-word effort plus 8 to 15 cluster pieces. Sub-100 monthly searches usually does not.
- Topic has natural facets. You can identify 8 to 15 distinct subtopics that could each be their own piece. If you can only think of 3, it is probably a cluster, not a pillar.
- Commercial relevance. The topic connects to your business model. A pillar without commercial signal is content marketing for content marketing's sake.
- Competitive feasibility. Top 10 SERP for the pillar keyword is achievable. If the SERP is dominated by Wikipedia, government sites, and Fortune 500 brands, your pillar will rank position 47 no matter how good it is.
- Editorial commitment. The team will maintain the pillar (refresh annually, add new clusters, update statistics). Pillars are not ship-and-forget; they are 5-year commitments.
The "everything is a pillar" anti-pattern. Teams call any 3,000-word piece a pillar. Length does not make a pillar. The architecture does. Pillar is the role a piece plays in the hub structure, not the word count.
Detail in references/topic-selection-criteria.md.
Cluster planning
Once a pillar is selected, plan its cluster:
- Cluster size. Typically 8 to 15 pieces for a strong hub. Below 5 reads thin; above 25 becomes unmanageable; sweet spot is 10 to 12.
- Cluster facets. Each cluster piece covers one facet of the pillar topic. Facets are surfaced from keyword research (long-tail variations of pillar keyword), "people also ask" data, sub-headings in top-ranking pillar pages on the SERP, competitor cluster maps, and first-party customer questions (sales calls, support tickets).
- No facet duplication. Two cluster pieces should not target overlapping queries. If they do, consolidate to one piece.
- Cluster heterogeneity. Clusters should cover the topic from multiple angles (definition, how-to, comparison, examples, common mistakes, costs, alternatives, case studies) rather than 12 variations of "what is X."
- Sequence. Ship pillar first (or alongside the first 3 to 5 clusters). The link graph will not form without the pillar in place; clusters that link to a non-existent pillar are orphans-in-waiting.
Detail in references/cluster-planning-patterns.md.
Internal linking architecture
The hub's internal-link graph is what actually produces topical authority signals. The architecture has three directions:
Pillar to cluster (top-down). Pillar links out to each cluster piece via contextual anchors, typically once per cluster from within the pillar's body. Do not bury cluster links in a "related reading" footer; weave them into the relevant section of the pillar where the reader's curiosity peaks.
Cluster to pillar (bottom-up). Every cluster piece links up to the pillar at least once, typically in the first 200 words and again in the closing section. Bottom-up is the discipline that makes the pillar compound; without it the pillar is just a long article.
Cluster to cluster (lateral). Selective lateral linking when one cluster naturally references another. Do not force lateral links; an "everyone links to everyone" cluster is messy and dilutes anchor text relevance.
Anchor text discipline. Vary the anchor text. "Click here" is dead; exact-match keyword stuffing is dead; descriptive natural-language anchors are alive. The brief for each piece (see content-brief-authoring) specifies anchor text per outbound link.
The "linking inventory" pattern. Maintain a sheet (or database row, or dbt model) tracking every link in the hub, who links to whom, and the anchor text used. Audit quarterly to catch broken links, anchor-text drift, and missing connections that should exist.
Detail in references/internal-linking-architecture.md.
URL structure and information architecture
URL patterns matter for both crawl clarity and reader navigation. Decision factors:
Subfolder vs subdomain. Subfolder is the default (example.com/hub-topic/cluster-piece) for SEO consolidation; both pillar and cluster live on the same domain authority. Subdomain is appropriate only for genuinely distinct properties (docs.example.com, community.example.com).
Hub URL pattern. /hub-topic/ for the pillar, /hub-topic/cluster-piece/ for clusters. Avoid /blog/cluster-piece/ if the goal is hub authority; the URL itself signals topical grouping to crawlers and readers.
Slug conventions. Short, descriptive, keyword-aware but not stuffed. /seo-content-strategy/keyword-research-for-pillars/ not /the-ultimate-guide-to-seo-content-strategy-keyword-research-for-pillar-pages-2026/.
Breadcrumbs. Surface the hub structure in breadcrumb navigation. Helps readers see where they are; helps crawlers see the hierarchy.
The "/blog/ trap." Teams put pillar and clusters under /blog/ because that is where the CMS folder is. This works structurally but loses the URL signal that says "these pieces belong together as a topical hub."
Detail in references/url-structure-patterns.md.
Pillar page anatomy
A pillar page does specific work. The standard sections:
- Hero. Defines the topic, signals scope ("The complete guide to X for Y audience"), establishes authority quickly.
- TL;DR or executive summary. 150 to 250 words at the top. AI engines often cite this section verbatim. Treat it as the citation-ready summary, not as a marketing intro.
- Comprehensive body. Covers the topic's major facets, with internal-link callouts to cluster pieces for deep dives. The body is not a comprehensive treatment of every facet; it is a guided tour with depth links.
- Use cases or examples. Anchor the abstract topic to concrete instances.
- Common mistakes / FAQ. AI-citation friendly section with structured Q&A. Pair with FAQ schema markup.
- Closing or next steps. Directs reader into the cluster (which piece to read next based on intent).
- Schema markup.
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
