Back to Skills

Seo Keyword Cluster Builder

SEO keyword clustering with topic organization, content hub architecture, internal linking strategies. Use for content strategy, keyword research, pillar page structures, or encountering cluster organization, hub architecture, internal linking errors.

By secondsky
20230Updated 1 week agoTypeScriptMIT

Skill Content

# SEO Keyword Cluster Builder

## Overview

Organize keywords into thematic topic clusters, develop pillar content strategies, and plan internal linking approaches for improved search engine optimization and content architecture.

## When to Use

- Planning comprehensive content strategy
- Organizing large keyword research lists
- Building topic authority with pillar pages
- Creating content hubs and silos
- Developing internal linking structure
- Prioritizing content creation roadmap

## Instructions

You are an expert at SEO and content architecture. Build topic clusters, plan pillar content, and design internal linking strategies for maximum search visibility.

### Common Trigger Phrases

Users typically request this skill with phrases like:
- "Help me with [keyword organization]"
- "Generate [content cluster plan]"
- "Create [internal linking strategy]"
- "Organize these keywords into topic clusters"
- "Build a content hub architecture for [topic]"

**Example Request:**
> "Help me organize these 30 keywords about email marketing into topic clusters and create a content hub architecture"

### Response Approach

When activated, follow this process:
1. **Understand context and goals**: Clarify user's industry, target audience, and objectives
2. **Generate comprehensive output**: Create detailed cluster analysis with practical structure
3. **Provide actionable recommendations**: Include specific next steps and priorities
4. **Include examples and templates**: Show real-world applications and copy-paste formats
5. **Suggest next steps**: Outline content calendar and implementation timeline

## Core Concepts

### Topic Clusters

A topic cluster consists of:
- **Pillar page**: Comprehensive guide on broad topic (2000-4000 words)
- **Cluster content**: Detailed articles on specific subtopics (800-1500 words each)
- **Internal links**: Bidirectional links connecting all related content

```text
                    [Pillar Page]
                  "Project Management"
                          |
        +----------------+----------------+
        |                |                |
   [Cluster 1]      [Cluster 2]     [Cluster 3]
   "PM Tools"       "PM Methods"    "PM Skills"
        |                |                |
    +--+--+          +--+--+          +--+--+
    |     |          |     |          |     |
  Sub1  Sub2      Sub1  Sub2       Sub1  Sub2
```

### Keyword Clustering Strategy

Group keywords by:
1. **Search intent**: Informational, commercial, transactional
2. **Topic similarity**: Semantic relationships
3. **User journey stage**: Awareness, consideration, decision
4. **Content type**: How-to, comparison, definition, list

## Clustering Process

### Step 1: Analyze Keywords

```markdown
Example keyword list:
- project management software (2.4k vol)
- best project management tools (1.8k vol)
- project management apps (1.2k vol)
- free project management software (900 vol)
- project management tools for small teams (500 vol)
```

### Step 2: Identify Clusters

Group by semantic similarity:

#### Cluster 1: Software Selection
- project management software
- best project management tools
- project management apps
- top pm software

#### Cluster 2: Budget/Pricing
- free project management software
- project management software pricing
- affordable pm tools
- pm software cost

#### Cluster 3: Team Size
- pm tools for small teams
- enterprise project management
- pm for startups
- pm for large organizations

### Step 3: Create Architecture

```markdown
Pillar Page: "Complete Guide to Project Management Software"
├── Cluster 1: Software Selection
│   ├── Best Project Management Tools 2024
│   ├── Project Management Apps Comparison
│   └── Top PM Software Features
├── Cluster 2: Budget & Pricing
│   ├── Free Project Management Software Options
│   ├── PM Software Pricing Guide
│   └── ROI of Project Management Tools
└── Cluster 3: Team Size Solutions
    ├── PM Tools for Small Teams
    ├── Enterprise PM Solutions
    └── Scaling PM Software
```

## Output Format

### Basic Template (Minimal)

For quick results, use this concise format:

```markdown
# SEO Keyword Cluster Builder Output

**Generated**: {timestamp}

---

## Results

[Your formatted output here]

---

## Recommendations

[Actionable next steps]
```

### Detailed Template (Comprehensive)

For thorough analysis, use this expanded format:

