Pillar Page Cluster Designer

Pillar Pages & Topic Clusters

by LeadMagic · MIT license · ★ 62 on GitHub

Designs pillar pages and topic clusters: hub page outlines, cluster keyword maps, and internal linking so the hub ranks for high-intent head terms. Use when the user is building cornerstone content, organizing a blog into clusters, or…

---
name: pillar-pages
description: >-
  Designs pillar pages and topic clusters: hub page outlines, cluster keyword
  maps, and internal linking so the hub ranks for high-intent head terms. Use
  when the user is building cornerstone content, organizing a blog into
  clusters, or planning a pillar page for a specific topic. Triggers on: "pillar
  page", "topic cluster", "hub page", "cornerstone content", "SEO pillar".
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "1.0.0"
  author: LeadMagic
  category: content-seo
  tags: [content-seo, pillar-pages, topic-clusters, cornerstone-content, seo]
  related_skills: [seo-strategy, pseo-strategy, faq-seo, content-marketing]
  frameworks:
    - "HubSpot — Topic cluster model"

Overview

Before delivering, verify: - [ ] All required sections are complete - [ ] Output matches the user's stated need - [ ] Named frameworks are cited for key recommendations - [ ] No vague claims — every recommendation has a specific action - [ ] Deliverable is ready for operational use, not just conceptual

Manual install (npx, ZIP)

Claude Codenpx skills add LeadMagic/gtm-skills --skill pillar-pages -g -a claude-code

Claude Code (degit)npx degit LeadMagic/gtm-skills/skills/content-seo/pillar-pages#main ~/.claude/skills/pillar-pages

Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.

Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

SKILL.md7.9 KB

Read SKILL.md here

LeadMagic/main1 file shown

SKILL.md7.9 KB

Browse every file on GitHub↗

SKILL.md

Show the full text164 lines

Pillar Pages & Topic Clusters

Overview

Pillar pages are comprehensive, authoritative pages that cover a topic broadly and link to detailed cluster content on specific subtopics. This architecture signals to Google that you're the authority on the topic, boosting rankings across the entire cluster.

Authoritative Foundations

HubSpot — Topic cluster model — Link one broad pillar page to cluster posts on subtopics, and link every cluster post back to the pillar.
Ahrefs — Keyword research by parent topic — Group keywords by the pages that already rank for them together; one pillar should target one parent topic.
Eli Schwartz — Product-Led SEO — Build pillars around what users need from the product, not only keyword volume.
Google Search Central — SEO Starter Guide — Use descriptive internal anchor text and a clear heading hierarchy so the cluster structure is crawlable.

When to Use

"Build a pillar page"
"Topic cluster strategy"
"Cornerstone content"
"Pillar page for [topic]"

Step-by-Step Process

Phase 1: Pillar Topic Selection

A pillar topic must be:

High search volume: 500-5,000+ monthly searches
High business value: Directly related to your product/ICP
Broad enough for clusters: At least 10-15 subtopics
Evergreen: Not news-dependent, will be relevant for years
Competitive but winnable: Check current top 10 — if they're all DR 70+ sites and you're DR 30, pick a different pillar

Phase 2: Cluster Mapping

Map the pillar's universe:

Core subtopics: 8-12 key areas the pillar must cover
Cluster content: 3-5 detailed articles per subtopic
Question clusters: The 20-30 questions people ask about this topic (from People Also Ask, Reddit, Quora, customer conversations)
Internal link map: Every cluster article links to the pillar. The pillar links to every cluster article. Cluster articles link to each other where relevant.

Phase 3: Pillar Page Structure

H1: [Topic]: The Complete Guide (or similar)
Executive summary: 2-3 paragraphs. What this covers, who it's for, key takeaways. This is what Google shows in featured snippets.
Table of contents: Jump links to each section
Section per subtopic: Each H2 covers one subtopic. 200-400 words per section. Link to the full cluster article for "deep dive."
Data & examples: Original data, customer examples, screenshots, case studies
Visual elements: Diagrams, charts, comparison tables, infographics
Expert contributions: Quotes from internal experts, customers, industry voices
Total length: 3,000-5,000 words. Long enough to be comprehensive, not so long that nobody reads it.

Phase 4: Internal Linking

Pillar → Cluster: In each pillar section, link to the full cluster article with descriptive anchor text
Cluster → Pillar: Every cluster article links to the pillar with a standard "Part of our [Topic] guide" callout
Cluster → Cluster: Cross-link between related cluster articles
Navigation: The pillar is linked from the main navigation or resource center
New content: Every new article on this topic gets a link from the pillar and links back to the pillar

Phase 5: Maintenance & Updates

Quarterly review: Check rankings, traffic, and conversion for the pillar and all cluster content
Annual refresh: Update data, examples, screenshots, and expert quotes. Republish with updated date.
Cluster expansion: Add new cluster articles as you identify new subtopics
Performance optimization: Improve page speed, mobile experience, and Core Web Vitals for the pillar page

