All skills
coreyhaines31 avatar

/site-architecture

@30f9b9a

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

Requires /pricing

Use this Skill: https://skilld.dev/gh/coreyhaines31/marketingskills/site-architecture

This session only. Nothing lands on disk.

referencesmermaid-templates.md

≈1.2k tokens on demand. Your agent reads this file only when SKILL.md points to it.

Mermaid Diagram Templates

Copy-paste-ready Mermaid diagrams for visual sitemaps. Customize node labels and connections for your site.


Basic Hierarchy

Simple top-down page hierarchy.

graph TD
    HOME["Homepage<br/>/"] --> FEAT["Features<br/>/features"]
    HOME --> PRICE["Pricing<br/>/pricing"]
    HOME --> BLOG["Blog<br/>/blog"]
    HOME --> ABOUT["About<br/>/about"]

    FEAT --> F1["Analytics<br/>/features/analytics"]
    FEAT --> F2["Automation<br/>/features/automation"]
    FEAT --> F3["Integrations<br/>/features/integrations"]

    BLOG --> B1["Post: SEO Guide<br/>/blog/seo-guide"]
    BLOG --> B2["Post: CRO Tips<br/>/blog/cro-tips"]

Hierarchy with Navigation Zones

Uses subgraphs to show which pages appear in which navigation area.

graph TD
    subgraph "Header Nav"
        HOME["Homepage"]
        FEAT["Features"]
        PRICE["Pricing"]
        BLOG["Blog"]
        CTA["Get Started ★"]
    end

    subgraph "Feature Pages"
        F1["Analytics"]
        F2["Automation"]
        F3["Integrations"]
    end

    subgraph "Footer Nav"
        ABOUT["About"]
        CAREERS["Careers"]
        CONTACT["Contact"]
        PRIVACY["Privacy"]
        TERMS["Terms"]
    end

    HOME --> FEAT
    HOME --> PRICE
    HOME --> BLOG
    FEAT --> F1
    FEAT --> F2
    FEAT --> F3
    HOME --> ABOUT
    ABOUT --> CAREERS
    HOME --> CONTACT

Hierarchy with URL Labels

Each node shows the page name and URL path.

graph TD
    HOME["Homepage<br/><small>/</small>"] --> PROD["Product<br/><small>/product</small>"]
    HOME --> PRICE["Pricing<br/><small>/pricing</small>"]
    HOME --> BLOG["Blog<br/><small>/blog</small>"]
    HOME --> DOCS["Docs<br/><small>/docs</small>"]
    HOME --> ABOUT["About<br/><small>/about</small>"]

    PROD --> P1["Analytics<br/><small>/product/analytics</small>"]
    PROD --> P2["Reports<br/><small>/product/reports</small>"]

    DOCS --> D1["Getting Started<br/><small>/docs/getting-started</small>"]
    DOCS --> D2["API Reference<br/><small>/docs/api</small>"]

Hub-and-Spoke Content Model

Shows a hub page connected to spoke articles, with spokes linking to each other.

graph TD
    HUB["SEO Guide<br/>(Hub Page)"]

    HUB --> S1["Keyword Research"]
    HUB --> S2["On-Page SEO"]
    HUB --> S3["Technical SEO"]
    HUB --> S4["Link Building"]

    S1 -.-> S2
    S2 -.-> S3
    S3 -.-> S4

    style HUB fill:#f9f,stroke:#333,stroke-width:2px

Legend:

  • Solid lines = primary hub-spoke links
  • Dashed lines = cross-links between spokes

Internal Linking Flow

Shows how different site sections link to each other.

graph LR
    subgraph "Marketing"
        HOME["Homepage"]
        FEAT["Features"]
        PRICE["Pricing"]
    end

    subgraph "Content"
        BLOG["Blog"]
        GUIDE["Guides"]
        CASE["Case Studies"]
    end

    subgraph "Product"
        DOCS["Docs"]
        API["API Ref"]
        CHANGE["Changelog"]
    end

    BLOG --> FEAT
    BLOG --> CASE
    CASE --> FEAT
    CASE --> PRICE
    FEAT --> DOCS
    GUIDE --> BLOG
    GUIDE --> DOCS
    HOME --> FEAT
    HOME --> BLOG
    HOME --> CASE