```markdown
# SEO Keyword Cluster Analysis

**Generated**: [Date]
**Total Keywords Analyzed**: [X]
**Clusters Identified**: [X]

---

## Cluster 1: [Cluster Name]

**Theme**: [Brief description of topic]
**Search Intent**: [Informational/Commercial/Transactional]
**Estimated Traffic Opportunity**: [Total monthly search volume]

### Keywords (sorted by volume)
1. [keyword] - [search volume] - [difficulty]
2. [keyword] - [search volume] - [difficulty]
3. [keyword] - [search volume] - [difficulty]

### Recommended Content

**Pillar Page**: "[Title]"
- Target length: [words]
- Primary keyword: [keyword]
- Secondary keywords: [list]

**Cluster Content** (3-5 articles):
1. **"[Article title]"**
   - Target keyword: [keyword]
   - Length: [words]
   - Focus: [brief description]

2. **"[Article title]"**
   - Target keyword: [keyword]
   - Length: [words]
   - Focus: [brief description]

### Internal Linking Strategy

```text
[Pillar Page] ←→ [Cluster Article 1]
      ↕               ↕
[Cluster Article 2] → [Cluster Article 3]
```

**Link from Pillar to Clusters**:
- Anchor text: "[keyword phrase]"
- Context: [where in pillar page]

**Link from Clusters to Pillar**:
- Anchor text: "[broader topic phrase]"
- Context: [intro or conclusion]

---

## Cluster 2: [Next Cluster Name]
[Repeat structure]

---

## Content Priority Roadmap

### Phase 1: Foundation (Months 1-2)
1. Create pillar page for Cluster 1
2. Write top 3 cluster articles (highest volume keywords)
3. Implement internal linking structure

### Phase 2: Expansion (Months 3-4)
1. Add remaining Cluster 1 articles
2. Create pillar page for Cluster 2
3. Write Cluster 2 core articles

### Phase 3: Depth (Months 5-6)
1. Add supporting content for both clusters
2. Create comparison/versus articles
3. Add FAQ sections for featured snippets

---

## Implementation Checklist

**Pillar Page Requirements**:
- [ ] Comprehensive coverage of topic (2000-4000 words)
- [ ] Links to all cluster articles
- [ ] Table of contents with anchor links
- [ ] Target primary keyword with variations
- [ ] Include multimedia (images, videos, infographics)
- [ ] FAQ section for featured snippets

**Cluster Article Requirements**:
- [ ] Deep dive into specific subtopic (800-1500 words)
- [ ] Link to pillar page (contextual anchor)
- [ ] Link to 2-3 related cluster articles
- [ ] Target long-tail keyword
- [ ] Include examples and actionable tips

**Technical SEO**:
- [ ] Optimize meta titles and descriptions
- [ ] Create descriptive URLs (keyword-rich slugs)
- [ ] Add alt text to all images
- [ ] Implement schema markup (Article/FAQ)
- [ ] Ensure mobile responsiveness
- [ ] Check page load speed

---

## Recommendations

### Next Steps
1. [Specific actionable step]
2. [Specific actionable step]
3. [Specific actionable step]

### Additional Opportunities
- [Content gap or keyword opportunity]
- [Internal linking improvement]
- [Topic expansion suggestion]
```

## Best Practices

### 1. Be Specific
- Focus on concrete, actionable outputs
- Provide exact content titles and structures
- Include specific word counts and keyword targets

### 2. Use Templates
- Provide copy-paste ready formats
- Include examples that users can adapt
- Show clear content hierarchies

### 3. Include Examples
- Demonstrate real-world usage
- Show before/after content organization
- Provide sample anchor text and link placements

### 4. Add Context
- Explain why recommendations matter
- Include search volume and difficulty data
- Estimate traffic opportunity

### 5. Stay Current
- Use latest SEO best practices
- Consider current search algorithm priorities
- Include content freshness strategies

## Common Clustering Patterns

### Pattern 1: Feature-Based

```text
Pillar: "Email Marketing Software"
├── Email Marketing Features
├── Email Marketing Automation
├── Email Marketing Analytics
└── Email Marketing Templates
```

### Pattern 2: Problem-Solution

```text
Pillar: "CRM for Small Business"
├── How to Choose a CRM
├── CRM Implementation Guide
├── CRM Best Practices
└── Common CRM Mistakes
```

### Pattern 3: Comparison-Based

```text
Pillar: "Project Management Tools Comparison"
├── Asana vs Monday.com
├── Trello vs ClickUp
├── Best Free PM Tools
└── PM Tools for Remote Teams
```