Output Format

Pillar page plan with: topic selection justification, cluster map, content outline, internal linking diagram, and maintenance calendar.

Quality Check

Before delivering, verify:

All required sections are complete
Output matches the user's stated need
Named frameworks are cited for key recommendations
No vague claims — every recommendation has a specific action
Deliverable is ready for operational use, not just conceptual

Common Pitfalls

Writing for search engines, not humans. Keyword-stuffed content that reads like a robot wrote it. Fix: write for your ICP first, optimize for search second.
Publishing and praying. Creating content without a distribution plan. Fix: every piece gets a 30-day promotion calendar across email, social, and paid.
Ignoring content freshness. 2-year-old content with outdated data and examples still ranking. Fix: quarterly content audit — update or retire stale pieces.

Implementation Depth

Use this section when the user asks for a finished asset, not a high-level explanation.

Diagnostic Questions

What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?

Framework Application

Map the recommendation explicitly to the named frameworks in this skill:

HubSpot Topic Cluster Model: apply only the part that directly improves the requested deliverable.
Animalz Content Strategy: apply only the part that directly improves the requested deliverable.
Google Search Central — SEO Starter Guide: apply only the part that directly improves the requested deliverable.

Deliverable Standard

A strong output from this skill includes:

A crisp diagnosis of the current situation
A recommended path with tradeoffs, not a generic list
A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
A measurement plan with leading and lagging indicators
Risks and edge cases called out before execution

Adaptation Rules

For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.

Execution Artifacts

references/framework-notes.md — Ahrefs cluster model, Schwartz product-led pillars, Pattern 25 routing
templates/output-template.md — Deliverable shell for agent output
scripts/check-output.py — Lightweight deliverable validator
references/seo-strategy-playbook.md — Repo root: §3 keyword tiers and cluster structure
the using-gtm-skills skill — Pattern 25: B2B SEO Stack (step 2)

seo-strategy, content-marketing, faq-seo, citation-harvesting, landing-pages

