Modo
Agendar llamada

site-architecture: planificar la estructura de tu web

Planifica la estructura de una web nueva o una reestructura: jerarquía de páginas, menú, URLs, migas y enlaces internos, con el mapa del sitio dibujado.

site-architecture: planificar la estructura de tu web

Respuesta rápida

Qué es
site-architecture es una skill de Corey Haines (licencia MIT) que le enseña a Claude a planificar la estructura de tu web: qué páginas necesitas, dónde va cada una, cómo se arman las URLs, el menú y los enlaces internos.
Qué le das
Qué vende tu negocio, las páginas que tienes hoy y el tipo de sitio
Qué te devuelve
El árbol de páginas, un mapa visual en Mermaid, la tabla de URLs, la especificación del menú y el plan de enlaces internos
Licencia
MIT
En GitHub
60,6 mil estrellas · actualizada el
Revisada por Claura

Instálala en una línea para todos tus proyectos, en Claude Code, Cursor, Codex y más:

npx skills add coreyhaines31/marketingskills --skill site-architecture -g

Funciona en

Claude CodeEn ~/.claude/skills/
CursorEn ~/.agents/skills/
CodexEn ~/.agents/skills/

Pedidos para probarla

Con la skill instalada, copia uno y pégaselo a tu agente tal cual, o cambia los datos por los tuyos.

  • Planifica la estructura de la web nueva de un estudio jurídico con cinco áreas de práctica y tres oficinas, con menú, URLs y enlaces internos.

  • Mi tienda online tiene 200 productos mal agrupados. Propón la jerarquía de categorías y las migas.

  • Voy a juntar dos webs en una. Arma el mapa del sitio nuevo y dime qué páginas viejas redirijo a cuáles.

#Qué hace

site-architecture es una skill de Corey Haines (licencia MIT) que convierte a Claude en un arquitecto de información. Primero entiende el negocio, el estado actual del sitio, el tipo de sitio y el inventario de contenido, y después diseña la estructura con reglas concretas:

  • Profundidad según el tipo de sitio: de 1 a 2 niveles para un negocio chico de servicios, de 3 a 4 para una tienda o una documentación grande, con la regla de los tres clics para las páginas importantes.
  • Menú: entre 4 y 7 ítems, el botón de acción a la derecha, el logo a la portada, y el pie agrupado en columnas (producto, recursos, empresa, legales).
  • URLs: legibles, en minúscula, con guiones, que reflejen la jerarquía, sin fechas ni números de ID, y con un patrón por tipo de página (servicios, blog, casos, comparaciones, integraciones, plantillas).
  • Migas que repiten la URL, con cada tramo enlazado.
  • Enlaces internos: cuatro tipos de enlace, el modelo de página pilar con sus páginas satélite, ninguna página huérfana y una lista de control para auditarlos.

La salida tiene cinco piezas: el árbol de páginas en texto, un mapa visual en Mermaid, la tabla de URLs con página madre, lugar en el menú y prioridad, la especificación del menú y el plan de enlaces internos. Sus referencias traen plantillas por tipo de sitio, patrones de navegación, plantillas de Mermaid y una guía de plataformas y migraciones.

#Cómo aplicarla a tu negocio

Caso: una clínica odontológica en Madrid con dos sedes, que hoy tiene una web de una sola página y quiere aparecer en Google por cada tratamiento.

  1. Cuenta el negocio. Tratamientos (implantes, ortodoncia invisible, blanqueamiento, odontopediatría), dos sedes, y que la meta es pedir cita. La skill lo clasifica como negocio de servicios con componente local.
  2. Pide el árbol. Sale algo así: portada, /tratamientos con una página por tratamiento, /clinicas con una página por sede, /casos, /blog y /pedir-cita. Nada a más de dos clics.
  3. Define el menú. Tratamientos, Clínicas, Casos, Blog, y el botón «Pedir cita» a la derecha. En el pie, horarios, teléfono y legales.
  4. Arma los enlaces internos. Cada nota del blog sobre ortodoncia enlaza a la página de ortodoncia invisible, que funciona como pilar; cada sede enlaza a los tratamientos que hace.
  5. Entrégale el plano al equipo. La tabla de URLs y el mapa en Mermaid son lo que necesitan el diseñador y el programador para construir sin improvisar.

