Site Architecture
A planning system for a website's page hierarchy, navigation, URL patterns, and internal linking — turning a pile of pages into a structure users and search engines can both navigate. Point your agent at it when you're mapping a new site or untangling one that grew into a mess.
Installs the full library — Site Architecture included
Good site architecture keeps every important page within three clicks of the homepage and mirrors that hierarchy in clean, readable URLs like /features/analytics — lowercase, hyphenated, no dates or IDs. Header navigation holds four to seven items ordered by priority with a CTA button rightmost; deeper pages live in dropdowns, the footer, or section sidebars. URLs should stay flat where possible, and any URL that changes needs a 301 redirect to preserve backlink equity. Tie it together with internal linking so no page is orphaned: use a hub-and-spoke model where cluster pages link back to a pillar page, descriptive anchor text instead of 'click here,' and breadcrumbs that mirror the URL path. The typical deliverables are an ASCII page-hierarchy tree, a Mermaid visual sitemap, a URL map table, a navigation spec, and an internal linking plan.
When to use it
Your agent reaches for this skill when you ask for things like:
What's inside
The playbook covers
Reference library — 3 deep-dives
Key data
The recommendations are grounded in benchmarks, not opinion:
See it in action
“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.”
Homepage (/) ├── Features (/features) │ ├── Analytics (/features/analytics) │ └── Automation (/features/automation) ├── Pricing (/pricing) ├── Integrations (/integrations) ← hub for 200 pSEO pages │ └── Slack (/integrations/slack) ├── Compare (/compare) ← hub for 50 comparison pages │ └── vs Competitor (/compare/competitor-name) ├── Blog (/blog) │ └── [Category: SEO] (/blog/category/seo) └── About (/about)
| Page | URL | Parent | Nav Location | Priority | |-----------|------------------------|----------|-----------------|----------| | Analytics | /features/analytics | Features | Header dropdown | Medium | | Pricing | /pricing | Homepage | Header | High | | Slack | /integrations/slack | Integrations | Hub page | Low |
FAQ
What is the 3-click rule in site architecture?
Users should be able to reach any important page within three clicks from the homepage. It isn't an absolute law, but if critical pages sit four or more levels deep, the structure needs flattening. The goal is to stay as flat as possible while keeping navigation clean — if a nav dropdown grows past 20 items, that's the signal to add a level of hierarchy rather than more depth.
How should I structure my URLs?
Make them human-readable and reflective of the hierarchy: lowercase, hyphen-separated (not underscores), short but descriptive, with a consistent trailing-slash policy. Prefer /blog/post-name over /resources/blog/2024/01/post-name — skip dates, IDs, and query parameters for content. Keep patterns consistent (don't mix /features/analytics with /product/automation), and always 301-redirect any URL you change.
Where do programmatic SEO pages fit in the site structure?
Route them under dedicated hub pages — for example /integrations and /compare — rather than cluttering the main navigation. Apply a hub-and-spoke model so each spoke page links back to its hub and the hub links to all spokes, which distributes link equity and keeps hundreds of pages crawlable. Keep them accessible from the hub and footer, not the primary header nav, and watch crawl budget as the count climbs.
Related skills
Build a tool for this workflow?
Marketers run this skill mid-task — the exact moment your tool matters. Partner tiers put your tool inside the skill their agent runs.
See partner tiers →