What makes Site Structure Optimizer notable?

1.3K downloads. Trust evidence available

How should Site Structure Optimizer be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Site Structure Optimizer

Use when the user asks to "plan my site structure", "design the page hierarchy / navigation / URL taxonomy", "fix internal linking", or "find orphan pages";...

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.3k

Updated

Oct 10, 2026

Version

19.0.0

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.3K downloads reported by the source. Last updated 10/10/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 10, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 10, 2026
Adoption signal: 1.3K downloadsadoption · observed Oct 10, 2026
Latest release: 19.0.0release · observed Jul 24, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17e1tg8pjra8dn1dvtq21sahx83hrxj:site-structure-optimizer

Install using `clawhub skill install s17e1tg8pjra8dn1dvtq21sahx83hrxj:site-structure-optimizer` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/aaron-he-zhu/site-structure-optimizer before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-aaron-he-zhu-site-structure-optimizer/snapshot"

Documentation

CLAWHUB

146,077 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: site-structure-optimizer
slug: site-structure-optimizer
displayName: "Site Structure Optimizer · 网站架构"
summary: "网站架构/信息架构/站点地图/内链优化"
description: 'Use 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. 网站架构/信息架构/站点地图/内链优化'
version: "19.0.0"
license: Apache-2.0
compatibility: "Claude Code and compatible agent-skill hosts"
homepage: "https://github.com/aaron-he-zhu/aaron-marketing-skills"
when_to_use: "Use when planning or restructuring a site (page hierarchy, navigation, URL taxonomy, hub/spoke topic clusters, visual sitemap) OR when fixing internal link structure (orphan pages, anchor-text distribution, authority flow, crawl depth). One skill, two altitudes: architecture designs the structure; linking optimizes the links inside it."
argument-hint: "[--mode architecture|linking] <domain, sitemap, or page list + site type>"
metadata: {"author": "aaron-he-zhu", "version": "19.0.0", "discipline": "seo-geo", "phase": "tune", "geo-relevance": "high", "hermes": {"tags": ["marketing", "seo-geo", "tune"], "category": "seo-geo"}, "openclaw": {"emoji": "🔍", "homepage": "https://github.com/aaron-he-zhu/aaron-marketing-skills"}}
---

# Site Structure Optimizer

Works one lever of site structure at two altitudes. **Architecture mode** designs the whole-site information architecture — page hierarchy, navigation, URL taxonomy, hub/spoke topic clusters, link topology — and renders Mermaid site maps that make orphans and link islands visible. **Linking mode** optimizes the links inside an existing structure — link graph, authority flow, anchor text, orphan disposition — and delivers a prioritized source/target/anchor plan. Both emit a **structure score /100** and a handoff summary.

**Scope guard**: this skill does not compute the CORE-EEAT score or run vetoes (T04, C01, R10) — that is the `content-quality-auditor` gate. It does not analyze external backlinks (`offsite-signal-analyzer`) or diagnose XML sitemaps / indexation (`technical-seo-checker`). It works the structure lever and hands off.

## Mode Selector

| Mode | Altitude | Use when | Core outputs |
|------|----------|----------|--------------|
| `architecture` | Whole-site layout | New build or restructure; the layout itself is the question | ASCII hierarchy tree, URL map table, nav spec, hub/spoke plan, Mermaid site map, architecture score /100 |
| `linking` | Links inside an existing layout | Pages exist; the question is how they connect | Orphan list + disposition, anchor-text distribution, contextual link p

_meta.json

{
  "ownerId": "kn73qjxwmbna25qq8q051epqt980sys5",
  "slug": "site-structure-optimizer",
  "version": "19.0.0",
  "publishedAt": 1784905895400
}

references/link-architecture-patterns.md

# Link Architecture Patterns (linking mode)

Internal-link topologies, selection thresholds, migration safeguards, and measurement targets. Used at Step 1 (Analyze Current Structure) of [SKILL.md](../SKILL.md) — the avg-links/page target range that drives the −10 score penalty comes from the model chosen here.

## The Five Models