Cada tratamiento con su página propia es justamente lo que permite competir en Google por «implantes dentales en Madrid» en lugar de tener todo en una sola página.

#Cómo instalarla

Es una skill agent-agnostic: el mismo SKILL.md corre en cualquier agente. La versión completa incluye sus referencias (plantillas por tipo de sitio, patrones de navegación, plantillas de Mermaid y migraciones) que viven en el repo de origen.

  • Con una línea, para cualquier agente: npx skills add coreyhaines31/marketingskills --skill site-architecture -g la deja instalada en todos tus proyectos.
  • A mano: copia la carpeta skills/site-architecture/ completa, con sus referencias, a ~/.claude/skills/ para Claude Code, o a ~/.agents/skills/ para Cursor, Codex y Gemini CLI (las tres leen esa carpeta).
  • App de Claude: comprime la carpeta en un ZIP y súbela desde Customize, Skills, «Upload a skill».

No pide claves de API. El SKILL.md completo (con la licencia MIT y la fuente) está más abajo.

El SKILL.md completo

Skill original de Corey Haines (MIT). Fuente: github.com/coreyhaines31/marketingskills/tree/main/skills/site-architecture.

El archivo original está en inglés y va tal cual, sin traducir. Lo de arriba de esta ficha es el resumen en español: qué hace, cómo aplicarla y cómo instalarla.

Leer el archivo (366 líneas)

Site Architecture

You are an information architecture expert. Your goal is to help plan website structure — page hierarchy, navigation, URL patterns, and internal linking — so the site is intuitive for users and optimized for search engines.

Before Planning

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context
  • What does the company do?
  • Who are the primary audiences?
  • What are the top 3 goals for the site? (conversions, SEO traffic, education, support)
2. Current State
  • New site or restructuring an existing one?
  • If restructuring: what's broken? (high bounce, poor SEO, users can't find things)
  • Existing URLs that must be preserved (for redirects)?
  • What platform is it on, and is a platform change on the table? (For choosing a platform, adding a section to an existing site, or migrating, see references/platforms-and-migration.md.)
3. Site Type
  • SaaS marketing site
  • Content/blog site
  • E-commerce
  • Documentation
  • Hybrid (SaaS + content)
  • Small business / local
4. Content Inventory
  • How many pages exist or are planned?
  • What are the most important pages? (by traffic, conversions, or business value)
  • Any planned sections or expansions?

Site Types and Starting Points

Site TypeTypical DepthKey SectionsURL Pattern
SaaS marketing2-3 levelsHome, Features, Pricing, Blog, Docs/features/name, /blog/slug
Content/blog2-3 levelsHome, Blog, Categories, About/blog/slug, /category/slug
E-commerce3-4 levelsHome, Categories, Products, Cart/category/subcategory/product
Documentation3-4 levelsHome, Guides, API Reference/docs/section/page
Hybrid SaaS+content3-4 levelsHome, Product, Blog, Resources, Docs/product/feature, /blog/slug
Small business1-2 levelsHome, Services, About, Contact/services/name

For full page hierarchy templates: See references/site-type-templates.md


Page Hierarchy Design

The 3-Click Rule

Users should reach any important page within 3 clicks from the homepage. This isn't absolute, but if critical pages are buried 4+ levels deep, something is wrong.

Flat vs Deep
ApproachBest ForTradeoff
Flat (2 levels)Small sites, portfoliosSimple but doesn't scale
Moderate (3 levels)Most SaaS, content sitesGood balance of depth and findability
Deep (4+ levels)E-commerce, large docsScales but risks burying content

Rule of thumb: Go as flat as possible while keeping navigation clean. If a nav dropdown has 20+ items, add a level of hierarchy.

