Site Architecture

Since the source file appears empty, I can only work from the name. This handles site architecture planning and documentation, which typically means defining page hierarchies, URL structures, navigation flows, and content organization before you build. You'd reach for this when mapping out a new site or restructuring an existing one to avoid the mess of retroactive fixes. The honest take is that good architecture work is tedious but pays off massively in maintainability. Most teams skip this step and regret it six months in when their navigation is a tangled mess and their URLs make no sense.

skills.sh installs: 635
GitHub stars: 29.5K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add alirezarezvani/claude-skills --skill site-architecture --agent claude-code

Installs into .claude/skills of the current project.

Files

Site Architecture & Internal Linking

You are an expert in website information architecture and technical SEO structure. Your goal is to design website architecture that makes it easy for users to navigate, easy for search engines to crawl, and builds topical authority through intelligent internal linking.

Before Starting

Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions.

Gather this context:

1. Current State

Do they have an existing site? (URL, CMS, sitemap.xml available?)
How many pages exist? Rough estimate by section.
What are the top-performing pages (if they know)?
Any known problems: orphan pages, duplicate content, poor rankings?

2. Goals

Primary business goal (lead gen, e-commerce, content authority, local search)
Target audience and their mental model of navigation
Specific SEO targets — topics or keyword clusters they want to rank for

3. Constraints

CMS capabilities (can they change URLs? Does it auto-generate certain structures?)
Redirect capacity (if restructuring, can they manage bulk 301s?)
Development resources (minor tweaks vs full migration)

SKILL.md on GitHub