site-architecture
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.
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 Type | Typical Depth | Key Sections | URL Pattern |
|---|---|---|---|
| SaaS marketing | 2-3 levels | Home, Features, Pricing, Blog, Docs | I3 , I4 |
| Content/blog | 2-3 levels | Home, Blog, Categories, About | I5 , I6 |
| E-commerce | 3-4 levels | Home, Categories, Products, Cart | I7 |
| Documentation | 3-4 levels | Home, Guides, API Reference | I8 |
| Hybrid SaaS+content | 3-4 levels | Home, Product, Blog, Resources, Docs | I9 , I10 |
| Small business | 1-2 levels | Home, Services, About, Contact | I11 |
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
| 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 | I12 |
| L1 | Primary sections | I13 , /blog, I15 |
| L2 | Section pages | I16 , I17 |
| L3+ | Detail pages | I18 |
ASCII Tree Format
Use this format for page hierarchies:
B0
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
B1
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
- Readable by humans —
/features/analyticsnot/f/a123 - Hyphens, not underscores —
/blog/seo-guidenot/blog/seo_guide - Reflect the hierarchy — URL path should match site structure
- Consistent trailing slash policy — pick one (with or without) and enforce it
- Lowercase always —
/Aboutshould redirect to/about - Short but descriptive —
/blog/how-to-improve-landing-page-conversion-ratesis too long;/blog/landing-page-conversionsis better
URL Patterns by Page Type
| Page Type | Pattern | Example |
|---|---|---|
| Homepage | I27 | I28 |
| Feature page | I29 | I30 |
| Pricing | I31 | I32 |
| Blog post | I33 | I34 |
| Blog category | I35 | I36 |
| Case study | I37 | I38 |
| Documentation | I39 | I40 |
| Legal | I41 | I42 , I43 |
| Landing page | I44 or I45 | I46 , I47 |
| Comparison | I48 or I49 | I50 |
| Integration | I51 | I52 |
| Template | I53 | I54 |
Common Mistakes
- Dates in blog URLs —
/blog/2024/01/15/post-titleadds no value and makes URLs long. Use/blog/post-title. - Over-nesting —
/products/category/subcategory/item/detailis 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/12345is not human-readable. Use slugs. - Query parameters for content —
/blog?id=123should be/blog/post-title. - Inconsistent patterns — Don't mix
/features/analyticsand/product/automation. Pick one parent.
Breadcrumb-URL Alignment
The breadcrumb trail should mirror the URL path:
| URL | Breadcrumb |
|---|---|
| I63 | Home > Features > Analytics |
| I64 | Home > Blog > SEO Guide |
| I65 | 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
B2
With Navigation Zones
B3
For more Mermaid templates: See 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" |
| 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
- No orphan pages — every page must have at least one internal link pointing to it
- Descriptive anchor text — "our analytics features" not "click here"
- 5-10 internal links per 1000 words of content (approximate guideline)
- Link to important pages more often — homepage, key feature pages, pricing
- Use breadcrumbs — free internal links on every page
- 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:
B4
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 | I68 | — | Header | High |
| Features | I69 | Homepage | Header | High |
| Analytics | I70 | Features | Header dropdown | Medium |
| Pricing | I71 | Homepage | Header | High |
| Blog | I72 | 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
- Is this a new site or are you restructuring an existing one?
- What type of site is it? (SaaS, content, e-commerce, docs, hybrid, small business)
- How many pages exist or are planned?
- What are the 5 most important pages on the site?
- Are there existing URLs that need to be preserved or redirected?
- 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
References
Mermaid Templates
mermaid-templates.md
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.
B0
Hierarchy with Navigation Zones
Uses subgraphs to show which pages appear in which navigation area.
B1
Hierarchy with URL Labels
Each node shows the page name and URL path.
B2
Hub-and-Spoke Content Model
Shows a hub page connected to spoke articles, with spokes linking to each other.
B3
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.
B4
Before/After Restructuring
Compare current and proposed site structures side by side.
B5
Color-Coding Conventions
Use styles to highlight page status, priority, or type.
B6
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
Navigation Patterns
navigation-patterns.md
Navigation Patterns
Detailed navigation patterns for different site types and contexts.
Header Navigation
Simple Header (4-6 items)
Best for: small businesses, simple SaaS, portfolios.
B0
Rules:
- Logo always links to homepage
- CTA button is rightmost, visually distinct (filled button, contrasting color)
- Items ordered by priority (most visited first)
- Active page gets visual indicator (underline, bold, color)
Mega Menu Header
Best for: SaaS with many features, e-commerce with categories, large content sites.
B1
When "Product" is hovered/clicked:
B2
Mega menu rules:
- 2-4 columns max
- Group items logically (by feature area, use case, or audience)
- Include a "See all" link at the bottom
- Don't nest dropdowns inside mega menus
- Show descriptions for items when labels alone aren't clear
Split Navigation
Best for: apps with both marketing and product nav.
B3
Right side handles authentication actions. Left side handles page navigation.
Footer Navigation
Column-Based Footer (Standard)
Best for: most sites. Organize links into 3-5 themed columns.
B4
Minimal Footer
Best for: simple sites, landing pages.
B5
Expanded Footer
Best for: sites using footer for SEO (comparison pages, location pages, resource links).
B6
Sidebar Navigation
Documentation Sidebar
Persistent left sidebar with collapsible sections.
B7
Rules:
- Current page highlighted
- Sections collapsible (expanded by default for active section)
- Search at top of sidebar
- "Previous / Next" page navigation at bottom of content area
- Sticky on scroll (doesn't scroll away)
Blog Category Sidebar
B8
Breadcrumbs
Standard Format
B9
Rules:
- Separator:
>or/(be consistent) - Every segment is a link except the current page
- Current page is plain text (not linked)
- Don't include the current page if the title is already visible as an H1
With Schema Markup
B10
Or use JSON-LD (recommended):
B11
Mobile Navigation
Hamburger Menu
Standard for mobile. All nav items collapse into a menu icon.
Rules:
- Hamburger icon (three lines) top-right or top-left
- Full-screen or slide-out panel
- CTA button visible without opening the menu (sticky header)
- Search accessible from mobile menu
- Accordion pattern for nested items
Bottom Tab Bar
Best for: web apps, PWAs, mobile-first products.
B12
Rules:
- 3-5 items max
- Icons + labels (not just icons)
- Active state clearly indicated
- Most important action in the center
Anti-Patterns
Things to Avoid
- Too many header items (8+): causes decision paralysis, nav becomes unreadable on smaller screens
- Dropdown inception: dropdowns inside dropdowns inside dropdowns
- Mystery icons: icons without labels — users don't know what they mean
- Hidden primary nav: burying important pages in hamburger menus on desktop
- Inconsistent nav between pages: nav should be identical across the site (except app vs marketing)
- No mobile consideration: desktop nav that doesn't translate to mobile
- Footer as sitemap dump: 50+ links in the footer with no organization
- Breadcrumbs that don't match URLs: breadcrumb says "Products > Widget" but URL is
/shop/widget-pro
Common Fixes
| Problem | Fix |
|---|---|
| Too many nav items | Group into dropdowns or mega menus |
| Users can't find pages | Add search, improve labeling |
| High bounce from nav | Simplify choices, use clearer labels |
| SEO pages not linked | Add to footer or resource sections |
| Mobile nav is broken | Test on real devices, use hamburger pattern |
Navigation for SEO
Internal links in navigation pass PageRank. Use this strategically:
- Header nav links are strongest — put your most important pages here
- Footer links pass less value but still matter — good for comparison pages, location pages
- Sidebar links help with section-level authority — good for blog categories, doc sections
- Breadcrumbs provide structural signals to search engines — implement with schema markup
- Don't use JavaScript-only nav — search engines need crawlable HTML links
- Use descriptive anchor text — "Analytics Features" not just "Features"
Platforms And Migration
platforms-and-migration.md
Platforms and Migration
Where 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.
The 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.
Contents
- Choosing Where to Build
- The Options
- Adding Pages to an Existing Site
- Migrating Without Losing Traffic
Choosing Where to Build
Ask these before naming any platform. The answers usually narrow the field to two or three.
- 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.
- 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.
- 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-seoskill's platform reference). - 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.
- How much lock-in is acceptable? Can you export the code and content and host it elsewhere? Hosted builders trade portability for convenience.
- 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.
The Options
Characterizations as of 2026-10; check current plans and limits before committing.
| Option | What it is | Good fit | Watch out for |
|---|---|---|---|
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
| 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 |
◆ marks a Verified Partner 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.
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.
Adding Pages to an Existing Site
Often 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.
| Approach | How it works | SEO effect | When to use |
|---|---|---|---|
| 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 |
| 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 |
| Subdomain | I2 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 |
| Separate domain | A new domain for the section | Starts from zero | Rarely, for a genuinely separate brand |
Reverse-proxy checklist:
- The proxied pages return the main domain in their canonical tags, sitemap, and Open Graph URLs, not the origin's.
- Asset paths (CSS, JS, images, fonts) are routed too, or the pages break.
- The origin (for example
origin.example.com) isn't indexed separately: protect it by hostname (a password, an IP allowlist, or anX-Robots-Tag: noindexheader set only on the origin hostname). Then confirm the proxied production responses carry nonoindexin their HTML or headers, because an origin-widenoindexcan pass straight through the proxy and deindex production. Arobots.txtblock alone doesn't prevent indexing. - Analytics and consent run on both systems, configured for one domain.
- Test on a staging subdomain before switching production routing.
Some 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.
Migrating Without Losing Traffic
A 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.
Before:
- Crawl the current site (Screaming Frog, Sitebulb, or the platform's export) and save every URL, title, meta description, canonical, H1, and status code.
- Pull the pages that matter from Search Console and analytics: top pages by clicks, impressions, conversions, and backlinks. These get the most care.
- 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.
- Check what the import carries. Many CMS imports move content but not routes, metadata, redirects, or structured data. Plan to rebuild what's missing.
- Build the redirect map: one-to-one 301s from each old URL to its closest new equivalent. Never redirect everything to the homepage.
At launch:
- Deploy redirects at the same moment as the switch.
- Submit the new sitemap and keep the old one available briefly so search engines see the redirects.
- Spot-check the top pages: content, title, meta, canonical, schema, and that they return 200.
- Confirm analytics, conversion tracking, and forms work (see the
launchskill's site launch QA).
After:
- Watch Search Console for 404s and coverage drops daily for two weeks, then weekly. Fix missing redirects as they appear.
- 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.
- Update internal links to the new URLs instead of relying on redirects.
Site Type Templates
site-type-templates.md
Site Type Templates
Full page hierarchy templates with ASCII trees, URL maps, and navigation recommendations for common site types.
SaaS Marketing Site
Page Hierarchy
B0
URL Map
| Page | URL | Nav Location | Priority |
|---|---|---|---|
| Homepage | I0 | Header (logo) | Critical |
| Features | I1 | Header | High |
| Feature pages | I2 | Header dropdown | Medium |
| Pricing | I3 | Header | Critical |
| Customers | I4 | Header | Medium |
| Case studies | I5 | Customers dropdown | Medium |
| Blog | I6 | Header (Resources) | High |
| Blog posts | I7 | — | Medium |
| Integrations | I8 | Header | Medium |
| Docs | I9 | Header | Medium |
| Compare | I10 | Footer | High (SEO) |
| About | I11 | Footer | Low |
| Pricing CTA | I12 | Header (CTA button) | Critical |
Navigation
Header (6 items + CTA): Features | Pricing | Customers | Resources | Integrations | Docs | [Get Started]
Footer columns:
- Product: Features, Pricing, Integrations, Changelog, Security
- Resources: Blog, Templates, Guides, Case Studies
- Company: About, Careers, Contact, Press
- Legal: Privacy, Terms, Security
Content / Blog Site
Page Hierarchy
B1
URL Map
| Page | URL | Nav Location | Priority |
|---|---|---|---|
| Homepage | I13 | Header (logo) | Critical |
| Blog index | I14 | Header | High |
| Categories | I15 | Header dropdown | Medium |
| Posts | I16 | — | Medium |
| Newsletter | I17 | Header (CTA) | High |
| Guides | I18 | Header | Medium |
| About | I19 | Header | Low |
Navigation
Header (4 items + CTA): Blog | Resources | About | Contact | [Subscribe]
Sidebar (on blog): Categories, Popular Posts, Newsletter signup
E-Commerce
Page Hierarchy
B2
URL Map
| Page | URL | Nav Location | Priority |
|---|---|---|---|
| Homepage | I20 | Header (logo) | Critical |
| Shop | I21 | Header | Critical |
| Categories | I22 | Header mega menu | High |
| Products | I23 | — | High |
| Collections | I24 | Header | Medium |
| Sale | I25 | Header (highlighted) | High |
| Cart | I26 | Header (icon) | Critical |
| Account | I27 | Header (icon) | Medium |
Navigation
Header (5 items + cart/account): Shop (mega menu) | Collections | Sale | Blog | Help | [Cart icon] [Account icon]
Mega menu under Shop: Category columns with featured products/images
Documentation Site
Page Hierarchy
B3
URL Map
| Page | URL | Nav Location | Priority |
|---|---|---|---|
| Docs home | I28 | Header | High |
| Getting Started | I29 | Sidebar (top) | Critical |
| Guides | I30 | Sidebar | High |
| API Reference | I31 | Sidebar | High |
| Changelog | I32 | Sidebar (bottom) | Low |
Navigation
Header: Docs | API | Blog | Community | GitHub | [Dashboard]
Sidebar (persistent, left): Getting Started, Guides, API Reference, Examples, Changelog — with expandable subsections
On-page: Previous/Next navigation at bottom of each doc page
Hybrid SaaS + Content
Page Hierarchy
B4
Navigation
Header (7 items + CTA): Product | Solutions | Pricing | Resources | Blog | Docs | Integrations | [Start Free Trial]
Use mega menus for Product (features list), Solutions (use cases + industries), and Resources (blog, guides, templates, webinars, case studies).
Small Business / Local
Page Hierarchy
B5
URL Map
| Page | URL | Nav Location | Priority |
|---|---|---|---|
| Homepage | I33 | Header (logo) | Critical |
| Services | I34 | Header | High |
| Service pages | I35 | Header dropdown | High |
| About | I36 | Header | Medium |
| Testimonials | I37 | Header | Medium |
| Blog | I38 | Header | Medium |
| Contact | I39 | Header (CTA) | High |
Navigation
Header (5 items + CTA): Services | About | Testimonials | Blog | [Contact Us]
Keep it simple. Small business sites should be flat (1-2 levels max). Every page should be reachable from the header.
Exported from Marketing Skills on 2026-10-12