Hierarchy Levels
LevelWhat It IsExample
L0Homepage/
L1Primary sections/features, /blog, /pricing
L2Section pages/features/analytics, /blog/seo-guide
L3+Detail pages/docs/api/authentication
ASCII Tree Format

Use this format for page hierarchies:

Homepage (/)
├── Features (/features)
│   ├── Analytics (/features/analytics)
│   ├── Automation (/features/automation)
│   └── Integrations (/features/integrations)
├── Pricing (/pricing)
├── Blog (/blog)
│   ├── [Category: SEO] (/blog/category/seo)
│   └── [Category: CRO] (/blog/category/cro)
├── Resources (/resources)
│   ├── Case Studies (/resources/case-studies)
│   └── Templates (/resources/templates)
├── Docs (/docs)
│   ├── Getting Started (/docs/getting-started)
│   └── API Reference (/docs/api)
├── About (/about)
│   └── Careers (/about/careers)
└── Contact (/contact)

When to use ASCII vs Mermaid:

  • ASCII: quick hierarchy drafts, text-only contexts, simple structures
  • Mermaid: visual presentations, complex relationships, showing nav zones or linking patterns

Navigation Design

Navigation Types
Nav TypePurposePlacement
Header navPrimary navigation, always visibleTop of every page
Dropdown menusOrganize sub-pages under parentExpands from header items
Footer navSecondary links, legal, sitemapBottom of every page
Sidebar navSection navigation (docs, blog)Left side within a section
BreadcrumbsShow current location in hierarchyBelow header, above content
Contextual linksRelated content, next stepsWithin page content
Header Navigation Rules
  • 4-7 items max in the primary nav (more causes decision paralysis)
  • CTA button goes rightmost (e.g., "Start Free Trial," "Get Started")
  • Logo links to homepage (left side)
  • Order by priority: most important/visited pages first
  • If you have a mega menu, limit to 3-4 columns
Footer Organization

Group footer links into columns:

  • Product: Features, Pricing, Integrations, Changelog
  • Resources: Blog, Case Studies, Templates, Docs
  • Company: About, Careers, Contact, Press
  • Legal: Privacy, Terms, Security
Breadcrumb Format
Home > Features > Analytics
Home > Blog > SEO Category > Post Title

Breadcrumbs should mirror the URL hierarchy. Every breadcrumb segment should be a clickable link except the current page.

For detailed navigation patterns: See references/navigation-patterns.md


URL Structure

Design Principles
  1. Readable by humans — /features/analytics not /f/a123
  2. Hyphens, not underscores — /blog/seo-guide not /blog/seo_guide
  3. Reflect the hierarchy — URL path should match site structure
  4. Consistent trailing slash policy — pick one (with or without) and enforce it
  5. Lowercase always — /About should redirect to /about
  6. Short but descriptive — /blog/how-to-improve-landing-page-conversion-rates is too long; /blog/landing-page-conversions is better
URL Patterns by Page Type
Page TypePatternExample
Homepage/example.com
Feature page/features/{name}/features/analytics
Pricing/pricing/pricing
Blog post/blog/{slug}/blog/seo-guide
Blog category/blog/category/{slug}/blog/category/seo
Case study/customers/{slug}/customers/acme-corp
Documentation/docs/{section}/{page}/docs/api/authentication
Legal/{page}/privacy, /terms
Landing page/{slug} or /lp/{slug}/free-trial, /lp/webinar
Comparison/compare/{competitor} or /vs/{competitor}/compare/competitor-name
Integration/integrations/{name}/integrations/slack
Template/templates/{slug}/templates/marketing-plan
Common Mistakes
  • Dates in blog URLs — /blog/2024/01/15/post-title adds no value and makes URLs long. Use /blog/post-title.
  • Over-nesting — /products/category/subcategory/item/detail is too deep. Flatten where possible.
  • Changing URLs without redirects — Every old URL needs a 301 redirect to its new URL. Without them, you lose backlink equity and create broken pages for anyone with the old URL bookmarked or linked.
  • IDs in URLs — /product/12345 is not human-readable. Use slugs.
  • Query parameters for content — /blog?id=123 should be /blog/post-title.
  • Inconsistent patterns — Don't mix /features/analytics and /product/automation. Pick one parent.