### Pattern 4: Stage-Based

```text
Pillar: "Content Marketing Guide"
├── Content Strategy Planning
├── Content Creation Process
├── Content Distribution Channels
└── Content Performance Measurement
```

## Keyword Research Integration

### Organize by Intent

**Informational Intent**:
- "what is [topic]"
- "how to [action]"
- "[topic] guide"
- "[topic] examples"

**Commercial Intent**:
- "best [product]"
- "[product] comparison"
- "[product] review"
- "top [product] for [use case]"

**Transactional Intent**:
- "[product] pricing"
- "buy [product]"
- "[product] discount"
- "[product] free trial"

### Search Volume Tiers

```markdown
High Volume (>1000/month):
- Primary pillar page targets
- High priority for content creation
- Competitive but high reward

Medium Volume (100-1000/month):
- Cluster article targets
- Good balance of difficulty and opportunity
- Build topic authority

Long-Tail (<100/month):
- Supporting content targets
- Lower competition
- Easier to rank, good for starting
```

## Internal Linking Guidelines

### Anchor Text Best Practices

**Good Examples**:
- "project management best practices"
- "how to implement agile methodology"
- "comparison of top CRM platforms"

**Bad Examples**:
- "click here" ❌ (not descriptive)
- "this article" ❌ (no keyword context)
- "project management project management" ❌ (stuffing)

### Link Structure

**Hub-and-Spoke Model**:
```text
Every cluster article links:
→ To pillar page (1 link)
→ To 2-3 related cluster articles (lateral links)
← From pillar page (receives link)
```

**Link Frequency**:
- Pillar to cluster: 1-2 contextual links
- Cluster to pillar: 1 link (introduction or conclusion)
- Cluster to cluster: 2-3 related links

## Content Calendar Template

```markdown
| Month | Week | Content Type | Title | Target Keyword | Status |
|-------|------|--------------|-------|----------------|--------|
| Jan | 1 | Pillar | [Title] | [keyword] | Planning |
| Jan | 2 | Cluster | [Title] | [keyword] | In Progress |
| Jan | 3 | Cluster | [Title] | [keyword] | Not Started |
| Jan | 4 | Cluster | [Title] | [keyword] | Not Started |
| Feb | 1 | Cluster | [Title] | [keyword] | Not Started |
```

## Success Metrics

### Track These KPIs

**Traffic Metrics**:
- Organic sessions per cluster
- Click-through rate from search
- Pages per session (internal link effectiveness)

**Ranking Metrics**:
- Average position for target keywords
- Number of keywords ranking in top 10
- Featured snippet wins

**Engagement Metrics**:
- Time on page
- Bounce rate
- Internal link click rate

**Authority Metrics**:
- Backlinks to pillar pages
- Domain authority growth
- Social shares per cluster

## Example Workflow

### User Request
"Help me organize these 30 keywords about email marketing into topic clusters"

### Your Response Process

1. **Analyze keywords** → Identify themes
2. **Group by similarity** → Create 3-4 main clusters
3. **Recommend structure** → Pillar + cluster content
4. **Suggest titles** → SEO-optimized content titles
5. **Plan linking** → Internal link strategy
6. **Prioritize** → Content creation roadmap
7. **Provide template** → Formatted output ready to use

---

## Philosophy

> "Focus on delivering value quickly and clearly!"

Build topic authority by creating comprehensive, interconnected content that serves user intent better than competitors. Topic clusters help search engines understand your expertise while providing users with complete information on their chosen topic.

How to use

  1. Copy the skill content above
  2. Create a .claude/skills directory in your project
  3. Save as .claude/skills/claude-skills-seo-keyword-cluster-builder.md
  4. Use /claude-skills-seo-keyword-cluster-builder in Claude Code to invoke this skill

Claude Code Skills Collection

142 production-ready skills for Claude Code CLI

Version 3.5.0 | Last Updated: 2026-07-18

<div align="center">

🔌 Platform Support

This repository uses Claude Plugin Patterns — natively supported by:

PlatformStatusNotes
Claude CodeNativeFull marketplace support
Factory DroidNativeFull marketplace support
</div> **For all other Platforms like opencode, codex and others, you can use https://github.com/enulus/OpenPackage **

A curated collection of battle-tested skills for building modern web applications with Cloudflare, AI integrations, React, Tailwind, and more.

PS: if skills.sh warns about any skill: Their scan process is a outdated LLM which flags newest versions pins (like in ZOD) as non existent and by that potentially malicous.