1	---
2	name: pillar-pages
3	description: >-
4	Designs pillar pages and topic clusters: hub page outlines, cluster keyword
5	maps, and internal linking so the hub ranks for high-intent head terms. Use
6	when the user is building cornerstone content, organizing a blog into
7	clusters, or planning a pillar page for a specific topic. Triggers on: "pillar
8	page", "topic cluster", "hub page", "cornerstone content", "SEO pillar".
9	license: MIT
10	compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
11	metadata:
12	version: "1.0.0"
13	author: LeadMagic
14	category: content-seo
15	tags: [content-seo, pillar-pages, topic-clusters, cornerstone-content, seo]
16	related_skills: [seo-strategy, pseo-strategy, faq-seo, content-marketing]
17	frameworks:
18	- "HubSpot — Topic cluster model"
19	- "Ahrefs — Keyword research by parent topic"
20	- "Eli Schwartz — Product-Led SEO"
21	- "Google Search Central — SEO Starter Guide"
22	---
23
24	# Pillar Pages & Topic Clusters
25
26	## Overview
27	Pillar pages are comprehensive, authoritative pages that cover a topic broadly
28	and link to detailed cluster content on specific subtopics. This architecture
29	signals to Google that you're the authority on the topic, boosting rankings
30	across the entire cluster.
31
32	## Authoritative Foundations
33	- HubSpot — Topic cluster model — Link one broad pillar page to cluster posts on subtopics, and link every cluster post back to the pillar.
34	- Ahrefs — Keyword research by parent topic — Group keywords by the pages that already rank for them together; one pillar should target one parent topic.
35	- Eli Schwartz — Product-Led SEO — Build pillars around what users need from the product, not only keyword volume.
36	- Google Search Central — SEO Starter Guide — Use descriptive internal anchor text and a clear heading hierarchy so the cluster structure is crawlable.
37
38	## When to Use
39	- "Build a pillar page"
40	- "Topic cluster strategy"
41	- "Cornerstone content"
42	- "Pillar page for [topic]"
43
44	## Step-by-Step Process
45
46	### Phase 1: Pillar Topic Selection
47	A pillar topic must be:
48	- High search volume: 500-5,000+ monthly searches
49	- High business value: Directly related to your product/ICP
50	- Broad enough for clusters: At least 10-15 subtopics
51	- Evergreen: Not news-dependent, will be relevant for years
52	- Competitive but winnable: Check current top 10 — if they're all DR 70+ sites
53	and you're DR 30, pick a different pillar
54
55	### Phase 2: Cluster Mapping
56	Map the pillar's universe:
57	- Core subtopics: 8-12 key areas the pillar must cover
58	- Cluster content: 3-5 detailed articles per subtopic
59	- Question clusters: The 20-30 questions people ask about this topic
60	(from People Also Ask, Reddit, Quora, customer conversations)
61	- Internal link map: Every cluster article links to the pillar. The pillar
62	links to every cluster article. Cluster articles link to each other where relevant.
63
64	### Phase 3: Pillar Page Structure
65	- H1: [Topic]: The Complete Guide (or similar)
66	- Executive summary: 2-3 paragraphs. What this covers, who it's for, key
67	takeaways. This is what Google shows in featured snippets.
68	- Table of contents: Jump links to each section
69	- Section per subtopic: Each H2 covers one subtopic. 200-400 words per section.
70	Link to the full cluster article for "deep dive."
71	- Data & examples: Original data, customer examples, screenshots, case studies
72	- Visual elements: Diagrams, charts, comparison tables, infographics
73	- Expert contributions: Quotes from internal experts, customers, industry voices
74	- Total length: 3,000-5,000 words. Long enough to be comprehensive, not so
75	long that nobody reads it.
76
77	### Phase 4: Internal Linking
78	- Pillar → Cluster: In each pillar section, link to the full cluster article
79	with descriptive anchor text
80	- Cluster → Pillar: Every cluster article links to the pillar with a standard
81	"Part of our [Topic] guide" callout
82	- Cluster → Cluster: Cross-link between related cluster articles
83	- Navigation: The pillar is linked from the main navigation or resource center
84	- New content: Every new article on this topic gets a link from the pillar
85	and links back to the pillar
86
87	### Phase 5: Maintenance & Updates
88	- Quarterly review: Check rankings, traffic, and conversion for the pillar
89	and all cluster content
90	- Annual refresh: Update data, examples, screenshots, and expert quotes.
91	Republish with updated date.
92	- Cluster expansion: Add new cluster articles as you identify new subtopics
93	- Performance optimization: Improve page speed, mobile experience, and
94	Core Web Vitals for the pillar page
95
96	## Output Format
97	Pillar page plan with: topic selection justification, cluster map, content
98	outline, internal linking diagram, and maintenance calendar.
99
100
101
102	## Quality Check
103
104	Before delivering, verify:
105	- [ ] All required sections are complete
106	- [ ] Output matches the user's stated need
107	- [ ] Named frameworks are cited for key recommendations
108	- [ ] No vague claims — every recommendation has a specific action
109	- [ ] Deliverable is ready for operational use, not just conceptual
110
111	## Common Pitfalls
112
113	1. Writing for search engines, not humans. Keyword-stuffed content that reads like a robot wrote it. Fix: write for your ICP first, optimize for search second.
114	2. Publishing and praying. Creating content without a distribution plan. Fix: every piece gets a 30-day promotion calendar across email, social, and paid.
115	3. Ignoring content freshness. 2-year-old content with outdated data and examples still ranking. Fix: quarterly content audit — update or retire stale pieces.
116
117	## Implementation Depth
118
119	Use this section when the user asks for a finished asset, not a high-level explanation.
120
121	### Diagnostic Questions
122
123	1. What is the primary motion: founder-led, sales-led, product-led, partner-led, or lifecycle-led?
124	2. Which ICP tier is the output for: small business, mid-market, enterprise, or mixed?
125	3. What proof is available today: customer stories, usage data, third-party validation, screenshots, or none?
126	4. What system will execute the work: CRM, sequencer, warehouse, support desk, product analytics, or manual workflow?
127	5. What decision will the user make from this output: launch, prioritize, route, rewrite, score, coach, or measure?
128
129	### Framework Application
130
131	Map the recommendation explicitly to the named frameworks in this skill:
132
133	- HubSpot Topic Cluster Model: apply only the part that directly improves the requested deliverable.
134	- Animalz Content Strategy: apply only the part that directly improves the requested deliverable.
135	- Google Search Central — SEO Starter Guide: apply only the part that directly improves the requested deliverable.
136
137	### Deliverable Standard
138
139	A strong output from this skill includes:
140
141	- A crisp diagnosis of the current situation
142	- A recommended path with tradeoffs, not a generic list
143	- A concrete artifact the user can use immediately: table, script, checklist, scorecard, sequence, dashboard spec, or implementation plan
144	- A measurement plan with leading and lagging indicators
145	- Risks and edge cases called out before execution
146
147	### Adaptation Rules
148
149	- For small business: reduce complexity, shorten time-to-value, and prioritize owner/operator clarity.
150	- For mid-market: include workflow ownership, handoffs, integrations, and enablement assets.
151	- For enterprise: include governance, risk, procurement, stakeholder mapping, and proof requirements.
152
153
154	## Execution Artifacts
155
156	- `references/framework-notes.md` — Ahrefs cluster model, Schwartz product-led pillars, Pattern 25 routing
157	- `templates/output-template.md` — Deliverable shell for agent output
158	- `scripts/check-output.py` — Lightweight deliverable validator
159	- `references/seo-strategy-playbook.md` — Repo root: §3 keyword tiers and cluster structure
160	- the `using-gtm-skills` skill — Pattern 25: B2B SEO Stack (step 2)
161
162	## Related Skills
163	- seo-strategy, content-marketing, faq-seo, citation-harvesting, landing-pages
164