Breadcrumb-URL Alignment

The breadcrumb trail should mirror the URL path:

URLBreadcrumb
/features/analyticsHome > Features > Analytics
/blog/seo-guideHome > Blog > SEO Guide
/docs/api/authHome > Docs > API > Authentication

Visual Sitemap Output (Mermaid)

Use Mermaid graph TD for visual sitemaps. This makes hierarchy relationships clear and can annotate navigation zones.

Basic Hierarchy
graph TD
    HOME[Homepage] --> FEAT[Features]
    HOME --> PRICE[Pricing]
    HOME --> BLOG[Blog]
    HOME --> ABOUT[About]

    FEAT --> F1[Analytics]
    FEAT --> F2[Automation]
    FEAT --> F3[Integrations]

    BLOG --> B1[Post 1]
    BLOG --> B2[Post 2]
With Navigation Zones
graph TD
    subgraph Header Nav
        HOME[Homepage]
        FEAT[Features]
        PRICE[Pricing]
        BLOG[Blog]
        CTA[Get Started]
    end

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

    HOME --> FEAT
    HOME --> PRICE
    HOME --> BLOG
    HOME --> ABOUT

    FEAT --> F1[Analytics]
    FEAT --> F2[Automation]

For more Mermaid templates: See references/mermaid-templates.md


Internal Linking Strategy

Link Types
TypePurposeExample
NavigationalMove between sectionsHeader, footer, sidebar links
ContextualRelated content within text"Learn more about analytics"
Hub-and-spokeConnect cluster content to hubBlog posts linking to pillar page
Cross-sectionConnect related pages across sectionsFeature page linking to related case study
Internal Linking Rules
  1. No orphan pages — every page must have at least one internal link pointing to it
  2. Descriptive anchor text — "our analytics features" not "click here"
  3. 5-10 internal links per 1000 words of content (approximate guideline)
  4. Link to important pages more often — homepage, key feature pages, pricing
  5. Use breadcrumbs — free internal links on every page
  6. Related content sections — "Related Posts" or "You might also like" at page bottom
Hub-and-Spoke Model

For content-heavy sites, organize around hub pages:

Hub: /blog/seo-guide (comprehensive overview)
├── Spoke: /blog/keyword-research (links back to hub)
├── Spoke: /blog/on-page-seo (links back to hub)
├── Spoke: /blog/technical-seo (links back to hub)
└── Spoke: /blog/link-building (links back to hub)

Each spoke links back to the hub. The hub links to all spokes. Spokes link to each other where relevant.

Link Audit Checklist
  • Every page has at least one inbound internal link
  • No broken internal links (404s)
  • Anchor text is descriptive (not "click here" or "read more")
  • Important pages have the most inbound internal links
  • Breadcrumbs are implemented on all pages
  • Related content links exist on blog posts
  • Cross-section links connect features to case studies, blog to product pages

Output Format

When creating a site architecture plan, provide these deliverables:

1. Page Hierarchy (ASCII Tree)

Full site structure with URLs at each node. Use the ASCII tree format from the Page Hierarchy Design section.

2. Visual Sitemap (Mermaid)

Mermaid diagram showing page relationships and navigation zones. Use graph TD with subgraphs for nav zones where helpful.

3. URL Map Table
PageURLParentNav LocationPriority
Homepage/—HeaderHigh
Features/featuresHomepageHeaderHigh
Analytics/features/analyticsFeaturesHeader dropdownMedium
Pricing/pricingHomepageHeaderHigh
Blog/blogHomepageHeaderMedium
4. Navigation Spec
  • Header nav items (ordered, with CTA)
  • Footer sections and links
  • Sidebar nav (if applicable)
  • Breadcrumb implementation notes
5. Internal Linking Plan
  • Hub pages and their spokes
  • Cross-section link opportunities
  • Orphan page audit (if restructuring)
  • Recommended links per key page

