fusengine/seo-cluster
plugins/seo/skills/seo-cluster/SKILL.md
Use when building semantic keyword clusters from SERP overlap. Covers seed keyword expansion, Jaccard SERP overlap, intent grouping, pillar/cluster content architecture.
$ install --global
skillsauthnpx skillsauth add fusengine/agents seo-clusterInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 3:42 AM147.5s1 file scanned
SKILL.md
- name:
- seo-cluster
- description:
- Use when building semantic keyword clusters from SERP overlap. Covers seed keyword expansion, Jaccard SERP overlap, intent grouping, pillar/cluster content architecture.
- user-invocable:
- false
- related-skills:
- seo, seo-internal-linking, seo-content, seo-content-brief
Semantic Clustering
Method
- Take seed keyword (e.g. "claude code")
- Fetch SERP for seed via WebFetch/fuse-browser (top 10 results)
- For each related keyword (autocomplete + "People Also Ask"):
- Fetch its SERP
- Compute overlap with seed's SERP (Jaccard index)
- Group keywords where SERP overlap ≥ 30% → same cluster
- Cluster center = highest-volume keyword
Output
# Cluster: "claude code"
## Pillar: claude code (vol: 12K, KD: 45)
- Intent: informational
- Featured: AI Overview, video
## Cluster pages
1. claude code installation (vol: 2.4K)
2. claude code vs cursor (vol: 1.8K)
3. claude code mcp servers (vol: 900)
4. claude code hooks (vol: 720)
Cluster by Buyer State (2026)
SERP overlap is the mechanical signal; the strategic axis is buyer state + intent, not surface similarity. Map each cluster keyword to a layer, then group by layer:
| Layer | State | Intent signal | |-------|-------|---------------| | L1 | Awareness | "what is", "why", problem framing | | L2 | Comparison | "vs", "alternatives", "best for" | | L3 | Evaluation | "pricing", "reviews", "worth it" | | L4 | Decision | "buy", "near me", "demo", "signup" |
Two keywords with high SERP overlap but different buyer states belong to different pages. Never merge clusters on lexical similarity alone.
Citation eligibility
AI Overviews capture ~30-60% of informational (L1/L2) CTR. For those layers, prioritize pages that produce verbatim-extractable answers per section over raw ranking — the goal is the LLM citation, not only the blue link.
Local vs Global Intent (2026)
| Axis | LOCAL intent | GLOBAL intent | |------|--------------|---------------| | Type | Proximity transactional/navigational ("near me", "[service] [city]") | Informational / comparative | | SERP feature | Triggers the Map Pack | AI Overviews-heavy | | AI Overviews exposure | Resists (local results stay link-driven) | CTR eroded -40% to -58% on informational keywords | | Target page | Local page / city hub | Global pillar |
One intent = one URL. Split a local page from the global/pillar page when local volume and content justify it. Do not split if local volume is below ~30 searches/month, or if you cannot write 1200+ words genuinely distinct from the pillar.
Anti-Cannibalization Check
Before creating cluster pages, verify no existing page targets the same buyer state + intent. Use seo-content skill. The primary keyword is exclusive per page — pillar = [service] (no city), local = [service] [city]. See seo-internal-linking for the pillar/local/region URL architecture and link mesh.
Related Skills
fusengine/ux-copy
testing
VerifiedTrustedCommunity
Copy self-audit and ban-lists — filler verbs/hype adjectives, slop placeholder names, fake-precise numbers, Title Case headlines, humor in error copy ('Oops!'), em-dash crutch, one copy register per page.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-webapp
development
VerifiedTrustedCommunity
Logged-in web apps — dashboards, auth flows, settings, onboarding, data tables, command palettes, modals, toasts. Register `product`: density and glance-speed over marketing polish, no hero/CTA-tricks, every data surface covers empty/loading/error explicitly, tables and dataviz follow preattentive-processing rules.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-web
development
VerifiedTrustedCommunity
Marketing sites, landing pages, campaign pages — register `brand` (design IS the product). Structure comes from the register's POV + a macrostructure pick, never from copying an inspiration site's section flow. Hero discipline, deviated section order, asymmetric grids, and a silhouette lookalike-test gate before ship.
20SKILL.mdUpdated Jul 15, 2026
fusengine/design-system
development
VerifiedTrustedCommunity
Token-strategy core — OKLCH color rules, neutral tinting, accent-commitment levels, type scale, 8pt spacing grid, touch targets, and the canonical output format of design-system.md (the file the harness gates on). This is routing step 1 of design-method/SKILL.md — read it before design-web/design-webapp/design-ios/design-android, before picking or auditing a single color/type/spacing value.
20SKILL.mdUpdated Jul 13, 2026