Quick Start

Marketplace Installation (Recommended)

# Add the marketplace
/plugin marketplace add https://github.com/secondsky/claude-skills

# Install individual skills as needed
/plugin install cloudflare-d1@claude-skills
/plugin install tailwind-v4-shadcn@claude-skills
/plugin install gemini-cli@claude-skills

See MARKETPLACE.md for complete catalog of all 139 skills.

Bulk Installation (Contributors)

# Clone the repository
git clone https://github.com/secondsky/claude-skills.git
cd claude-skills

# Install all 139 skills at once
./scripts/install-all.sh

# Or install individual skills
./scripts/install-skill.sh cloudflare-d1

Repository Structure

This repository contains 139 production-tested skills for Claude Code, each focused on a specific technology or capability.

Individual Skills: Each skill is a standalone unit with:

  • SKILL.md - Core knowledge and guidance
  • Templates - Working code examples
  • References - Extended documentation
  • Scripts - Helper utilities

Installation Options:

  1. Individual - Install only the skills you need via marketplace
  2. Bulk - Install all 139 skills using ./scripts/install-all.sh

Available Skills (139 Individual Skills)

Each skill is individually installable. Install only the skills you need.

Full Catalog: See MARKETPLACE.md for detailed listings.

Categories

CategorySkillsExamples
tooling22turborepo, plan-interview, code-review
frontend26nuxt-v4, nuxt-v5, tailwind-v4-shadcn, tanstack-query, nuxt-studio, maz-ui, threejs
cloudflare21cloudflare-d1, cloudflare-workers-ai, cloudflare-agents
api16api-design-principles, graphql-implementation
ai7gemini-cli, ml-model-training, tanstack-ai
web10hono-routing, firecrawl-scraper, web-performance
security5csrf-protection, xss-prevention
mobile5react-native-app, react-native-skills
woocommerce4woocommerce-backend-dev
testing4vitest-testing, playwright-testing
design4design-review, design-system-creation
auth4better-auth
architecture3microservices-patterns, architecture-patterns
data2recommendation-engine, recommendation-system
cms2hugo, wordpress-plugin-core
database1drizzle-orm-d1
seo2seo-optimizer, seo-keyword-cluster-builder
documentation1technical-specification

How It Works

Auto-Discovery

Claude Code automatically checks ~/.claude/skills/ for relevant skills before planning tasks:

User: "Set up a Cloudflare Worker with D1 database"
           ↓
Claude: [Checks skills automatically]
           ↓
Claude: "Found cloudflare-d1 skills.
         These prevent 12 documented errors. Use them?"
           ↓
User: "Yes"
           ↓
Result: Production-ready setup, zero errors, ~65% token savings

Note: Due to token limits, not all skills may be visible at once. See ⚠️ Important: Token Limits below.

Skill Structure

Each skill includes:

skills/[skill-name]/
├── SKILL.md              # Complete documentation
├── .claude-plugin/
│   └── plugin.json       # Plugin metadata
├── templates/            # Ready-to-copy templates
├── scripts/              # Automation scripts
└── references/           # Extended documentation

Recent Additions

July 2026

Offensive Security (new category):

  • cybersecurity — Unified OSS-only cybersecurity skill with progressive disclosure. Fuses 7 community skills (mukul975 business-logic/XSS/host-header/forced-browsing/open-redirect, rysweet/amplihack cybersecurity-analyst, Aradotso security-detections-mcp) ported to fully open-source tooling (OWASP ZAP, Dalfox, ffuf, Nuclei, mitmproxy, interact.sh, Semgrep, Sigma). Covers threat modeling (STRIDE/PASTA/VAST, MITRE ATT&CK), web-vuln testing, SAST, code audit, AI/LLM-app security, and detection engineering. Live-target testing is gated behind an authorization disclaimer; static analysis, code review, and threat modeling are always available. Cross-references the 5 existing defensive security plugins (csrf-protection, xss-prevention, vulnerability-scanning, security-headers-configuration, defense-in-depth-validation) for remediation. Integrates 20 Aradotso dev-security skills across 5 grouped reference docs.

May 2026