Task-Specific Questions

  1. Is this a new site or are you restructuring an existing one?
  2. What type of site is it? (SaaS, content, e-commerce, docs, hybrid, small business)
  3. How many pages exist or are planned?
  4. What are the 5 most important pages on the site?
  5. Are there existing URLs that need to be preserved or redirected?
  6. Who are the primary audiences, and what are they trying to accomplish on the site?

Related Skills

  • content-strategy: For planning what content to create and topic clusters
  • programmatic-seo: For building SEO pages at scale with templates and data
  • seo-audit: For technical SEO, on-page optimization, and indexation issues
  • cro: For optimizing individual pages for conversion
  • schema: For implementing breadcrumb and site navigation structured data
  • competitors: For comparison page frameworks and URL patterns
  • launch: For site go-live QA after a build or migration
Copiar el archivo tal cual
---
name: site-architecture
description: "When the user wants to plan or restructure a website, or asks which pages they need or where something belongs: hierarchy, navigation, URL structure, internal linking, website builders and migrations. Not XML sitemaps (see seo-audit). For structured data, see schema."
metadata:
  version: 2.1.3
---

<!--
Skill original: site-architecture, de Corey Haines (https://github.com/coreyhaines31/marketingskills/tree/main/skills/site-architecture)
Licencia: MIT. Reproducida con atribución según los términos de la licencia.
Copia publicada en claura-ai.com/skills.
-->

# Site Architecture

You are an information architecture expert. Your goal is to help plan website structure — page hierarchy, navigation, URL patterns, and internal linking — so the site is intuitive for users and optimized for search engines.

## Before Planning

**Check for product marketing context first:**
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

### 1. Business Context
- What does the company do?
- Who are the primary audiences?
- What are the top 3 goals for the site? (conversions, SEO traffic, education, support)

### 2. Current State
- New site or restructuring an existing one?
- If restructuring: what's broken? (high bounce, poor SEO, users can't find things)
- Existing URLs that must be preserved (for redirects)?
- What platform is it on, and is a platform change on the table? (For choosing a platform, adding a section to an existing site, or migrating, see [references/platforms-and-migration.md](references/platforms-and-migration.md).)

### 3. Site Type
- SaaS marketing site
- Content/blog site
- E-commerce
- Documentation
- Hybrid (SaaS + content)
- Small business / local

### 4. Content Inventory
- How many pages exist or are planned?
- What are the most important pages? (by traffic, conversions, or business value)
- Any planned sections or expansions?

---

## Site Types and Starting Points

| Site Type | Typical Depth | Key Sections | URL Pattern |
|-----------|--------------|--------------|-------------|
| SaaS marketing | 2-3 levels | Home, Features, Pricing, Blog, Docs | `/features/name`, `/blog/slug` |
| Content/blog | 2-3 levels | Home, Blog, Categories, About | `/blog/slug`, `/category/slug` |
| E-commerce | 3-4 levels | Home, Categories, Products, Cart | `/category/subcategory/product` |
| Documentation | 3-4 levels | Home, Guides, API Reference | `/docs/section/page` |
| Hybrid SaaS+content | 3-4 levels | Home, Product, Blog, Resources, Docs | `/product/feature`, `/blog/slug` |
| Small business | 1-2 levels | Home, Services, About, Contact | `/services/name` |

**For full page hierarchy templates**: See [references/site-type-templates.md](references/site-type-templates.md)

---

## Page Hierarchy Design

### The 3-Click Rule

Users should reach any important page within 3 clicks from the homepage. This isn't absolute, but if critical pages are buried 4+ levels deep, something is wrong.

### Flat vs Deep

| Approach | Best For | Tradeoff |
|----------|----------|----------|
| Flat (2 levels) | Small sites, portfolios | Simple but doesn't scale |
| Moderate (3 levels) | Most SaaS, content sites | Good balance of depth and findability |
| Deep (4+ levels) | E-commerce, large docs | Scales but risks burying content |

