Design Intuitive Site Architecture

Site Architecture plans website structure - page hierarchy, navigation, URL patterns, and internal linking - so a site is intuitive for users and optimized for search engines.

Use this when planning or restructuring page hierarchy, navigation, and URL structure, mapping site sections, breadcrumbs, and internal linking, or when the question is how pages should be organized rather than how an XML sitemap should be generated. Before planning, it checks for an existing .agents/product-marketing-context.md (or the older .claude/ path) and only asks about what isn't already covered: business context (what the company does, primary audiences, top 3 site goals), current state (new site vs restructuring, what's broken, URLs that must be preserved for redirects), site type, and content inventory (page count, most important pages, planned expansions).

Six site types each get a typical depth, key sections, and URL pattern - SaaS marketing (2-3 levels), content/blog (2-3), e-commerce (3-4), documentation (3-4), hybrid SaaS+content (3-4), and small business (1-2). Hierarchy design follows the 3-click rule (important pages reachable within 3 clicks of the homepage) and a flat-vs-deep tradeoff (flat for small sites, moderate for most SaaS/content sites, deep for e-commerce and large docs - go as flat as possible while keeping nav dropdowns under roughly 20 items), expressed as L0 homepage through L3+ detail pages and rendered as an ASCII tree for quick drafts or a Mermaid graph TD diagram for visual presentations and nav-zone annotation. Navigation design covers six nav types (header, dropdown, footer, sidebar, breadcrumbs, contextual links), with header nav capped at 4-7 items, a CTA button rightmost, logo linking home, and mega menus limited to 3-4 columns; footer links grouped into Product/Resources/Company/Legal columns; and breadcrumbs that mirror the URL hierarchy with every segment but the current page clickable. URL structure follows six principles - human-readable, hyphens not underscores, matching the hierarchy, a consistent trailing-slash policy, always lowercase, short but descriptive - with patterns per page type such as /features/{name}, /blog/{slug}, /docs/{section}/{page}, and /compare/{competitor}, and named mistakes to avoid: dates in blog URLs, over-nesting, changing URLs without 301 redirects, numeric IDs instead of slugs, query parameters for content, and mixing inconsistent parent patterns.

Internal linking strategy names four link types (navigational, contextual, hub-and-spoke, cross-section) and six rules - no orphan pages, descriptive anchor text, roughly 5-10 internal links per 1000 words, more links to important pages, breadcrumbs as free internal links, and "related content" sections - organized around a hub-and-spoke model where spoke pages link back to a comprehensive hub and to each other where relevant. A full plan delivers five outputs: an ASCII-tree page hierarchy, a Mermaid visual sitemap, a URL map table (page, URL, parent, nav location, priority), a navigation spec, and an internal linking plan including an orphan-page audit when restructuring. It names six related skills: content-strategy for topic clusters, programmatic-seo for templated pages at scale, seo-audit for technical/on-page/indexation issues, page-cro for conversion optimization, schema-markup for breadcrumb/navigation structured data, and competitor-alternatives for comparison-page URL patterns.

Teams planning a new site or restructuring an existing one who need a concrete hierarchy, navigation spec, URL scheme, and internal-linking plan, not just high-level advice, tailored to their specific site type and content volume.