| Model | Shape | Best for | Site-size fit | Authority flow |
|-------|-------|----------|---------------|----------------|
| Hub-spoke (topic cluster) | Pillar links to all spokes; every spoke links back to pillar; spokes cross-link where relevant | Blogs, SaaS use-cases, most content sites | 50–500 content pages | Concentrates authority on the pillar, distributes to spokes |
| Silo | Strict category trees; links stay within a category, minimal cross-links | Docs, large ecommerce categories | 100+ categories or distinct taxonomies | Contains authority within a topic; strong topical signal |
| Flat | Key pages linked from home; shallow URLs; free cross-linking; nav/menu support | Small sites, shallow URL structures | <50 ideal; 50–100 manageable; 100+ difficult | Even, home-centric distribution; little topical concentration |
| Pyramid | Home → category → subcategory → page hierarchy, 3–4 levels max, breadcrumbs | News/media, large blogs, corporate, gov/edu | 500+ posts or a clear hierarchy | Cascades down and back up the hierarchy |
| Mesh | Dense cross-linking across the whole site, few strict boundaries | Small sites (<50 pages), wikis, knowledge bases | Dense topic networks | Even distribution; dilutes topical concentration |

**Default**: hub-spoke. Use silo when topical separation matters more than cross-topic discovery; use flat on small/shallow sites; use pyramid on large hierarchical sites (news, corporate); use mesh only on small sites where every page is broadly relevant to every other.

## Selection Thresholds

Figures are **Estimated** defaults — adjust to the site.

| Signal | Hub-spoke | Silo | Flat | Pyramid | Mesh |
|--------|-----------|------|------|---------|------|
| Page count | 30–500 | 200+ | <50 | 500+ | <50 |
| Distinct topics | 3–15 pillars | many rigid categories | 1–3 | many, hierarchical | 1–2 |
| Cross-topic relevance | medium | low | high | low–medium | high |

## Measurement Targets (per model)

Used in the Step 1 score: `−10 if avg links/page is outside the model's target range`. All **Estimated**.

| Metric | Hub-spoke target | Silo target | Flat target | Pyramid target | Mesh target |
|--------|------------------|-------------|-------------|----------------|-------------|
| Avg internal links per page | 3–10 | 3–8 | 8–15 | 3–5 | 5–15 |
| Inbound contextual links per important page | ≥3 | ≥2 | ≥3 | ≥2 | ≥3 |
| Max click depth for important pages | ≤3 | ≤3 | ≤2 | ≤4 | ≤2 |
| Orphan pages | 0 | 0 | 0 | 0 | 0 |

Outside the target range = under-linked (crawl/authority starvation) or over-linked (diluted anchors, thin PageRank per link).

## Anchor-Text Distribution Targets

Cross-referenc

references/linking-example.md

# Linking Example — worked before/after

One worked internal-linking example for a small blog, referenced from the Example section of [SKILL.md](../SKILL.md). All numbers are **Estimated** and illustrative.

## Setup

A 6-page email-marketing blog. New post: **"Email marketing best practices"** (the pillar). Existing spokes: list-building, subject-lines, segmentation, automation, tools. One legacy page (old-promo) sits with no inbound links.

## Before — link graph

```mermaid
graph TD
  subgraph Site
    H[Home] --> B[Best practices pillar]
    H --> LB[List building]
    H --> SL[Subject lines]
  end
  subgraph Orphans
    SEG[Segmentation]
    AUT[Automation]
    TL[Tools]
    OP[Old promo]
  end
```

Diagnosis (Estimated):
- Pages analyzed: 8 · total internal links: 6 · avg links/page: 0.75 (below hub-spoke target 3–10) → −10
- Orphans: 4 (segmentation, automation, tools, old-promo) → −40
- Pillar has no spoke cross-links; segmentation/automation/tools unreachable
- **Structure score: ~50/100** (100 −10 −40, then floored inputs)

## Contextual Link Plan (Step 5 output)

| # | Source paragraph in pillar | Target | Suggested anchor | Priority |
|---|----------------------------|--------|------------------|----------|
| 1 | "Grow a permission-based list…" | /list-building | building an email list | High |
| 2 | "Write subject lines that earn opens…" | /subject-lines | writing subject lines | High |
| 3 | "Send the right message to the right group…" | /segmentation | audience segmentation | High |
| 4 | "Trigger sequences automatically…" | /automation | email automation | High |
| 5 | "Pick a platform that fits…" | /tools | email marketing tools | Medium |

