aiskillstore/marketplace / skills/aaron-he-zhu/site-structure-optimizer
site-structure-optimizer
VerifiedUse when the user asks to "plan my site structure", "design the page hierarchy / navigation / URL taxonomy", "fix internal linking", or "find orphan pages"; runs two modes — architecture (hierarchy, nav, URL patterns, hub/spoke clusters, Mermaid site maps) and linking (link graph, authority flow, anchor text, orphan disposition, source/target/anchor plan) — and outputs a structure score /100 plus a handoff summary. Not for external backlinks — use offsite-signal-analyzer; not for XML sitemap or indexation issues — use technical-seo-checker. 网站架构/信息架构/站点地图/内链优化
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.4 KB |
| references/link-architecture-patterns.md | markdown | 7.8 KB |
| references/linking-example.md | markdown | 2.7 KB |
| references/linking-templates.md | markdown | 4.3 KB |
| references/mermaid-templates.md | markdown | 3.1 KB |
| references/site-type-patterns.md | markdown | 3.5 KB |
| skill-report.json | config | 59.1 KB |
references/mermaid-templates.md
View on GitHub# Mermaid Templates — site hierarchy & link graph
Copy-paste `mermaid` diagrams for architecture Step 7 (Draw the Site Map) and linking-mode site maps in [SKILL.md](../SKILL.md). Paste any block into a Mermaid renderer. Swap the bracketed labels for real pages. Convention: one subgraph per nav zone; orphans in their own subgraph with no inbound edges; islands are clusters that link among themselves but never back to a pillar.
## 1. Hierarchy tree (L0 → L1 → L2/L3)
```mermaid
graph TD
H[Home /] --> S1[Section /features]
H --> S2[Section /use-cases]
H --> S3[Blog /blog]
S1 --> F1[Reporting /features/reporting]
S1 --> F2[Automation /features/automation]
S3 --> P1[Post /blog/subject-lines]
S3 --> P2[Post /blog/segmentation]
```
## 2. Nav zones (header / footer / sidebar)
```mermaid
graph TD
subgraph Header
H[Home] --> Feat[Features]
H --> Price[Pricing]
H --> CTA[Start free]
end
subgraph Footer
H --> About[About]
H --> Docs[Docs]
H --> Legal[Privacy]
end
```
## 3. Hub/spoke topic cluster
```mermaid
graph TD
P[Pillar: Email marketing] --> A[List building]
P --> B[Subject lines]
P --> C[Segmentation]
A --> P
B --> P
C --> P
A --- B
style P fill:#9C27B0,color:#fff
```
Solid = hub↔spoke links; `---` = cross-links between spokes. Purple = the hub/pillar.
## 4. Orphan & island highlighting
Orphans have no inbound edge; islands cross-link internally but never to a pillar.
```mermaid
graph TD
subgraph Pillars
H[Home] --> P[Pillar: Email]
end
subgraph Cluster
P --> A[List building]
P --> B[Subject lines]
end
subgraph Island
X[Glossary A] --- Y[Glossary B]
end
subgraph Orphans
O[Old promo page]
end
style X fill:#f44336,color:#fff
style Y fill:#f44336,color:#fff
style O fill:#FFC107
```
Color key: **red** (#f44336) = island (reconnect to a pillar or retire); **yellow** (#FFC107) = orphan (add inbound links, noindex, or 301).
## 5. Before / after (linking mode)
```mermaid
graph TD
subgraph Before
Hb[Home] --> Bb[Pillar]
SEGb[Segmentation]
AUTb[Automation]
end
subgraph After
Ha[Home] --> Ba[Pillar]
Ba --> SEGa[Segmentation]
Ba --> AUTa[Automation]
SEGa --> Ba
AUTa --> Ba
end
```
Use `-.301.->` for a planned redirect edge (dotted): `OP[Old promo] -.301.-> B[Pillar]`.
## 6. Color-coding conventions
Apply `style` fills to make the diagnostic view readable at a glance.
```mermaid
graph TD
H[Home] --> F[Features]
H --> N[New section]
H --> R[Deprecated page]
H --> O[Orphan page]
style H fill:#4CAF50,color:#fff
style F fill:#4CAF50,color:#fff
style N fill:#2196F3,color:#fff
style R fill:#f44336,color:#fff
style O fill:#FFC107
```
Key: **green** (#4CAF50) = existing, no change; **blue** (#2196F3) = new page to create; **red** (#f44336) = remove/redirect or island; **yellow** (#FFC107) = orphan/restructure; **purple** (#9C27B0) = hub or CTA.
## Rendering notes
- `graph TD` = top-down; use `graph LR` for wide, shallow sites.
- Keep node labels short (`page name /url`) so the diagram stays readable.
- One subgraph per nav zone keeps orphans and islands visually separate — the point of the map.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |