pillar-content
Hub-and-cluster authority content. OmniSkill Social crew — builds a comprehensive pillar page with supporting cluster articles and the internal linking that makes the structure work.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 9
- Forks
- 0
01 前言 Front Matter
- name
- pillar-content
- description
- Hub-and-cluster authority content. OmniSkill Social crew — builds a comprehensive pillar page with supporting cluster articles and the internal linking that makes the structure work.
- disable-model-invocation
- true
03 SKILL.md 正文
Pillar Content
Hub-and-cluster authority · OmniSkill Social crew
One comprehensive pillar page on a broad topic, surrounded by cluster articles covering sub-topics in depth, all deliberately interlinked.
Why the structure works
Three effects compound:
- Demonstrated coverage. A site with a pillar and fifteen supporting pieces on a subject visibly knows that subject better than a site with one post.
- Internal link equity. Clusters link to the pillar, concentrating authority where it competes for the hardest term.
- Query coverage. The pillar catches broad head terms; clusters catch specific long-tail ones. Together they cover a topic's full search surface.
The structure is the point. A pillar page with no clusters is just a long article; clusters with no pillar are scattered posts.
1. Choose the pillar topic
It must be:
- Broad enough to support 10+ genuine sub-topics
- Narrow enough to actually cover comprehensively
- Commercially relevant — connected to what the business sells
- Winnable at current domain authority
"Marketing" is too broad. "Email subject lines" is too narrow. "Email marketing for e-commerce" is a pillar.
Source topics from /omniskill:content-strategy rather than brainstorming.
2. Build the pillar page
Comprehensive, not exhausting. Cover every major sub-topic well enough to be genuinely useful standalone, then link out to the cluster piece for depth. The pillar is a map with real terrain, not a table of contents.
Structure:
- Clear definition and scope up front — answer the head query in the first paragraph
- A section per major sub-topic, each self-contained and useful
- A contextual link from each section to its cluster article
- Table of contents with anchor links for anything long
- Original data, frameworks, or visuals that exist nowhere else
Length follows coverage, not a target. Typically 2,000–5,000 words, but a 2,000-word pillar that covers the topic beats a padded 6,000-word one.
Make it linkable. Original research, a useful framework, or a genuinely definitive resource earns external links. Pillars are the pages worth building links to.
3. Build the clusters
Each cluster article:
- Covers one sub-topic in real depth
- Stands alone as useful — never a stub existing only to link
- Links back to the pillar with descriptive anchor text
- Links sideways to sibling clusters where genuinely relevant
- Targets a specific long-tail query
Aim for 8–15 clusters per pillar. Publish the pillar first, then clusters steadily.
4. Get the internal linking right
This is where most implementations fail.
- Every cluster links up to the pillar. Non-negotiable — this is the mechanism.
- The pillar links down to every cluster. Update it as each publishes; a pillar that never gets updated leaves clusters orphaned.
- Clusters link to relevant siblings, not to all of them indiscriminately.
- Descriptive anchor text — the target's topic, not "click here" and not the same exact-match phrase every time.
- Contextual placement in the body, which carries more weight than a footer link block.
5. Maintain
Pillars decay. Review quarterly: refresh statistics and dates, add clusters as new sub-topics emerge, update links, consolidate clusters that have started competing with each other for the same query.
A well-maintained pillar compounds for years. An abandoned one slides steadily.
6. Measure at cluster level
Judge the cluster as a unit, not article by article. Track combined organic traffic, pillar ranking for the head term, cluster rankings for long-tail, internal link flow, and conversions.
Expect 3–6 months before the structure shows its effect. Judging at week four kills strategies that were working.
Output
Pillar outline with sections, the cluster list with target queries, the internal linking map, the publication sequence, and the maintenance schedule.
Checks before delivering
- Pillar is broad enough for 10+ sub-topics and narrow enough to cover.
- Every cluster is independently useful.
- Every cluster links to the pillar; the pillar links to every cluster.
- Anchor text is descriptive and varied.
- Something on the pillar is genuinely original.
- Maintenance cadence is scheduled.
04 同仓库更多 Skills
xlsx
Excel with live formulas. OmniSkill Operations crew — adapter for the xlsx skill, which installs separately.
webapp-testing
Browser-test a web app. OmniSkill Developers crew — drives a real browser to verify user flows, catches console and network errors, and writes tests that do not flake.
web-artifacts
shadcn HTML artifacts. OmniSkill Design crew — bundled copy of the Web Artifacts skill.
video
Script and produce video. OmniSkill Social crew — structures short-form and long-form video around retention, with shot lists, captions, and platform-specific delivery.
vgpu
暂无简介
uisfx
暂无简介