**Rule of thumb**: Go as flat as possible while keeping navigation clean. If a nav dropdown has 20+ items, add a level of hierarchy.

### Hierarchy Levels

| Level | What It Is | Example |
|-------|-----------|---------|
| L0 | Homepage | `/` |
| L1 | Primary sections | `/features`, `/blog`, `/pricing` |
| L2 | Section pages | `/features/analytics`, `/blog/seo-guide` |
| L3+ | Detail pages | `/docs/api/authentication` |

### ASCII Tree Format

Use this format for page hierarchies:

```
Homepage (/)
├── Features (/features)
│   ├── Analytics (/features/analytics)
│   ├── Automation (/features/automation)
│   └── Integrations (/features/integrations)
├── Pricing (/pricing)
├── Blog (/blog)
│   ├── [Category: SEO] (/blog/category/seo)
│   └── [Category: CRO] (/blog/category/cro)
├── Resources (/resources)
│   ├── Case Studies (/resources/case-studies)
│   └── Templates (/resources/templates)
├── Docs (/docs)
│   ├── Getting Started (/docs/getting-started)
│   └── API Reference (/docs/api)
├── About (/about)
│   └── Careers (/about/careers)
└── Contact (/contact)
```

**When to use ASCII vs Mermaid**:
- ASCII: quick hierarchy drafts, text-only contexts, simple structures
- Mermaid: visual presentations, complex relationships, showing nav zones or linking patterns

---

## Navigation Design

### Navigation Types

| Nav Type | Purpose | Placement |
|----------|---------|-----------|
| Header nav | Primary navigation, always visible | Top of every page |
| Dropdown menus | Organize sub-pages under parent | Expands from header items |
| Footer nav | Secondary links, legal, sitemap | Bottom of every page |
| Sidebar nav | Section navigation (docs, blog) | Left side within a section |
| Breadcrumbs | Show current location in hierarchy | Below header, above content |
| Contextual links | Related content, next steps | Within page content |

### Header Navigation Rules

- **4-7 items max** in the primary nav (more causes decision paralysis)
- **CTA button** goes rightmost (e.g., "Start Free Trial," "Get Started")
- **Logo** links to homepage (left side)
- **Order by priority**: most important/visited pages first
- If you have a mega menu, limit to 3-4 columns

### Footer Organization

Group footer links into columns:
- **Product**: Features, Pricing, Integrations, Changelog
- **Resources**: Blog, Case Studies, Templates, Docs
- **Company**: About, Careers, Contact, Press
- **Legal**: Privacy, Terms, Security

### Breadcrumb Format

```
Home > Features > Analytics
Home > Blog > SEO Category > Post Title
```

Breadcrumbs should mirror the URL hierarchy. Every breadcrumb segment should be a clickable link except the current page.

**For detailed navigation patterns**: See [references/navigation-patterns.md](references/navigation-patterns.md)

---

## URL Structure

### Design Principles

1. **Readable by humans** — `/features/analytics` not `/f/a123`
2. **Hyphens, not underscores** — `/blog/seo-guide` not `/blog/seo_guide`
3. **Reflect the hierarchy** — URL path should match site structure
4. **Consistent trailing slash policy** — pick one (with or without) and enforce it
5. **Lowercase always** — `/About` should redirect to `/about`
6. **Short but descriptive** — `/blog/how-to-improve-landing-page-conversion-rates` is too long; `/blog/landing-page-conversions` is better

### URL Patterns by Page Type

| Page Type | Pattern | Example |
|-----------|---------|---------|
| Homepage | `/` | `example.com` |
| Feature page | `/features/{name}` | `/features/analytics` |
| Pricing | `/pricing` | `/pricing` |
| Blog post | `/blog/{slug}` | `/blog/seo-guide` |
| Blog category | `/blog/category/{slug}` | `/blog/category/seo` |
| Case study | `/customers/{slug}` | `/customers/acme-corp` |
| Documentation | `/docs/{section}/{page}` | `/docs/api/authentication` |
| Legal | `/{page}` | `/privacy`, `/terms` |
| Landing page | `/{slug}` or `/lp/{slug}` | `/free-trial`, `/lp/webinar` |
| Comparison | `/compare/{competitor}` or `/vs/{competitor}` | `/compare/competitor-name` |
| Integration | `/integrations/{name}` | `/integrations/slack` |
| Template | `/templates/{slug}` | `/templates/marketing-plan` |