Before/After Restructuring

Compare current and proposed site structures side by side.

graph TD
    subgraph "Before"
        B_HOME["Homepage"] --> B_P1["Page 1"]
        B_HOME --> B_P2["Page 2"]
        B_HOME --> B_P3["Page 3"]
        B_HOME --> B_P4["Page 4"]
        B_HOME --> B_P5["Page 5"]
        B_HOME --> B_P6["Page 6"]
        B_HOME --> B_P7["Page 7"]
        B_HOME --> B_P8["Page 8"]
    end

    subgraph "After"
        A_HOME["Homepage"] --> A_S1["Features"]
        A_HOME --> A_S2["Resources"]
        A_HOME --> A_S3["Company"]
        A_S1 --> A_P1["Feature A"]
        A_S1 --> A_P2["Feature B"]
        A_S2 --> A_P3["Blog"]
        A_S2 --> A_P4["Guides"]
        A_S3 --> A_P5["About"]
        A_S3 --> A_P6["Contact"]
    end

Color-Coding Conventions

Use styles to highlight page status, priority, or type.

graph TD
    HOME["Homepage"] --> FEAT["Features"]
    HOME --> PRICE["Pricing"]
    HOME --> BLOG["Blog"]
    HOME --> NEW["New Section"]
    HOME --> REMOVE["Deprecated Page"]

    FEAT --> F1["Existing Feature"]
    FEAT --> F2["New Feature"]

    style HOME fill:#4CAF50,color:#fff
    style PRICE fill:#4CAF50,color:#fff
    style FEAT fill:#4CAF50,color:#fff
    style BLOG fill:#4CAF50,color:#fff
    style F1 fill:#4CAF50,color:#fff
    style NEW fill:#2196F3,color:#fff
    style F2 fill:#2196F3,color:#fff
    style REMOVE fill:#f44336,color:#fff

Color key:

  • Green (#4CAF50): Existing pages (no changes)
  • Blue (#2196F3): New pages to create
  • Red (#f44336): Pages to remove or redirect
  • Yellow (#FFC107): Pages to restructure or move
  • Purple (#9C27B0): High-priority / CTA pages

Source: SKILL.md on GitHub

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides comprehensive guidance and templates for planning website architecture, including page hierarchy, navigation design, URL structure, and internal linking. It uses standard markdown, ASCII trees, and Mermaid diagrams to represent structures. No malicious code, data exfiltration, or prompt injection patterns were found.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    4 files scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 30f9b9a. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 hours ago.

Activeupdated 5 months ago
metadata
{
  "version": "2.0.0"
}
  • information-architecture
  • site-structure
  • navigation-design
  • url-structure
  • sitemap
  • page-hierarchy
  • internal-linking
  • web-planning

README badge

README badge for coreyhaines31/marketingskills/site-architecture

Helps plan website page hierarchy, navigation menus, URL structure, and internal linking strategies. Use this when users ask about sitemap structure, information architecture, navigation design, or how to organize website pages—not for XML sitemaps or technical SEO audits.

Generated from the current SKILL.md.

Does this skill help with XML sitemaps?
No. This skill is for planning page hierarchy, navigation, and URL structure. XML sitemaps are handled by the seo-audit skill.
What site types does this cover?
SaaS marketing sites, content/blog sites, e-commerce, documentation, hybrid SaaS+content, and small business sites. The skill includes templates and starting points for each type.
Does this skill include internal linking strategy?
Yes. The skill covers navigational, contextual, hub-and-spoke, and cross-section linking patterns, plus a link audit checklist.
What output formats does this skill provide?
ASCII tree hierarchies, Mermaid visual sitemaps, URL maps, navigation designs, and breadcrumb structures.
Does this skill require existing product marketing context?
The skill checks for product-marketing.md files first to avoid duplicate questions, but will ask for business context, current state, site type, and content inventory if that file doesn't exist.

Generated from the current SKILL.md. These answers refresh after source changes.