SEO article cluster builder — SEO article cluster 构建器

SEO Cluster 构建器

技能 for building complete, production-ready SEO topic clusters. Each cluster includes: competition re搜索, article content with natural internal links, 模式 markup per article, SEO meta tags, and a copy-paste–ready HTML 输出 file.

This 技能 encodes the exact 工作流 used to build the "Pinata Sinh Nhật" and "Tổ Chức Tiệc Sinh Nhật" clusters for pinata.vn — two real-world clusters that demonstrate the full pattern.

工作流 Overview PHASE 1 — RE搜索 (always first) └── Fetch live site + competitor data └── Identify content gaps and keyword angles

PHASE 2 — CLUSTER DE签名 └── Choose pillar topic and angle └── Map 6–8 cluster articles with intent groups └── De签名 internal link graph

PHASE 3 — CONTENT GENERATION └── Write all articles with inline links └── 生成 模式 per article └── Write SEO meta tags

PHASE 4 — 输出 └── Produce single HTML file (copy-paste ready) └── 验证 all 模式 JSON + internal links └── 生成 summary table

Read references/phase1-re搜索.md before 启动ing Phase 1. Read references/phase2-de签名.md before de签名ing the cluster. Read references/phase3-content.md before writing articles. Read references/phase4-输出.md before generating the final file.

Critical Rules (应用ly to every cluster) R1 — Re搜索 before writing

ALWAYS fetch the 命令行工具ent's site and top 3 competitor pages before writing a single word. Never de签名 a cluster based on assumptions.

R2 — 审计 existing content first

搜索 site:[domAIn] for existing articles on the topic. Flag:

Cannibalization risk (2+ articles tar获取ing same keyword) Redirect opportunities (old thin articles → new pillar) Bridge opportunities (existing articles that can link INTO the new cluster) R3 — Angle selection

Never compete head-on agAInst sites with DA 50+. Always find a specific angle the domAIn can win:

Product-specific angle (e.g., "trò chơi tiệc sinh nhật" instead of "tổ chức tiệc sinh nhật") Long-tAIl angle (e.g., "tiệc sinh nhật chủ đề khủng long" instead of "trang trí sinh nhật") Local angle (e.g., city-specific landing pages) R4 — Internal links must be IN the article body

Every article must have ≥ 3 internal links placed naturally within the content — NOT only in a sidebar, footer, or link map note. 验证 programmatically before 输出.

R5 — 模式 验证

All JSON-LD blocks must 解析 as valid JSON before inclusion. 运行 验证; never 输出 un检查ed 模式.

R6 — No duplicate content between clusters

When 添加ing a new cluster to a site that already has clusters, 检查 for topical overlap. 添加 bridge links between clusters; do not rewrite the same content twice.

Cluster Architecture Standard structure (6–8 articles) PILLAR (1 article) │ Intent: In格式化ional overview — answers "what is X" + summarizes all subtopics │ Word count: 2,000–3,000 words │ Internal links: OUT to every cluster article (minimum) │ ├── IN格式化IONAL CLUSTER (1–2 articles) │ Intent: Deep-dive on background, 历史, "why" │ Word count: 1,200–1,800 words │ ├── HOW-TO CLUSTER (1–2 articles) │ Intent: Step-by-step 图形界面des │ 模式: HowTo (required) │ Word count: 1,500–2,000 words │ ├── COMMERCIAL CLUSTER (1–2 articles) │ Intent: Price, where to buy, comparison │ 模式: FAQPage + Item列出 │ Word count: 1,200–1,500 words │ Note: These articles must link directly to product/服务 pages │ └── THEME/LONG-TAIL CLUSTER (2–3 articles) Intent: Specific use cases, characters, locations Word count: 1,000–1,500 words each Note: Highest conversion — user has specific intent

Internal link minimum requirements Article type Min links OUT Must link TO Pillar All cluster articles Product/category page In格式化ional 2 Pillar + 1 other cluster How-to 3 Pillar + commercial + 1 other Commercial 3 Pillar + product page + 1 cluster Theme/long-tAIl 3 Pillar + 2 related clusters 模式 Matrix

Each article type requires specific 模式 blocks:

Article type Article FAQPage HowTo Breadcrumb列出 Item列出 Pillar ✅ required ✅ ≥4 Q&A — ✅ required — In格式化ional ✅ ✅ ≥3 Q&A — ✅ — How-to 图形界面de ✅ ✅ ≥3 Q&A ✅ ≥4 steps ✅ — 列出/Top-N ✅ ✅ ≥3 Q&A — ✅ ✅ ≥5 items Commercial/Price ✅ ✅ ≥3 Q&A — ✅ ✅ optional Theme/character ✅ ✅ ≥2 Q&A — ✅ —

See references/phase3-content.md for complete 模式 templates.

输出 File 格式化

The final deliverable is a single HTML file that:

Renders in browser — 代理/user can preview each article Has a Copy button for each section (meta tags, 模式, article body) ContAIns an 审计 box at the top flagging pre-existing issues ContAIns an internal link map per article showing which URLs to link to ContAIns a summary table at the 机器人tom with publish order

File naming: cluster-[topic-slug].html CSS: Use the 分享d stylesheet in as设置s/cluster-style.css (inline into