Supply Chain Security (cross-cutting):

  • dependency-upgrade expanded with Socket CLI integration — proactive malicious package detection, typosquatting alerts, and CI/CD security gates. New 418-line reference guide, 2 GitHub Actions templates, and expanded supply chain security comparison (3 tools)
  • 31 skills now include "Secure Installation" guidance — contextually-tailored security sections across all high-risk skill categories (scaffolding, MCP/agent SDKs, multi-provider installs, Docker, CI/CD). Covers 8 Bun skills, 5 Nuxt skills, 6 Cloudflare skills, 4 AI/agent skills, and 8 frontend/tooling skills
  • Supply chain security is now a first-class cross-cutting concern woven into the skill collection — not a standalone topic

February - April 2026

Full-Stack Frameworks:

  • nuxt-v5 (v1.0.0) - Full Nuxt 5 support with 4 skills (core, data, server, production), 3 diagnostic agents, and interactive setup wizard
  • threejs (v1.0.0) - 3D web graphics: scenes, geometries, shaders, animations, post-processing

Infrastructure:

  • JSON schema validation - Automated plugin.json validation with CI support
  • GitHub issue templates - Skill-specific issue templates for bug reports, feature requests, and submissions

Plugin Enhancements:

  • mutation-testing - Added Bun native runner support
  • dependency-upgrade - Added supply chain security content

December 2025 - January 2026

Frontend Expansion:

  • nuxt-studio (v1.0.0) - Visual CMS for Nuxt Content with live preview, OAuth auth, and R2 storage integration
  • maz-ui (v1.0.0) - 50+ Vue/Nuxt components with theming, i18n, form generation, and 14 composables

Developer Workflow:

  • plan-interview (v2.0.0) - Adaptive interview-driven spec generation with autonomous quality review
  • turborepo (v2.8.0) - Updated to official Vercel skill with enhanced monorepo build optimization

Mobile Development:

  • react-native-skills (v1.0.0) - React Native & Expo best practices with performance optimization patterns

Enhanced Authentication:

  • better-auth (v2.2.0) - Expanded to 18 framework integrations with 30+ authentication plugins

⚠️ Important: Token Limits

Skill Visibility Constraint

Claude Code has a 15,000 character limit for the total size of skill descriptions in the system prompt. This limit also applies to commands and agents.

What this means:

  • Not all 139 skills may be visible in Claude's context at once
  • Skills are loaded based on relevance and available token budget
  • You can verify how many skills Claude currently sees by asking: "How many skills do you see in your system prompt?"

Checking Visible Skills

To verify which skills are currently loaded:

# Ask Claude Code directly
"Check what skills/plugins you see in your system prompt"

Claude will report something like: "85 of 139 skills visible due to token limits"

Workaround: Increase Token Budget

You can double the headroom for skill descriptions by setting an environment variable:

# Increase limit to 30,000 characters
export SLASH_COMMAND_TOOL_CHAR_BUDGET=30000

# Then launch Claude Code
claude

This gives you approximately 2x more skill visibility in the system prompt.

Note: This is a temporary workaround. The Claude Code team is working on better solutions for skill discovery and loading.


Token Efficiency

MetricManual SetupWith SkillsSavings
Average Tokens12,000-15,0004,000-5,000~65%
Typical Errors2-4 per service0 (prevented)100%
Setup Time2-4 hours15-45 minutes~80%

Across all 139 skills: 400+ documented errors prevented.


Contributing

Prerequisites for Contributors

Install the official plugin development toolkit:

/plugin install plugin-dev@claude-code-marketplace

This provides:

  • /plugin-dev:create-plugin command (8-phase guided workflow)
  • 7 comprehensive skills (hooks, MCP, structure, agents, commands, skills)
  • 2 specialized agents (agent-creator, plugin-validator)

Quick Steps

  1. Create skill directory in plugins/
  2. Add SKILL.md with YAML frontmatter
  3. Run ./scripts/sync-plugins.sh
  4. Submit pull request

See CONTRIBUTING.md and PLUGIN_DEV_BEST_PRACTICES.md for detailed guidelines.


Documentation

DocumentPurpose
START_HERE.mdStart here! Quick navigation guide
PLUGIN_DEV_BEST_PRACTICES.mdRepository-specific best practices (marketplace, budget, quality)
MARKETPLACE.mdFull skill catalog and installation guide
MARKETPLACE_MANAGEMENT.mdTechnical infrastructure (plugin.json, scripts, validation)
CLAUDE.mdProject context and development standards
CONTRIBUTING.mdContribution guidelines

Links


Built with ❤️ by Claude Skills Maintainers

View source on GitHub