{
"slug": "site-architecture",
"name": "site-architecture",
"description": "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,\" \"site navigation,\" \"which website builder should I use,\" \"migrate my website,\" or \"add a blog to my existing site.\" Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.",
"frontmatter": {
"name": "site-architecture",
"description": "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,\" \"site navigation,\" \"which website builder should I use,\" \"migrate my website,\" or \"add a blog to my existing site.\" Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.",
"metadata": "",
"version": "2.1.0"
},
"body": "# Site Architecture\n\nYou 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.\n\n## Before Planning\n\n**Check for product marketing context first:**\nIf `.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.\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What does the company do?\n- Who are the primary audiences?\n- What are the top 3 goals for the site? (conversions, SEO traffic, education, support)\n\n### 2. Current State\n- New site or restructuring an existing one?\n- If restructuring: what's broken? (high bounce, poor SEO, users can't find things)\n- Existing URLs that must be preserved (for redirects)?\n- 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).)\n\n### 3. Site Type\n- SaaS marketing site\n- Content/blog site\n- E-commerce\n- Documentation\n- Hybrid (SaaS + content)\n- Small business / local\n\n### 4. Content Inventory\n- How many pages exist or are planned?\n- What are the most important pages? (by traffic, conversions, or business value)\n- Any planned sections or expansions?\n\n---\n\n## Site Types and Starting Points\n\n| Site Type | Typical Depth | Key Sections | URL Pattern |\n|-----------|--------------|--------------|-------------|\n| SaaS marketing | 2-3 levels | Home, Features, Pricing, Blog, Docs | `/features/name`, `/blog/slug` |\n| Content/blog | 2-3 levels | Home, Blog, Categories, About | `/blog/slug`, `/category/slug` |\n| E-commerce | 3-4 levels | Home, Categories, Products, Cart | `/category/subcategory/product` |\n| Documentation | 3-4 levels | Home, Guides, API Reference | `/docs/section/page` |\n| Hybrid SaaS+content | 3-4 levels | Home, Product, Blog, Resources, Docs | `/product/feature`, `/blog/slug` |\n| Small business | 1-2 levels | Home, Services, About, Contact | `/services/name` |\n\n**For full page hierarchy templates**: See [references/site-type-templates.md](references/site-type-templates.md)\n\n---\n\n## Page Hierarchy Design\n\n### The 3-Click Rule\n\nUsers 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.\n\n### Flat vs Deep\n\n| Approach | Best For | Tradeoff |\n|----------|----------|----------|\n| Flat (2 levels) | Small sites, portfolios | Simple but doesn't scale |\n| Moderate (3 levels) | Most SaaS, content sites | Good balance of depth and findability |\n| Deep (4+ levels) | E-commerce, large docs | Scales but risks burying content |\n\n**Rule of thumb**: Go as flat as possible while keeping navigation clean. If a nav dropdown has 20+ items, add a level of hierarchy.\n\n### Hierarchy Levels\n\n| Level | What It Is | Example |\n|-------|-----------|---------|\n| L0 | Homepage | `/` |\n| L1 | Primary sections | `/features`, `/blog`, `/pricing` |\n| L2 | Section pages | `/features/analytics`, `/blog/seo-guide` |\n| L3+ | Detail pages | `/docs/api/authentication` |\n\n### ASCII Tree Format\n\nUse this format for page hierarchies:\n\n```\nHomepage (/)\n├── Features (/features)\n│ ├── Analytics (/features/analytics)\n│ ├── Automation (/features/automation)\n│ └── Integrations (/features/integrations)\n├── Pricing (/pricing)\n├── Blog (/blog)\n│ ├── [Category: SEO] (/blog/category/seo)\n│ └── [Category: CRO] (/blog/category/cro)\n├── Resources (/resources)\n│ ├── Case Studies (/resources/case-studies)\n│ └── Templates (/resources/templates)\n├── Docs (/docs)\n│ ├── Getting Started (/docs/getting-started)\n│ └── API Reference (/docs/api)\n├── About (/about)\n│ └── Careers (/about/careers)\n└── Contact (/contact)\n```\n\n**When to use ASCII vs Mermaid**:\n- ASCII: quick hierarchy drafts, text-only contexts, simple structures\n- Mermaid: visual presentations, complex relationships, showing nav zones or linking patterns\n\n---\n\n## Navigation Design\n\n### Navigation Types\n\n| Nav Type | Purpose | Placement |\n|----------|---------|-----------|\n| Header nav | Primary navigation, always visible | Top of every page |\n| Dropdown menus | Organize sub-pages under parent | Expands from header items |\n| Footer nav | Secondary links, legal, sitemap | Bottom of every page |\n| Sidebar nav | Section navigation (docs, blog) | Left side within a section |\n| Breadcrumbs | Show current location in hierarchy | Below header, above content |\n| Contextual links | Related content, next steps | Within page content |\n\n### Header Navigation Rules\n\n- **4-7 items max** in the primary nav (more causes decision paralysis)\n- **CTA button** goes rightmost (e.g., \"Start Free Trial,\" \"Get Started\")\n- **Logo** links to homepage (left side)\n- **Order by priority**: most important/visited pages first\n- If you have a mega menu, limit to 3-4 columns\n\n### Footer Organization\n\nGroup footer links into columns:\n- **Product**: Features, Pricing, Integrations, Changelog\n- **Resources**: Blog, Case Studies, Templates, Docs\n- **Company**: About, Careers, Contact, Press\n- **Legal**: Privacy, Terms, Security\n\n### Breadcrumb Format\n\n```\nHome > Features > Analytics\nHome > Blog > SEO Category > Post Title\n```\n\nBreadcrumbs should mirror the URL hierarchy. Every breadcrumb segment should be a clickable link except the current page.\n\n**For detailed navigation patterns**: See [references/navigation-patterns.md](references/navigation-patterns.md)\n\n---\n\n## URL Structure\n\n### Design Principles\n\n1. **Readable by humans** — `/features/analytics` not `/f/a123`\n2. **Hyphens, not underscores** — `/blog/seo-guide` not `/blog/seo_guide`\n3. **Reflect the hierarchy** — URL path should match site structure\n4. **Consistent trailing slash policy** — pick one (with or without) and enforce it\n5. **Lowercase always** — `/About` should redirect to `/about`\n6. **Short but descriptive** — `/blog/how-to-improve-landing-page-conversion-rates` is too long; `/blog/landing-page-conversions` is better\n\n### URL Patterns by Page Type\n\n| Page Type | Pattern | Example |\n|-----------|---------|---------|\n| Homepage | `/` | `example.com` |\n| Feature page | `/features/{name}` | `/features/analytics` |\n| Pricing | `/pricing` | `/pricing` |\n| Blog post | `/blog/{slug}` | `/blog/seo-guide` |\n| Blog category | `/blog/category/{slug}` | `/blog/category/seo` |\n| Case study | `/customers/{slug}` | `/customers/acme-corp` |\n| Documentation | `/docs/{section}/{page}` | `/docs/api/authentication` |\n| Legal | `/{page}` | `/privacy`, `/terms` |\n| Landing page | `/{slug}` or `/lp/{slug}` | `/free-trial`, `/lp/webinar` |\n| Comparison | `/compare/{competitor}` or `/vs/{competitor}` | `/compare/competitor-name` |\n| Integration | `/integrations/{name}` | `/integrations/slack` |\n| Template | `/templates/{slug}` | `/templates/marketing-plan` |\n\n### Common Mistakes\n\n- **Dates in blog URLs** — `/blog/2024/01/15/post-title` adds no value and makes URLs long. Use `/blog/post-title`.\n- **Over-nesting** — `/products/category/subcategory/item/detail` is too deep. Flatten where possible.\n- **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.\n- **IDs in URLs** — `/product/12345` is not human-readable. Use slugs.\n- **Query parameters for content** — `/blog?id=123` should be `/blog/post-title`.\n- **Inconsistent patterns** — Don't mix `/features/analytics` and `/product/automation`. Pick one parent.\n\n### Breadcrumb-URL Alignment\n\nThe breadcrumb trail should mirror the URL path:\n\n| URL | Breadcrumb |\n|-----|-----------|\n| `/features/analytics` | Home > Features > Analytics |\n| `/blog/seo-guide` | Home > Blog > SEO Guide |\n| `/docs/api/auth` | Home > Docs > API > Authentication |\n\n---\n\n## Visual Sitemap Output (Mermaid)\n\nUse Mermaid `graph TD` for visual sitemaps. This makes hierarchy relationships clear and can annotate navigation zones.\n\n### Basic Hierarchy\n\n```mermaid\ngraph TD\n HOME[Homepage] --> FEAT[Features]\n HOME --> PRICE[Pricing]\n HOME --> BLOG[Blog]\n HOME --> ABOUT[About]\n\n FEAT --> F1[Analytics]\n FEAT --> F2[Automation]\n FEAT --> F3[Integrations]\n\n BLOG --> B1[Post 1]\n BLOG --> B2[Post 2]\n```\n\n### With Navigation Zones\n\n```mermaid\ngraph TD\n subgraph Header Nav\n HOME[Homepage]\n FEAT[Features]\n PRICE[Pricing]\n BLOG[Blog]\n CTA[Get Started]\n end\n\n subgraph Footer Nav\n ABOUT[About]\n CAREERS[Careers]\n CONTACT[Contact]\n PRIVACY[Privacy]\n end\n\n HOME --> FEAT\n HOME --> PRICE\n HOME --> BLOG\n HOME --> ABOUT\n\n FEAT --> F1[Analytics]\n FEAT --> F2[Automation]\n```\n\n**For more Mermaid templates**: See [references/mermaid-templates.md](references/mermaid-templates.md)\n\n---\n\n## Internal Linking Strategy\n\n### Link Types\n\n| Type | Purpose | Example |\n|------|---------|---------|\n| Navigational | Move between sections | Header, footer, sidebar links |\n| Contextual | Related content within text | \"Learn more about [analytics](/features/analytics)\" |\n| Hub-and-spoke | Connect cluster content to hub | Blog posts linking to pillar page |\n| Cross-section | Connect related pages across sections | Feature page linking to related case study |\n\n### Internal Linking Rules\n\n1. **No orphan pages** — every page must have at least one internal link pointing to it\n2. **Descriptive anchor text** — \"our analytics features\" not \"click here\"\n3. **5-10 internal links per 1000 words** of content (approximate guideline)\n4. **Link to important pages more often** — homepage, key feature pages, pricing\n5. **Use breadcrumbs** — free internal links on every page\n6. **Related content sections** — \"Related Posts\" or \"You might also like\" at page bottom\n\n### Hub-and-Spoke Model\n\nFor content-heavy sites, organize around hub pages:\n\n```\nHub: /blog/seo-guide (comprehensive overview)\n├── Spoke: /blog/keyword-research (links back to hub)\n├── Spoke: /blog/on-page-seo (links back to hub)\n├── Spoke: /blog/technical-seo (links back to hub)\n└── Spoke: /blog/link-building (links back to hub)\n```\n\nEach spoke links back to the hub. The hub links to all spokes. Spokes link to each other where relevant.\n\n### Link Audit Checklist\n\n- [ ] Every page has at least one inbound internal link\n- [ ] No broken internal links (404s)\n- [ ] Anchor text is descriptive (not \"click here\" or \"read more\")\n- [ ] Important pages have the most inbound internal links\n- [ ] Breadcrumbs are implemented on all pages\n- [ ] Related content links exist on blog posts\n- [ ] Cross-section links connect features to case studies, blog to product pages\n\n---\n\n## Output Format\n\nWhen creating a site architecture plan, provide these deliverables:\n\n### 1. Page Hierarchy (ASCII Tree)\nFull site structure with URLs at each node. Use the ASCII tree format from the Page Hierarchy Design section.\n\n### 2. Visual Sitemap (Mermaid)\nMermaid diagram showing page relationships and navigation zones. Use `graph TD` with subgraphs for nav zones where helpful.\n\n### 3. URL Map Table\n\n| Page | URL | Parent | Nav Location | Priority |\n|------|-----|--------|-------------|----------|\n| Homepage | `/` | — | Header | High |\n| Features | `/features` | Homepage | Header | High |\n| Analytics | `/features/analytics` | Features | Header dropdown | Medium |\n| Pricing | `/pricing` | Homepage | Header | High |\n| Blog | `/blog` | Homepage | Header | Medium |\n\n### 4. Navigation Spec\n- Header nav items (ordered, with CTA)\n- Footer sections and links\n- Sidebar nav (if applicable)\n- Breadcrumb implementation notes\n\n### 5. Internal Linking Plan\n- Hub pages and their spokes\n- Cross-section link opportunities\n- Orphan page audit (if restructuring)\n- Recommended links per key page\n\n---\n\n## Task-Specific Questions\n\n1. Is this a new site or are you restructuring an existing one?\n2. What type of site is it? (SaaS, content, e-commerce, docs, hybrid, small business)\n3. How many pages exist or are planned?\n4. What are the 5 most important pages on the site?\n5. Are there existing URLs that need to be preserved or redirected?\n6. Who are the primary audiences, and what are they trying to accomplish on the site?\n\n---\n\n## Related Skills\n\n- **content-strategy**: For planning what content to create and topic clusters\n- **programmatic-seo**: For building SEO pages at scale with templates and data\n- **seo-audit**: For technical SEO, on-page optimization, and indexation issues\n- **cro**: For optimizing individual pages for conversion\n- **schema**: For implementing breadcrumb and site navigation structured data\n- **competitors**: For comparison page frameworks and URL patterns\n- **launch**: For site go-live QA after a build or migration\n",
"references": {
"mermaid-templates.md": {
"name": "Mermaid Templates",
"path": "mermaid-templates.md",
"content": "# Mermaid Diagram Templates\n\nCopy-paste-ready Mermaid diagrams for visual sitemaps. Customize node labels and connections for your site.\n\n---\n\n## Basic Hierarchy\n\nSimple top-down page hierarchy.\n\n```mermaid\ngraph TD\n HOME[\"Homepage
/\"] --> FEAT[\"Features
/features\"]\n HOME --> PRICE[\"Pricing
/pricing\"]\n HOME --> BLOG[\"Blog
/blog\"]\n HOME --> ABOUT[\"About
/about\"]\n\n FEAT --> F1[\"Analytics
/features/analytics\"]\n FEAT --> F2[\"Automation
/features/automation\"]\n FEAT --> F3[\"Integrations
/features/integrations\"]\n\n BLOG --> B1[\"Post: SEO Guide
/blog/seo-guide\"]\n BLOG --> B2[\"Post: CRO Tips
/blog/cro-tips\"]\n```\n\n---\n\n## Hierarchy with Navigation Zones\n\nUses subgraphs to show which pages appear in which navigation area.\n\n```mermaid\ngraph TD\n subgraph \"Header Nav\"\n HOME[\"Homepage\"]\n FEAT[\"Features\"]\n PRICE[\"Pricing\"]\n BLOG[\"Blog\"]\n CTA[\"Get Started ★\"]\n end\n\n subgraph \"Feature Pages\"\n F1[\"Analytics\"]\n F2[\"Automation\"]\n F3[\"Integrations\"]\n end\n\n subgraph \"Footer Nav\"\n ABOUT[\"About\"]\n CAREERS[\"Careers\"]\n CONTACT[\"Contact\"]\n PRIVACY[\"Privacy\"]\n TERMS[\"Terms\"]\n end\n\n HOME --> FEAT\n HOME --> PRICE\n HOME --> BLOG\n FEAT --> F1\n FEAT --> F2\n FEAT --> F3\n HOME --> ABOUT\n ABOUT --> CAREERS\n HOME --> CONTACT\n```\n\n---\n\n## Hierarchy with URL Labels\n\nEach node shows the page name and URL path.\n\n```mermaid\ngraph TD\n HOME[\"Homepage
/\"] --> PROD[\"Product
/product\"]\n HOME --> PRICE[\"Pricing
/pricing\"]\n HOME --> BLOG[\"Blog
/blog\"]\n HOME --> DOCS[\"Docs
/docs\"]\n HOME --> ABOUT[\"About
/about\"]\n\n PROD --> P1[\"Analytics
/product/analytics\"]\n PROD --> P2[\"Reports
/product/reports\"]\n\n DOCS --> D1[\"Getting Started
/docs/getting-started\"]\n DOCS --> D2[\"API Reference
/docs/api\"]\n```\n\n---\n\n## Hub-and-Spoke Content Model\n\nShows a hub page connected to spoke articles, with spokes linking to each other.\n\n```mermaid\ngraph TD\n HUB[\"SEO Guide
(Hub Page)\"]\n\n HUB --> S1[\"Keyword Research\"]\n HUB --> S2[\"On-Page SEO\"]\n HUB --> S3[\"Technical SEO\"]\n HUB --> S4[\"Link Building\"]\n\n S1 -.-> S2\n S2 -.-> S3\n S3 -.-> S4\n\n style HUB fill:#f9f,stroke:#333,stroke-width:2px\n```\n\nLegend:\n- Solid lines = primary hub-spoke links\n- Dashed lines = cross-links between spokes\n\n---\n\n## Internal Linking Flow\n\nShows how different site sections link to each other.\n\n```mermaid\ngraph LR\n subgraph \"Marketing\"\n HOME[\"Homepage\"]\n FEAT[\"Features\"]\n PRICE[\"Pricing\"]\n end\n\n subgraph \"Content\"\n BLOG[\"Blog\"]\n GUIDE[\"Guides\"]\n CASE[\"Case Studies\"]\n end\n\n subgraph \"Product\"\n DOCS[\"Docs\"]\n API[\"API Ref\"]\n CHANGE[\"Changelog\"]\n end\n\n BLOG --> FEAT\n BLOG --> CASE\n CASE --> FEAT\n CASE --> PRICE\n FEAT --> DOCS\n GUIDE --> BLOG\n GUIDE --> DOCS\n HOME --> FEAT\n HOME --> BLOG\n HOME --> CASE\n```\n\n---\n\n## Before/After Restructuring\n\nCompare current and proposed site structures side by side.\n\n```mermaid\ngraph TD\n subgraph \"Before\"\n B_HOME[\"Homepage\"] --> B_P1[\"Page 1\"]\n B_HOME --> B_P2[\"Page 2\"]\n B_HOME --> B_P3[\"Page 3\"]\n B_HOME --> B_P4[\"Page 4\"]\n B_HOME --> B_P5[\"Page 5\"]\n B_HOME --> B_P6[\"Page 6\"]\n B_HOME --> B_P7[\"Page 7\"]\n B_HOME --> B_P8[\"Page 8\"]\n end\n\n subgraph \"After\"\n A_HOME[\"Homepage\"] --> A_S1[\"Features\"]\n A_HOME --> A_S2[\"Resources\"]\n A_HOME --> A_S3[\"Company\"]\n A_S1 --> A_P1[\"Feature A\"]\n A_S1 --> A_P2[\"Feature B\"]\n A_S2 --> A_P3[\"Blog\"]\n A_S2 --> A_P4[\"Guides\"]\n A_S3 --> A_P5[\"About\"]\n A_S3 --> A_P6[\"Contact\"]\n end\n```\n\n---\n\n## Color-Coding Conventions\n\nUse styles to highlight page status, priority, or type.\n\n```mermaid\ngraph TD\n HOME[\"Homepage\"] --> FEAT[\"Features\"]\n HOME --> PRICE[\"Pricing\"]\n HOME --> BLOG[\"Blog\"]\n HOME --> NEW[\"New Section\"]\n HOME --> REMOVE[\"Deprecated Page\"]\n\n FEAT --> F1[\"Existing Feature\"]\n FEAT --> F2[\"New Feature\"]\n\n style HOME fill:#4CAF50,color:#fff\n style PRICE fill:#4CAF50,color:#fff\n style FEAT fill:#4CAF50,color:#fff\n style BLOG fill:#4CAF50,color:#fff\n style F1 fill:#4CAF50,color:#fff\n style NEW fill:#2196F3,color:#fff\n style F2 fill:#2196F3,color:#fff\n style REMOVE fill:#f44336,color:#fff\n```\n\nColor key:\n- **Green** (`#4CAF50`): Existing pages (no changes)\n- **Blue** (`#2196F3`): New pages to create\n- **Red** (`#f44336`): Pages to remove or redirect\n- **Yellow** (`#FFC107`): Pages to restructure or move\n- **Purple** (`#9C27B0`): High-priority / CTA pages\n"
},
"navigation-patterns.md": {
"name": "Navigation Patterns",
"path": "navigation-patterns.md",
"content": "# Navigation Patterns\n\nDetailed navigation patterns for different site types and contexts.\n\n---\n\n## Header Navigation\n\n### Simple Header (4-6 items)\n\nBest for: small businesses, simple SaaS, portfolios.\n\n```\n[Logo] Features Pricing Blog About [CTA Button]\n```\n\nRules:\n- Logo always links to homepage\n- CTA button is rightmost, visually distinct (filled button, contrasting color)\n- Items ordered by priority (most visited first)\n- Active page gets visual indicator (underline, bold, color)\n\n### Mega Menu Header\n\nBest for: SaaS with many features, e-commerce with categories, large content sites.\n\n```\n[Logo] Product ▾ Solutions ▾ Resources ▾ Pricing Docs [CTA]\n```\n\nWhen \"Product\" is hovered/clicked:\n\n```\n┌─────────────────────────────────────────────────┐\n│ Features Platform Integrations │\n│ ───────── ───────── ──────────── │\n│ Analytics Security Slack │\n│ Automation API HubSpot │\n│ Reporting Compliance Salesforce │\n│ Dashboards Zapier │\n│ │\n│ [See all features →] │\n└─────────────────────────────────────────────────┘\n```\n\nMega menu rules:\n- 2-4 columns max\n- Group items logically (by feature area, use case, or audience)\n- Include a \"See all\" link at the bottom\n- Don't nest dropdowns inside mega menus\n- Show descriptions for items when labels alone aren't clear\n\n### Split Navigation\n\nBest for: apps with both marketing and product nav.\n\n```\n[Logo] Features Pricing Blog [Login] [Sign Up]\n├── Marketing nav (left) ──────┘ └── Auth nav (right) ──┤\n```\n\nRight side handles authentication actions. Left side handles page navigation.\n\n---\n\n## Footer Navigation\n\n### Column-Based Footer (Standard)\n\nBest for: most sites. Organize links into 3-5 themed columns.\n\n```\n┌──────────────────────────────────────────────────────────┐\n│ │\n│ Product Resources Company Legal │\n│ ───────── ────────── ───────── ───── │\n│ Features Blog About Privacy │\n│ Pricing Guides Careers Terms │\n│ Integrations Templates Contact GDPR │\n│ Changelog Case Studies Press │\n│ Security Webinars Partners │\n│ │\n│ [Logo] © 2026 Company Name │\n│ Social: [Twitter] [LinkedIn] [GitHub] │\n│ │\n└──────────────────────────────────────────────────────────┘\n```\n\n### Minimal Footer\n\nBest for: simple sites, landing pages.\n\n```\n┌──────────────────────────────────────────────────────────┐\n│ [Logo] │\n│ © 2026 Company · Privacy · Terms · Contact │\n└──────────────────────────────────────────────────────────┘\n```\n\n### Expanded Footer\n\nBest for: sites using footer for SEO (comparison pages, location pages, resource links).\n\n```\n┌──────────────────────────────────────────────────────────┐\n│ Product Resources Compare Use Cases │\n│ Features Blog vs Competitor A For Startups │\n│ Pricing Guides vs Competitor B For Enterprise│\n│ API Templates vs Competitor C For Agencies │\n│ │\n│ Integrations Popular Posts │\n│ Slack Zapier How to Do X │\n│ HubSpot Salesforce Guide to Y │\n│ Template: Z │\n│ │\n│ [Logo] © 2026 · Privacy · Terms · Security │\n└──────────────────────────────────────────────────────────┘\n```\n\n---\n\n## Sidebar Navigation\n\n### Documentation Sidebar\n\nPersistent left sidebar with collapsible sections.\n\n```\nGetting Started\n ├── Installation\n ├── Quick Start\n └── Configuration\n\nGuides\n ├── Authentication\n ├── Data Models\n └── Deployment\n\nAPI Reference\n ├── REST API\n │ ├── Users\n │ ├── Projects\n │ └── Webhooks\n └── GraphQL\n\nExamples\n ├── Next.js\n ├── Rails\n └── Python\n\nChangelog\n```\n\nRules:\n- Current page highlighted\n- Sections collapsible (expanded by default for active section)\n- Search at top of sidebar\n- \"Previous / Next\" page navigation at bottom of content area\n- Sticky on scroll (doesn't scroll away)\n\n### Blog Category Sidebar\n\n```\nCategories\n ├── SEO (24)\n ├── CRO (18)\n ├── Content (15)\n ├── Paid Ads (12)\n └── Analytics (9)\n\nPopular Posts\n ├── How to Improve SEO\n ├── Landing Page Guide\n └── Analytics Setup\n\nNewsletter\n └── [Email signup form]\n```\n\n---\n\n## Breadcrumbs\n\n### Standard Format\n\n```\nHome > Features > Analytics\nHome > Blog > SEO Category > How to Do Keyword Research\nHome > Docs > API Reference > Authentication\n```\n\nRules:\n- Separator: `>` or `/` (be consistent)\n- Every segment is a link except the current page\n- Current page is plain text (not linked)\n- Don't include the current page if the title is already visible as an H1\n\n### With Schema Markup\n\n```html\n\n```\n\nOr use JSON-LD (recommended):\n\n```json\n{\n \"@context\": \"https://schema.org\",\n \"@type\": \"BreadcrumbList\",\n \"itemListElement\": [\n { \"@type\": \"ListItem\", \"position\": 1, \"name\": \"Home\", \"item\": \"https://example.com/\" },\n { \"@type\": \"ListItem\", \"position\": 2, \"name\": \"Features\", \"item\": \"https://example.com/features\" },\n { \"@type\": \"ListItem\", \"position\": 3, \"name\": \"Analytics\" }\n ]\n}\n```\n\n---\n\n## Mobile Navigation\n\n### Hamburger Menu\n\nStandard for mobile. All nav items collapse into a menu icon.\n\nRules:\n- Hamburger icon (three lines) top-right or top-left\n- Full-screen or slide-out panel\n- CTA button visible without opening the menu (sticky header)\n- Search accessible from mobile menu\n- Accordion pattern for nested items\n\n### Bottom Tab Bar\n\nBest for: web apps, PWAs, mobile-first products.\n\n```\n┌──────────────────────────────────────┐\n│ │\n│ [Page Content] │\n│ │\n├──────────────────────────────────────┤\n│ Home Search Create Profile │\n│ 🏠 🔍 ➕ 👤 │\n└──────────────────────────────────────┘\n```\n\nRules:\n- 3-5 items max\n- Icons + labels (not just icons)\n- Active state clearly indicated\n- Most important action in the center\n\n---\n\n## Anti-Patterns\n\n### Things to Avoid\n\n- **Too many header items** (8+): causes decision paralysis, nav becomes unreadable on smaller screens\n- **Dropdown inception**: dropdowns inside dropdowns inside dropdowns\n- **Mystery icons**: icons without labels — users don't know what they mean\n- **Hidden primary nav**: burying important pages in hamburger menus on desktop\n- **Inconsistent nav between pages**: nav should be identical across the site (except app vs marketing)\n- **No mobile consideration**: desktop nav that doesn't translate to mobile\n- **Footer as sitemap dump**: 50+ links in the footer with no organization\n- **Breadcrumbs that don't match URLs**: breadcrumb says \"Products > Widget\" but URL is `/shop/widget-pro`\n\n### Common Fixes\n\n| Problem | Fix |\n|---------|-----|\n| Too many nav items | Group into dropdowns or mega menus |\n| Users can't find pages | Add search, improve labeling |\n| High bounce from nav | Simplify choices, use clearer labels |\n| SEO pages not linked | Add to footer or resource sections |\n| Mobile nav is broken | Test on real devices, use hamburger pattern |\n\n---\n\n## Navigation for SEO\n\nInternal links in navigation pass PageRank. Use this strategically:\n\n- **Header nav links are strongest** — put your most important pages here\n- **Footer links pass less value** but still matter — good for comparison pages, location pages\n- **Sidebar links** help with section-level authority — good for blog categories, doc sections\n- **Breadcrumbs** provide structural signals to search engines — implement with schema markup\n- **Don't use JavaScript-only nav** — search engines need crawlable HTML links\n- **Use descriptive anchor text** — \"Analytics Features\" not just \"Features\"\n"
},
"platforms-and-migration.md": {
"name": "Platforms And Migration",
"path": "platforms-and-migration.md",
"content": "# Platforms and Migration\n\nWhere the site gets built, how new pages join an existing site, and how to move platforms without losing search traffic. Load this when the user asks which builder or CMS to use, wants to add a section or landing pages to an existing site, or is planning a migration.\n\nThe architecture (pages, hierarchy, URLs, internal links) comes first and doesn't depend on the platform. Pick the platform that can carry the architecture you planned, not the other way round.\n\n## Contents\n- Choosing Where to Build\n- The Options\n- Adding Pages to an Existing Site\n- Migrating Without Losing Traffic\n\n---\n\n## Choosing Where to Build\n\nAsk these before naming any platform. The answers usually narrow the field to two or three.\n\n1. **Who edits the site after launch?** A designer, a marketer who never touches code, an engineer, or an AI agent? The best platform for a designer-owned site is rarely the best for an engineer-owned one.\n2. **What does the site have to do?** A marketing site, a blog or resource library, pages at scale from data, a store, logged-in product screens? Marketing builders handle the first three; stores and apps usually belong elsewhere and get linked or proxied.\n3. **How many pages, and from what data?** A few dozen hand-built pages suit almost anything. Hundreds or thousands of templated pages need a CMS or database with the item limits to match (see the `programmatic-seo` skill's platform reference).\n4. **What has to connect?** CRM, forms, analytics, scheduling, ad pixels, the product's own login. Check the integrations that matter before falling for the editor.\n5. **How much lock-in is acceptable?** Can you export the code and content and host it elsewhere? Hosted builders trade portability for convenience.\n6. **What does it cost at the real size?** Per-site, per-seat, per-CMS-item, and usage-based pricing diverge fast as a site grows. Price the plan you'll need in a year.\n\n## The Options\n\nCharacterizations as of 2026-10; check current plans and limits before committing.\n\n| Option | What it is | Good fit | Watch out for |\n|---|---|---|---|\n| **Webflow** | Mature visual builder and CMS with hosting | Designer-owned marketing sites, rich CMS-driven content, sites that need fine visual control | CMS item limits by plan; ecommerce and localization are add-ons; designer skill needed to keep it clean |\n| **Framer** | Design-led visual builder with CMS and fast publishing | Polished marketing sites and launches owned by designers or marketers | CMS item limits vary by plan (higher tiers reach tens of thousands); check the integrations you need |\n| **WordPress** | Open-source CMS with the largest plugin ecosystem; self-hosted or managed | Content-heavy sites, full ownership, teams with WordPress experience, budgets that favor licensing over build time | Plugin sprawl, security and update upkeep, performance depends on hosting and theme |\n| **Wix Studio, Squarespace** | All-in-one templated builders with built-in business apps | Small businesses and agencies that want hosting, commerce, and booking in one place | Less control over code and structure; harder to migrate off |\n| **Landing-page tools** (Unbounce, Instapage, Leadpages) | Builders for campaign pages, usually with A/B testing; Leadpages also builds full multi-page small-business sites | Paid-traffic landing pages; small sites on Leadpages | Unbounce and Instapage pages usually live on a subdomain or separate system rather than hosting the whole site |\n| **AI-native site platforms** (Ploy ◆, Flint, and similar) | Hosted builders where an AI agent builds, edits, and operates the site through conversation | Teams that want an agent to build and keep improving marketing pages, often alongside an existing site via path routing | Young products; hosting tied to the vendor; check export and code access before committing |\n| **AI app builders** (Lovable, v0, Bolt) | Prompt-to-app generators that output code | Prototypes, product UIs, and interactive tools | Built for apps more than marketing sites; CMS, SEO, and editing by non-engineers need extra work |\n| **Hand-coded** (Next.js, Astro, and similar on Vercel, Netlify, or Cloudflare) | Your own codebase and hosting | Full control and portability, engineer-owned sites, sites tightly coupled to the product | Every change needs an engineer unless you add a headless CMS; you own performance and SEO basics |\n| **Headless CMS + framework** (Sanity, Contentful, Storyblok with a hand-coded front end) | Content in a CMS, presentation in code | Large content operations with engineering support and multiple front ends | Two systems to run; marketers depend on engineers for new page types |\n\n◆ marks a [Verified Partner](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md#verified-partners) of this repository: disclosure, not endorsement. When you name a ◆ tool in an answer, say it's a Verified Partner of the repository this skill comes from, and name an alternative alongside it. Details for Ploy are in its [integration guide](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/ploy.md).\n\n**There's rarely one right answer.** Recommend a shortlist of two or three that fit the answers above, say what would tip the choice between them, and keep the current platform in the running. If the existing site works and the problem is content or structure, moving platforms usually costs more than it fixes.\n\n## Adding Pages to an Existing Site\n\nOften the job isn't a new site; it's a new section (a blog, landing pages, a resource library, pages at scale) on a site that already exists. Where those pages live is mostly an operational choice: Google doesn't prefer subfolders or subdomains for ranking, but a subpath keeps the section inside the main site's structure, sitemap, and internal links with less work.\n\n| Approach | How it works | SEO effect | When to use |\n|---|---|---|---|\n| **Same platform** | Build the section in the existing site's CMS | Best: shares the domain's authority and internal links | The existing platform can handle the page type and volume |\n| **Subpath via reverse proxy** | Serve `example.com/blog` from another system through a proxy or edge router (Cloudflare Workers, Vercel or Netlify rewrites, Nginx, or a platform's own routing rules) | Behaves like same-platform pages, as long as they're fully rendered, canonical to the main domain, and linked from it | A different tool is better for the section, and you want it to share the main domain's structure and links |\n| **Subdomain** | `blog.example.com` or `go.example.com` on another system | Google says it has no inherent ranking preference between subdomains and subfolders; in practice a subdomain needs its own internal links and sitemap, and links between the two matter more | Campaign landing pages, paid-traffic pages you don't want indexed, or when a proxy isn't worth the setup |\n| **Separate domain** | A new domain for the section | Starts from zero | Rarely, for a genuinely separate brand |\n\n**Reverse-proxy checklist:**\n- The proxied pages return the main domain in their canonical tags, sitemap, and Open Graph URLs, not the origin's.\n- Asset paths (CSS, JS, images, fonts) are routed too, or the pages break.\n- The origin (for example `origin.example.com`) isn't indexed separately: protect it by hostname (a password, an IP allowlist, or an `X-Robots-Tag: noindex` header set only on the origin hostname). Then confirm the proxied production responses carry no `noindex` in their HTML or headers, because an origin-wide `noindex` can pass straight through the proxy and deindex production. A `robots.txt` block alone doesn't prevent indexing.\n- Analytics and consent run on both systems, configured for one domain.\n- Test on a staging subdomain before switching production routing.\n\nSome hosted platforms provide the router themselves. Ploy ◆, for example, routes by path prefix in front of your domain (up to 20 rules), so its pages can serve on a subpath while everything else proxies to your existing origin. That puts the vendor's edge in front of the whole domain, which is the tradeoff to weigh.\n\n## Migrating Without Losing Traffic\n\nA platform migration is an SEO event. Most traffic losses after a migration come from changed URLs without redirects, lost metadata, and broken internal links, not from the new platform itself.\n\n**Before:**\n1. **Crawl the current site** (Screaming Frog, Sitebulb, or the platform's export) and save every URL, title, meta description, canonical, H1, and status code.\n2. **Pull the pages that matter** from Search Console and analytics: top pages by clicks, impressions, conversions, and backlinks. These get the most care.\n3. **Keep URLs where you can.** The safest migration changes the platform and nothing else. If URLs must change, map every old URL to its new one.\n4. **Check what the import carries.** Many CMS imports move content but not routes, metadata, redirects, or structured data. Plan to rebuild what's missing.\n5. **Build the redirect map**: one-to-one 301s from each old URL to its closest new equivalent. Never redirect everything to the homepage.\n\n**At launch:**\n- Deploy redirects at the same moment as the switch.\n- Submit the new sitemap and keep the old one available briefly so search engines see the redirects.\n- Spot-check the top pages: content, title, meta, canonical, schema, and that they return 200.\n- Confirm analytics, conversion tracking, and forms work (see the `launch` skill's site launch QA).\n\n**After:**\n- Watch Search Console for 404s and coverage drops daily for two weeks, then weekly. Fix missing redirects as they appear.\n- Compare traffic to the same period before, by page. A dip of a few weeks can be normal; a sustained drop on specific pages usually means a missing redirect or lost content.\n- Update internal links to the new URLs instead of relying on redirects.\n"
},
"site-type-templates.md": {
"name": "Site Type Templates",
"path": "site-type-templates.md",
"content": "# Site Type Templates\n\nFull page hierarchy templates with ASCII trees, URL maps, and navigation recommendations for common site types.\n\n---\n\n## SaaS Marketing Site\n\n### Page Hierarchy\n\n```\nHomepage (/)\n├── Features (/features)\n│ ├── Feature A (/features/feature-a)\n│ ├── Feature B (/features/feature-b)\n│ └── Feature C (/features/feature-c)\n├── Pricing (/pricing)\n├── Customers (/customers)\n│ ├── Case Study 1 (/customers/company-name)\n│ └── Case Study 2 (/customers/company-name-2)\n├── Resources (/resources)\n│ ├── Blog (/blog)\n│ │ └── [Posts] (/blog/post-slug)\n│ ├── Templates (/resources/templates)\n│ │ └── [Template] (/resources/templates/template-slug)\n│ └── Guides (/resources/guides)\n│ └── [Guide] (/resources/guides/guide-slug)\n├── Integrations (/integrations)\n│ └── [Integration] (/integrations/integration-name)\n├── Docs (/docs)\n│ ├── Getting Started (/docs/getting-started)\n│ ├── Guides (/docs/guides)\n│ └── API Reference (/docs/api)\n├── About (/about)\n│ ├── Careers (/about/careers)\n│ └── Contact (/contact)\n├── Compare (/compare)\n│ └── [Competitor] (/compare/competitor-name)\n├── Privacy (/privacy)\n└── Terms (/terms)\n```\n\n### URL Map\n\n| Page | URL | Nav Location | Priority |\n|------|-----|-------------|----------|\n| Homepage | `/` | Header (logo) | Critical |\n| Features | `/features` | Header | High |\n| Feature pages | `/features/{slug}` | Header dropdown | Medium |\n| Pricing | `/pricing` | Header | Critical |\n| Customers | `/customers` | Header | Medium |\n| Case studies | `/customers/{slug}` | Customers dropdown | Medium |\n| Blog | `/blog` | Header (Resources) | High |\n| Blog posts | `/blog/{slug}` | — | Medium |\n| Integrations | `/integrations` | Header | Medium |\n| Docs | `/docs` | Header | Medium |\n| Compare | `/compare/{slug}` | Footer | High (SEO) |\n| About | `/about` | Footer | Low |\n| Pricing CTA | `/pricing` | Header (CTA button) | Critical |\n\n### Navigation\n\n**Header (6 items + CTA)**: Features | Pricing | Customers | Resources | Integrations | Docs | [Get Started]\n\n**Footer columns**:\n- Product: Features, Pricing, Integrations, Changelog, Security\n- Resources: Blog, Templates, Guides, Case Studies\n- Company: About, Careers, Contact, Press\n- Legal: Privacy, Terms, Security\n\n---\n\n## Content / Blog Site\n\n### Page Hierarchy\n\n```\nHomepage (/)\n├── Blog (/blog)\n│ ├── [Category: Topic A] (/blog/category/topic-a)\n│ ├── [Category: Topic B] (/blog/category/topic-b)\n│ ├── [Category: Topic C] (/blog/category/topic-c)\n│ └── [Posts] (/blog/post-slug)\n├── Newsletter (/newsletter)\n├── Resources (/resources)\n│ ├── Guides (/resources/guides)\n│ │ └── [Guide] (/resources/guides/guide-slug)\n│ └── Tools (/resources/tools)\n│ └── [Tool] (/resources/tools/tool-slug)\n├── About (/about)\n├── Contact (/contact)\n├── Privacy (/privacy)\n└── Terms (/terms)\n```\n\n### URL Map\n\n| Page | URL | Nav Location | Priority |\n|------|-----|-------------|----------|\n| Homepage | `/` | Header (logo) | Critical |\n| Blog index | `/blog` | Header | High |\n| Categories | `/blog/category/{slug}` | Header dropdown | Medium |\n| Posts | `/blog/{slug}` | — | Medium |\n| Newsletter | `/newsletter` | Header (CTA) | High |\n| Guides | `/resources/guides` | Header | Medium |\n| About | `/about` | Header | Low |\n\n### Navigation\n\n**Header (4 items + CTA)**: Blog | Resources | About | Contact | [Subscribe]\n\n**Sidebar** (on blog): Categories, Popular Posts, Newsletter signup\n\n---\n\n## E-Commerce\n\n### Page Hierarchy\n\n```\nHomepage (/)\n├── Shop (/shop)\n│ ├── Category A (/shop/category-a)\n│ │ ├── Subcategory (/shop/category-a/subcategory)\n│ │ │ └── [Product] (/shop/category-a/subcategory/product-slug)\n│ │ └── [Product] (/shop/category-a/product-slug)\n│ ├── Category B (/shop/category-b)\n│ │ └── [Product] (/shop/category-b/product-slug)\n│ └── Category C (/shop/category-c)\n│ └── [Product] (/shop/category-c/product-slug)\n├── Collections (/collections)\n│ └── [Collection] (/collections/collection-slug)\n├── Sale (/sale)\n├── Blog (/blog)\n│ └── [Posts] (/blog/post-slug)\n├── About (/about)\n│ └── Our Story (/about/our-story)\n├── Help (/help)\n│ ├── FAQ (/help/faq)\n│ ├── Shipping (/help/shipping)\n│ ├── Returns (/help/returns)\n│ └── Contact (/contact)\n├── Cart (/cart)\n├── Account (/account)\n├── Privacy (/privacy)\n└── Terms (/terms)\n```\n\n### URL Map\n\n| Page | URL | Nav Location | Priority |\n|------|-----|-------------|----------|\n| Homepage | `/` | Header (logo) | Critical |\n| Shop | `/shop` | Header | Critical |\n| Categories | `/shop/{category}` | Header mega menu | High |\n| Products | `/shop/{category}/{product}` | — | High |\n| Collections | `/collections/{slug}` | Header | Medium |\n| Sale | `/sale` | Header (highlighted) | High |\n| Cart | `/cart` | Header (icon) | Critical |\n| Account | `/account` | Header (icon) | Medium |\n\n### Navigation\n\n**Header (5 items + cart/account)**: Shop (mega menu) | Collections | Sale | Blog | Help | [Cart icon] [Account icon]\n\n**Mega menu under Shop**: Category columns with featured products/images\n\n---\n\n## Documentation Site\n\n### Page Hierarchy\n\n```\nDocs Home (/docs)\n├── Getting Started (/docs/getting-started)\n│ ├── Installation (/docs/getting-started/installation)\n│ ├── Quick Start (/docs/getting-started/quick-start)\n│ └── Configuration (/docs/getting-started/configuration)\n├── Guides (/docs/guides)\n│ ├── Guide A (/docs/guides/guide-a)\n│ ├── Guide B (/docs/guides/guide-b)\n│ └── Guide C (/docs/guides/guide-c)\n├── API Reference (/docs/api)\n│ ├── Authentication (/docs/api/authentication)\n│ ├── Endpoints (/docs/api/endpoints)\n│ └── Webhooks (/docs/api/webhooks)\n├── Examples (/docs/examples)\n│ └── [Example] (/docs/examples/example-slug)\n├── Changelog (/docs/changelog)\n└── FAQ (/docs/faq)\n```\n\n### URL Map\n\n| Page | URL | Nav Location | Priority |\n|------|-----|-------------|----------|\n| Docs home | `/docs` | Header | High |\n| Getting Started | `/docs/getting-started` | Sidebar (top) | Critical |\n| Guides | `/docs/guides` | Sidebar | High |\n| API Reference | `/docs/api` | Sidebar | High |\n| Changelog | `/docs/changelog` | Sidebar (bottom) | Low |\n\n### Navigation\n\n**Header**: Docs | API | Blog | Community | GitHub | [Dashboard]\n\n**Sidebar** (persistent, left): Getting Started, Guides, API Reference, Examples, Changelog — with expandable subsections\n\n**On-page**: Previous/Next navigation at bottom of each doc page\n\n---\n\n## Hybrid SaaS + Content\n\n### Page Hierarchy\n\n```\nHomepage (/)\n├── Product (/product)\n│ ├── Feature A (/product/feature-a)\n│ ├── Feature B (/product/feature-b)\n│ └── Feature C (/product/feature-c)\n├── Solutions (/solutions)\n│ ├── By Use Case (/solutions/use-case-slug)\n│ └── By Industry (/solutions/industry-slug)\n├── Pricing (/pricing)\n├── Blog (/blog)\n│ ├── [Category] (/blog/category/slug)\n│ └── [Posts] (/blog/post-slug)\n├── Resources (/resources)\n│ ├── Guides (/resources/guides)\n│ ├── Templates (/resources/templates)\n│ ├── Webinars (/resources/webinars)\n│ └── Case Studies (/resources/case-studies)\n├── Docs (/docs)\n│ ├── Getting Started (/docs/getting-started)\n│ └── API (/docs/api)\n├── Integrations (/integrations)\n│ └── [Integration] (/integrations/slug)\n├── Compare (/compare)\n│ └── [Competitor] (/compare/competitor-slug)\n├── About (/about)\n│ ├── Careers (/about/careers)\n│ └── Contact (/contact)\n├── Privacy (/privacy)\n└── Terms (/terms)\n```\n\n### Navigation\n\n**Header (7 items + CTA)**: Product | Solutions | Pricing | Resources | Blog | Docs | Integrations | [Start Free Trial]\n\nUse mega menus for Product (features list), Solutions (use cases + industries), and Resources (blog, guides, templates, webinars, case studies).\n\n---\n\n## Small Business / Local\n\n### Page Hierarchy\n\n```\nHomepage (/)\n├── Services (/services)\n│ ├── Service A (/services/service-a)\n│ ├── Service B (/services/service-b)\n│ └── Service C (/services/service-c)\n├── About (/about)\n├── Testimonials (/testimonials)\n├── Blog (/blog)\n│ └── [Posts] (/blog/post-slug)\n├── Contact (/contact)\n├── Privacy (/privacy)\n└── Terms (/terms)\n```\n\n### URL Map\n\n| Page | URL | Nav Location | Priority |\n|------|-----|-------------|----------|\n| Homepage | `/` | Header (logo) | Critical |\n| Services | `/services` | Header | High |\n| Service pages | `/services/{slug}` | Header dropdown | High |\n| About | `/about` | Header | Medium |\n| Testimonials | `/testimonials` | Header | Medium |\n| Blog | `/blog` | Header | Medium |\n| Contact | `/contact` | Header (CTA) | High |\n\n### Navigation\n\n**Header (5 items + CTA)**: Services | About | Testimonials | Blog | [Contact Us]\n\nKeep it simple. Small business sites should be flat (1-2 levels max). Every page should be reachable from the header.\n"
}
},
"evals": {
"skill_name": "site-architecture",
"evals": [
{
"id": 1,
"prompt": "Help me plan the site architecture for our new SaaS marketing website. We have a homepage, product page, pricing page, about page, blog, and want to add competitor comparison pages and integration pages.",
"expected_output": "Should check for product-marketing.md first. Should apply the page hierarchy design principles (3-click rule, flat vs deep). Should create an ASCII tree showing the full site structure. Should organize pages logically: main nav (Home, Product, Pricing, About, Blog), comparison pages section, integrations hub. Should recommend URL structure patterns for each section. Should provide navigation design recommendations (4-7 header items). Should include internal linking strategy (hub-and-spoke for comparisons and integrations). Should provide the full deliverable set: hierarchy, URL map, nav spec.",
"assertions": [
"Checks for product-marketing.md",
"Applies 3-click rule and flat vs deep principles",
"Creates ASCII tree for site structure",
"Organizes pages logically",
"Recommends URL structure for each section",
"Provides navigation design (4-7 header items)",
"Includes internal linking strategy",
"Provides hierarchy, URL map, and nav spec"
],
"files": []
},
{
"id": 2,
"prompt": "Our website has grown organically and the navigation is a mess. We have 50+ pages and users can't find anything. Help us reorganize.",
"expected_output": "Should treat this as a site architecture audit and redesign. Should recommend starting with a content inventory of all 50+ pages. Should apply the page hierarchy design to reorganize: group related pages, establish clear parent-child relationships, apply the 3-click rule. Should redesign the navigation (reduce header items, use mega-menu or dropdowns for deeper pages). Should provide before/after ASCII tree structure. Should address URL redirects for any pages that move. Should include a visual sitemap (Mermaid).",
"assertions": [
"Recommends content inventory first",
"Groups related pages logically",
"Applies 3-click rule",
"Redesigns navigation structure",
"Provides ASCII tree or visual sitemap",
"Addresses URL redirects for moved pages",
"Reduces header navigation items"
],
"files": []
},
{
"id": 3,
"prompt": "what should our url structure look like? we keep debating between /blog/post-name vs /resources/blog/post-name and /product/feature vs /features/feature-name",
"expected_output": "Should trigger on casual phrasing. Should apply the URL structure patterns guidance. Should recommend clean, descriptive URLs: prefer shorter paths (/blog/post-name over /resources/blog/post-name), use consistent patterns, avoid unnecessary nesting. Should provide URL structure recommendations for each section type (blog, features, comparisons, integrations). Should address SEO implications of URL structure. Should provide a complete URL map as a reference.",
"assertions": [
"Triggers on casual phrasing",
"Applies URL structure patterns",
"Recommends shorter, cleaner paths",
"Provides recommendations for each section type",
"Addresses SEO implications",
"Provides URL map reference"
],
"files": []
},
{
"id": 4,
"prompt": "We're adding programmatic SEO pages — 200 integration pages and 50 comparison pages. How should these fit into our site architecture?",
"expected_output": "Should address how to integrate scaled content into the site architecture. Should recommend hub pages for both sections (/integrations and /compare or /vs). Should apply the hub-and-spoke internal linking model. Should address navigation: these shouldn't clutter the main nav, but should be accessible via hub pages. Should provide URL structure for both sections. Should address crawl budget considerations for 250 new pages. Should cross-reference programmatic-seo for the content strategy.",
"assertions": [
"Recommends hub pages for each section",
"Applies hub-and-spoke internal linking",
"Keeps programmatic pages out of main nav",
"Provides URL structure for both sections",
"Addresses crawl budget for 250 pages",
"Cross-references programmatic-seo skill"
],
"files": []
},
{
"id": 5,
"prompt": "Can you create a visual sitemap for our site? We want something we can share with our design team.",
"expected_output": "Should provide a visual sitemap using Mermaid diagram format. Should organize the sitemap hierarchically showing page relationships. Should use the Mermaid graph syntax that can be rendered by most tools. Should include all major sections and key pages. Should be clear enough for a design team to use as a reference for navigation and wireframing.",
"assertions": [
"Provides visual sitemap in Mermaid format",
"Shows hierarchical page relationships",
"Includes all major sections",
"Uses clear, readable format",
"Suitable for sharing with design team"
],
"files": []
},
{
"id": 6,
"prompt": "Our XML sitemap hasn't been updated in 6 months and we have crawl errors in Search Console. Can you fix our technical SEO?",
"expected_output": "Should recognize this is a technical SEO audit task, not a site architecture design task. Should defer to or cross-reference the seo-audit skill, which handles XML sitemaps, crawl errors, and technical SEO issues. Site-architecture focuses on page hierarchy, navigation, and URL structure design — not technical SEO troubleshooting.",
"assertions": [
"Recognizes this as technical SEO, not site architecture",
"References or defers to seo-audit skill",
"Explains site-architecture covers design, not technical SEO"
],
"files": []
},
{
"id": 7,
"prompt": "We're a 20-person B2B SaaS on Webflow. Marketing wants a new blog and about 300 integration pages, and someone suggested moving the whole site to an AI website builder. What should we do?",
"expected_output": "Should start from the architecture and the questions in the platforms reference (who edits, page volume and data, integrations, lock-in, cost at real size) rather than naming a platform first. Should keep the current platform (Webflow) in the running and note that moving platforms often costs more than it fixes when the site works. Should compare a shortlist (e.g., staying on Webflow's CMS within its item limits, a reverse-proxied subpath from another tool, or an AI-native platform) with tradeoffs. Any Verified Partner tool named (e.g., Ploy) carries the disclosure and an alternative. Should cover subpath vs subdomain for the new sections and, if migrating, the redirect map and SEO checks.",
"assertions": [
"Asks or reasons through the platform criteria before recommending",
"Keeps the current platform as a real option",
"Gives a shortlist with tradeoffs, not a single answer",
"Discloses any partner tool and names an alternative",
"Covers subpath vs subdomain for the new sections"
],
"files": []
},
{
"id": 8,
"prompt": "We're migrating our marketing site from WordPress to a new platform next month. How do we not lose our SEO traffic?",
"expected_output": "Should lay out the migration plan from the platforms reference: crawl and save every URL with metadata, pull top pages by clicks/conversions/backlinks, keep URLs where possible, check what the CMS import carries (many don't move routes, metadata, redirects), build a one-to-one 301 map (never all to homepage), deploy redirects at switch time, submit the new sitemap, spot-check top pages, verify tracking and forms, and monitor Search Console for 404s afterwards.",
"assertions": [
"Crawls and saves current URLs and metadata first",
"Builds a one-to-one 301 redirect map",
"Warns that imports may not carry routes, metadata, or redirects",
"Includes launch-day checks and post-launch Search Console monitoring"
],
"files": []
}
]
},
"exported_at": "2026-10-12T11:13:42+02:00"
}