Each spoke adds one link back to the pillar (spoke → hub). Old-promo has no traffic value → default disposition: 301 to the pillar (see SKILL.md Decision Gate).

## After — link graph

```mermaid
graph TD
  subgraph Pillars
    H[Home] --> B[Best practices pillar]
  end
  subgraph Cluster
    B --> LB[List building]
    B --> SL[Subject lines]
    B --> SEG[Segmentation]
    B --> AUT[Automation]
    B --> TL[Tools]
    LB --> B
    SL --> B
    SEG --> B
    AUT --> B
    TL --> B
  end
  OP[Old promo] -.301.-> B
```

After (Estimated):
- avg links/page: ~2.9 (approaching hub-spoke target) · orphans: 0 · every spoke ≤2 clicks from home
- Anchor mix: 100% descriptive on the 5 new links (no "click here")
- **Structure score: ~95/100** (residual gap: avg links/page still near the low end)

## Takeaway

Adding 5 descriptive contextual links plus 5 return links converted 4 orphans into a reachable cluster and lifted the pillar's inbound signal — no new content, structure only. Broken-target and migration risks (the old-promo 301) hand off to `content-quality-auditor`.

references/linking-templates.md

# Linking Templates (linking-mode steps 3–7)

Copy-paste output templates for linking mode in [SKILL.md](../SKILL.md). Each template maps to one step. Label every metric **Measured**, **User-provided**, or **Estimated**. Threshold defaults live in [Link Architecture Patterns](link-architecture-patterns.md).

## Anchor & Link Rules (apply throughout)

- **Descriptive over generic**: anchor should describe the target ("email segmentation guide"), not "click here" / "read more".
- **Contextual over navigational**: in-body links inside relevant prose carry more weight than menu/footer links. Count them separately.
- **Link-depth budget**: important pages ≤3 clicks from home; each in-body link ≈ 1 unit of PageRank divided among all links on the page — do not exceed the model's avg-links/page target.
- **One primary target per anchor**: avoid pointing the same exact-match anchor at multiple pages.
- **No redirect chains**: link to the final URL.

> Exact-match anchor guidance tightened: the old 10–20% allowance is retired in favor of **<5% per target** (the stricter current scheme) — repeated exact-match anchors above this read as over-optimization.

## Step 3 — Anchor-Text Distribution

```text
Anchor-Text Distribution — [domain]
Data source: [Measured/Estimated]

| Anchor type          | Count | Share | Target        | Flag |
|----------------------|-------|-------|---------------|------|
| Descriptive/topical  |       |    %  | 60–80%        |      |
| Branded/navigational |       |    %  | 10–20%        |      |
| Generic              |       |    %  | <10%          |      |
| Exact-match (repeat) |       |    %  | <5% / target  |      |

Over-optimized anchors (exact-match > threshold): [list target → anchor → count]
Generic anchors to rewrite: [source → current anchor → suggested descriptive anchor]

Anchor Score /10: [n]
  Start 10; −2 if generic >10%; −2 if any exact-match >5% to one target;
  −2 if descriptive <60%; −1 per over-optimized cluster (cap −4). Floor 0.
```

## Step 4 — Topic Cluster Link Strategy

```text
Topic Clusters — [domain]

| Pillar (hub) | Spokes (in-cluster) | Missing hub→spoke | Missing spoke→hub | Cross-links to add |
|--------------|---------------------|-------------------|-------------------|--------------------|
|              |                     |                   |                   |                    |

Recommended structure: [hub-spoke / silo / mesh] — see Link Architecture Patterns
Specific links to add: [source → target → anchor → reason]
```

## Step 5 — Contextual Link Opportunities

```text
Contextual Link Plan — [page or domain]

| # | Source page (+paragraph) | Target URL | Suggested anchor | Priority | Target resolves? |
|---|--------------------------|------------|------------------|----------|------------------|
| 1 |                          |            |                  | High     | Yes/No (404→flag)|

Broken targets flagged for content-quality-auditor (R10): [list]
```

## Step 6 — Navigation

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.