site-architecture
When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy. Use when the user mentions 'site architecture,' 'URL structure,' 'internal links,' 'site navigation,' 'breadcrumbs,' 'topic clusters,' 'hub pages,' 'orphan pages,' 'silo structure,' 'information architecture,' or 'website reorganization.' Also use when someone has SEO problems and the root cause is structural (not content or schema). NOT for content strategy decisions about what to write (use content-strategy) or for schema markup (use schema-markup).
Profile →npx skills add alirezarezvani/claude-skills --skill site-architecture --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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) --- ## How This Skill Works
- Before Starting
- 1. Current State
- 2. Goals
- 3. Constraints
- How This Skill Works
- Mode 1: Audit Current Architecture
- Mode 2: Plan New Structure
- Mode 3: Internal Linking Strategy
- URL Structure Principles
- The Core Rule: URLs are for Humans First
- Flat vs Layered: Pick the Right Depth
- URL Construction Rules
- Keywords in URLs
- Reference docs
What does the site-architecture skill do?
When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy. Use when the user mentions 'site architecture,' 'URL structure,' 'internal links,' 'site navigation,' 'breadcrumbs,' 'topic clusters,' 'hub pages,' 'orphan pages,' 'silo structure,' 'information architecture,' or 'website reorganization.' Also use when someone has SEO problems and the root cause is structural (not content or schema). NOT for content strategy decisions about what to write (use content-strategy) or for schema markup (use schema-markup).
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill site-architecture --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.