seo cluster

Other Community

Skill notes

Quick Reference

Command · What it does /seo cluster plan <seed-keyword> · Full planning workflow: expand, cluster, architect, visualize /seo cluster plan --from strategy · Import from existing /seo plan output /seo cluster execute · Execute plan: create content via claude-blog or output briefs /seo cluster map · Regenerate the interactive cluster visualization

Step 1: Seed Keyword Expansion

Expand the seed keyword into 30-50 variants using WebSearch: Related searches — Search the seed, extract "related searches" and "people also search for" People Also Ask (PAA) — Extract all PAA questions from SERP results Long-tail modifiers — Append common modifiers: "best", "how to", "vs", "for beginners", "tools", "examples", "guide", "template", "mistakes", "checklist" Question mining — Generate who/what/when/where/why/how variants

Step 2: SERP Overlap Clustering

This is the core differentiator. Load references/serp-overlap-methodology.md for the full algorithm. Process: Group keywords by initial intent guess (reduces pairwise comparisons) For each candidate pair within a group, WebSearch both keywords

Step 3: Intent Classification

Classify each keyword into one of four intent categories: Intent · Signals · Include in Clusters? Informational · how, what, why, guide, tutorial, learn · Yes Commercial · best, top, review, comparison, vs, alternative · Yes Transactional · buy, price, discount, coupon, order, sign up · Yes

Step 4: Hub-and-Spoke Architecture

Load references/hub-spoke-architecture.md for full specifications. Design the cluster structure: Select the pillar keyword — Highest volume, broadest intent, most SERP overlap with other keywords Group spokes into clusters — Each cluster is a subtopic area (2-5 clusters per pillar) Assign posts to clusters — Each cluster gets 2-4 spoke posts

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@AgriciDaniel · no license declared
Token usage
Moderate
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
Python
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Seed Keyword Expansion

Expand the seed keyword into 30-50 variants using WebSearch: Related searches — Search the seed, extract "related searches" and "people also search for" People Also Ask (PAA) — Extract all PAA questions from SERP results Long-tail modifiers — Append common modifiers: "best", "how to", "vs", "for beginners", "tools", "examples", "guide", "template", "mistakes", "checklist" Question mining — Generate who/what/when/where/why/how variants

02
Step 2: SERP Overlap Clustering

This is the core differentiator. Load `references/serp-overlap-methodology.md` for the full algorithm. Process: Group keywords by initial intent guess (reduces pairwise comparisons) For each candidate pair within a group, WebSearch both keywords

03
Step 3: Intent Classification

Classify each keyword into one of four intent categories: Intent · Signals · Include in Clusters? Informational · how, what, why, guide, tutorial, learn · Yes Commercial · best, top, review, comparison, vs, alternative · Yes Transactional · buy, price, discount, coupon, order, sign up · Yes

04
Step 4: Hub-and-Spoke Architecture

Load `references/hub-spoke-architecture.md` for full specifications. Design the cluster structure: Select the pillar keyword — Highest volume, broadest intent, most SERP overlap with other keywords Group spokes into clusters — Each cluster is a subtopic area (2-5 clusters per pillar) Assign posts to clusters — Each cluster gets 2-4 spoke posts

05
Step 5: Internal Link Matrix

Design the bidirectional linking structure: Link Type · Direction · Requirement Spoke to pillar · spoke -> pillar · Mandatory (every spoke) Pillar to spoke · pillar -> spoke · Mandatory (every spoke) Spoke to spoke (within cluster) · spoke <-> spoke · 2-3 links per post

06
Step 6: Interactive Cluster Map

Generate `cluster-map.html` using the template at `templates/cluster-map.html`. Read the template file Build the `CLUSTER_DATA` JSON object from the cluster plan: Replace the `CLUSTER_DATA` placeholder in the template with the actual JSON Write the completed HTML file to the output directory

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.