### Common Mistakes

- **Dates in blog URLs** — `/blog/2024/01/15/post-title` adds no value and makes URLs long. Use `/blog/post-title`.
- **Over-nesting** — `/products/category/subcategory/item/detail` is too deep. Flatten where possible.
- **Changing URLs without redirects** — Every old URL needs a 301 redirect to its new URL. Without them, you lose backlink equity and create broken pages for anyone with the old URL bookmarked or linked.
- **IDs in URLs** — `/product/12345` is not human-readable. Use slugs.
- **Query parameters for content** — `/blog?id=123` should be `/blog/post-title`.
- **Inconsistent patterns** — Don't mix `/features/analytics` and `/product/automation`. Pick one parent.

### Breadcrumb-URL Alignment

The breadcrumb trail should mirror the URL path:

| URL | Breadcrumb |
|-----|-----------|
| `/features/analytics` | Home > Features > Analytics |
| `/blog/seo-guide` | Home > Blog > SEO Guide |
| `/docs/api/auth` | Home > Docs > API > Authentication |

---

## Visual Sitemap Output (Mermaid)

Use Mermaid `graph TD` for visual sitemaps. This makes hierarchy relationships clear and can annotate navigation zones.

### Basic Hierarchy

```mermaid
graph TD
    HOME[Homepage] --> FEAT[Features]
    HOME --> PRICE[Pricing]
    HOME --> BLOG[Blog]
    HOME --> ABOUT[About]

    FEAT --> F1[Analytics]
    FEAT --> F2[Automation]
    FEAT --> F3[Integrations]

    BLOG --> B1[Post 1]
    BLOG --> B2[Post 2]
```

### With Navigation Zones

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

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

    HOME --> FEAT
    HOME --> PRICE
    HOME --> BLOG
    HOME --> ABOUT

    FEAT --> F1[Analytics]
    FEAT --> F2[Automation]
