Marketer pack
Claude Skill
Site Architecture Planner
Plans a site's page hierarchy, navigation, URLs, and internal linking so users and search engines both find what matters.
What it does
Maps what pages a site needs and how they connect — hierarchy, navigation, URL patterns, breadcrumbs, and internal linking — for a new site or a restructure. Balances user findability against SEO (topic clusters routing link equity to priority pages) and preserves the existing URLs that must redirect. This is information architecture, not crawl/schema technical SEO.
When to use
- ✓Planning a new site or restructuring an existing one
- ✓Users bounce because they can't find what they need
- ✓A flat or messy structure is hurting SEO and conversions
When not to use
- ✗XML sitemaps, crawl errors, or schema — that's technical SEO, a different skill
- ✗A single landing page with no hierarchy to plan
Install
Download the .zip, then unzip into your Claude skills folder.
mkdir -p ~/.claude/skills
unzip ~/Downloads/site-architecture-planner.zip -d ~/.claude/skills/
# Restart Claude Code session.
# Skill is now available — Claude will use it when relevant.SKILL.md
SKILL.md
---
name: site-architecture-planner
description: Use when planning or restructuring a site's page hierarchy, navigation, URL structure, or internal linking. Triggers on "site architecture", "information architecture", "IA", "sitemap", "navigation design", "URL structure", "internal linking strategy", "what pages do I need".
---
# Site Architecture Planner
Plan structure so the site is intuitive for people and legible to search engines at once. Start from the audiences and the top business goals — not from the org chart. The pages a company is organized around are rarely the pages a visitor is looking for.
## Hierarchy
Keep it shallow: the pages that drive conversions or rank should be reachable in three clicks or fewer. Group by what the visitor is trying to do, not by internal team or product taxonomy.
## URL patterns
Readable, stable, and mirroring the hierarchy (`/guides/seo/internal-linking`, not `/page?id=482`). URLs are a commitment — changing them later costs redirects and lost equity, so design them to last.
## Navigation
Navigation is a curated path, not a dump of the whole tree. Expose the routes most visitors need; let secondary pages live in footers, hubs, and contextual links. A mega-menu listing everything helps no one.
## Internal linking as topic clusters
Group related content into clusters: a pillar page links out to its supporting pages and they link back. This routes link equity to the priority (money) pages and tells search engines what the site is authoritative about. Orphan pages — reachable by no internal link — are invisible.
## Preserve and redirect
For a restructure, inventory the URLs that have traffic or backlinks and map a 301 for every one that moves. Breaking URLs without redirects throws away ranking and link equity.
## Anti-patterns
- Navigation that mirrors the org chart instead of visitor intent
- Money pages buried four-plus clicks deep
- Orphan pages with no internal links pointing in
- Changing URLs in a restructure without redirects
- A mega-menu that exposes the entire site at once
Example prompts
Once installed, try these prompts in Claude:
- Plan the IA for a hybrid SaaS + content site — product, docs, blog, comparisons. Give me hierarchy, URLs, and internal-linking rules.
- Our site is a flat list of 60 pages. Restructure it into topic clusters without breaking existing URLs.