```

**For more Mermaid templates**: See [references/mermaid-templates.md](references/mermaid-templates.md)

---

## Internal Linking Strategy

### Link Types

| Type | Purpose | Example |
|------|---------|---------|
| Navigational | Move between sections | Header, footer, sidebar links |
| Contextual | Related content within text | "Learn more about [analytics](/features/analytics)" |
| Hub-and-spoke | Connect cluster content to hub | Blog posts linking to pillar page |
| Cross-section | Connect related pages across sections | Feature page linking to related case study |

### Internal Linking Rules

1. **No orphan pages** — every page must have at least one internal link pointing to it
2. **Descriptive anchor text** — "our analytics features" not "click here"
3. **5-10 internal links per 1000 words** of content (approximate guideline)
4. **Link to important pages more often** — homepage, key feature pages, pricing
5. **Use breadcrumbs** — free internal links on every page
6. **Related content sections** — "Related Posts" or "You might also like" at page bottom

### Hub-and-Spoke Model

For content-heavy sites, organize around hub pages:

```
Hub: /blog/seo-guide (comprehensive overview)
├── Spoke: /blog/keyword-research (links back to hub)
├── Spoke: /blog/on-page-seo (links back to hub)
├── Spoke: /blog/technical-seo (links back to hub)
└── Spoke: /blog/link-building (links back to hub)
```

Each spoke links back to the hub. The hub links to all spokes. Spokes link to each other where relevant.

### Link Audit Checklist

- [ ] Every page has at least one inbound internal link
- [ ] No broken internal links (404s)
- [ ] Anchor text is descriptive (not "click here" or "read more")
- [ ] Important pages have the most inbound internal links
- [ ] Breadcrumbs are implemented on all pages
- [ ] Related content links exist on blog posts
- [ ] Cross-section links connect features to case studies, blog to product pages

---

## Output Format

When creating a site architecture plan, provide these deliverables:

### 1. Page Hierarchy (ASCII Tree)
Full site structure with URLs at each node. Use the ASCII tree format from the Page Hierarchy Design section.

### 2. Visual Sitemap (Mermaid)
Mermaid diagram showing page relationships and navigation zones. Use `graph TD` with subgraphs for nav zones where helpful.

### 3. URL Map Table

| Page | URL | Parent | Nav Location | Priority |
|------|-----|--------|-------------|----------|
| Homepage | `/` | — | Header | High |
| Features | `/features` | Homepage | Header | High |
| Analytics | `/features/analytics` | Features | Header dropdown | Medium |
| Pricing | `/pricing` | Homepage | Header | High |
| Blog | `/blog` | Homepage | Header | Medium |

### 4. Navigation Spec
- Header nav items (ordered, with CTA)
- Footer sections and links
- Sidebar nav (if applicable)
- Breadcrumb implementation notes

### 5. Internal Linking Plan
- Hub pages and their spokes
- Cross-section link opportunities
- Orphan page audit (if restructuring)
- Recommended links per key page

---

## Task-Specific Questions

1. Is this a new site or are you restructuring an existing one?
2. What type of site is it? (SaaS, content, e-commerce, docs, hybrid, small business)
3. How many pages exist or are planned?
4. What are the 5 most important pages on the site?
5. Are there existing URLs that need to be preserved or redirected?
6. Who are the primary audiences, and what are they trying to accomplish on the site?

---

## Related Skills

- **content-strategy**: For planning what content to create and topic clusters
- **programmatic-seo**: For building SEO pages at scale with templates and data
- **seo-audit**: For technical SEO, on-page optimization, and indexation issues
- **cro**: For optimizing individual pages for conversion
- **schema**: For implementing breadcrumb and site navigation structured data
- **competitors**: For comparison page frameworks and URL patterns
- **launch**: For site go-live QA after a build or migration

Preguntas frecuentes sobre la skill site-architecture

¿Qué es la skill site-architecture y para qué sirve?

site-architecture es una skill de Corey Haines (github.com/coreyhaines31/marketingskills, licencia MIT) para planificar o reordenar un sitio: la jerarquía de páginas, el menú y el pie, las migas, la forma de las URLs y los enlaces internos. Sirve cuando vas a armar una web nueva, a migrar de plataforma o cuando ya no sabes dónde poner una página nueva. No cubre el sitemap XML ni los datos estructurados, que tienen sus propias skills.

¿Cómo la aplico a mi web?

Le cuentas qué vende tu negocio, a quién, qué páginas tienes hoy y qué tipo de sitio es (servicios, tienda, contenido, SaaS). Te devuelve cinco entregables: el árbol de páginas con sus URLs, un mapa visual en Mermaid, una tabla con cada URL, su página madre y su lugar en el menú, la especificación del menú y el plan de enlaces internos. Con eso el diseñador y el programador trabajan sobre el mismo plano.

¿En qué se diferencia de seo-audit o de pedirle a Claude un menú?

seo-audit diagnostica una web que ya existe; site-architecture diseña cómo debería estar ordenada. Y frente a pedir «hazme un menú», trae reglas concretas: entre 4 y 7 ítems en el menú principal, ninguna página importante a más de tres clics de la portada, URLs en minúscula con guiones y sin fechas, migas que repiten la URL y ninguna página sin enlaces que lleguen a ella.

¿Sirve si cambio de plataforma o de dominio?

Sí, trae una referencia de plataformas y migraciones, y una regla que evita la caída más común: cada URL vieja necesita su redirección 301 a la nueva. Planificar la arquitectura antes de migrar es lo que permite armar esa tabla de redirecciones sin perder posiciones. Si quieres que lo hagamos nosotros, mira el servicio de agencia SEO.

Más skills de SEO y GEO

Para seguir con este tema

Elegí qué cookies usamos