MCPInstall

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).

Installs
626
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/alirezarezvani/claude-skills --skill site-architecture
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads site-architecture automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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

Mode 1: Audit Current Architecture

When a site exists and they need a structural assessment.

  1. Run scripts/sitemap_analyzer.py on their sitemap.xml (or paste sitemap content)
  2. Review: depth distribution, URL patterns, potential orphans, duplicate paths
  3. Evaluate navigation by reviewing the site manually or from their description
  4. Identify the top structural problems by SEO impact
  5. Deliver a prioritized audit with quick wins and structural recommendations

Mode 2: Plan New Structure

When building a new site or doing a full redesign/restructure.

  1. Map business goals to site sections
  2. Design URL hierarchy (flat vs layered by content type)
  3. Define content silos for topical authority
  4. Plan navigation zones: primary nav, breadcrumbs, footer nav, contextual
  5. Deliver site map diagram (text-based tree) + URL structure spec

Mode 3: Internal Linking Strategy

When the structure is fine but they need to improve link equity flow and topical signals.

  1. Identify hub pages (the pillar content that should rank highest)
  2. Map spoke pages (supporting content that links to hubs)
  3. Find orphan pages (indexed pages with no inbound internal links)
  4. Identify anchor text patterns and over-optimized phrases
  5. Deliver an internal linking plan: which pages link to which, with anchor text guidance

URL Structure Principles

The Core Rule: URLs are for Humans First

A URL should tell a user exactly where they are before they click. It also tells search engines about content hierarchy. Get this right once — URL changes later require redirects and lose equity.

Flat vs Layered: Pick the Right Depth

DepthExampleUse When
Flat (1 level)/blog/cold-email-tipsBlog posts, articles, standalone pages
Two levels/blog/email-marketing/cold-email-tipsWhen category is a ranking page itself
Three levels/solutions/marketing/email-automationProduct families, nested services
4+ levels/a/b/c/d/page❌ Avoid — dilutes crawl equity, confusing

Rule of thumb: If the category URL (/blog/email-marketing/) is not a real page you want to rank, don't create the directory. Flat is usually better for SEO.

URL Construction Rules

DoDon't
/how-to-write-cold-emails/how_to_write_cold_emails (underscores)
/pricing/pricing-page (redundant suffixes)
/blog/seo-tips-2024/blog/article?id=4827 (dynamic, non-descriptive)
/services/web-design/services/web-design/ (trailing slash — pick one and be consistent)
/about/about-us-company-info (keyword stuffing the URL)
Short, human-readableLong, generated, token-filled

Keywords in URLs

Yes — include the primary keyword. No — don't stuff 4 keywords in.

/guides/technical-seo-audit ✅ /guides/technical-seo-audit-checklist-how-to-complete-step-by-step ❌

The keyword in the URL is a minor signal, not a major one. Don't sacrifice readability for it.

Reference docs

See references/url-design-guide.md for patterns by site type (blog, SaaS, e-commerce, local).


Navigation Design

Navigation serves two masters: user experience and link equity flow. Most sites optimize for neither.

Navigation Zones

ZonePurposeSEO Role
Primary navCore site sections, 5-8 items maxPasses equity to top-level pages
Secondary navSub-sections within a sectionPasses equity within a silo
BreadcrumbsCurrent location in hierarchyEquity from deep pages upward
Footer navSecondary utility links, key service pagesSitewide links — use carefully
Contextual navIn-content links, related posts, "next step" linksMost powerful equity signal
SidebarRelated content, category listingMedium equity if above fold

Primary Navigation Rules

  • 5-8 items maximum. Cognitive load increases with every item.
  • Each nav item should link to a page you want to rank.
  • Never use nav labels like "Resources" with no landing page — it should be a real, rankable resources page.
  • Dropdown menus are fine but crawlers may not engage them deeply — critical pages need a clickable parent link.

Breadcrumbs

Add breadcrumbs to every non-homepage page. They do three things:

  1. Show users where they are
  2. Create site-wide upward internal links to category/hub pages
  3. Enable BreadcrumbList schema for rich results in Google

Format: Home > Category > Subcategory > Current Page

Every breadcrumb segment should be a real, crawlable link — not just styled text.


Silo Structure & Topical Authority

A silo is a self-contained cluster of content about one topic, where all pages link to each other and to a central hub page. Google uses this to determine topical authority.

Hub-and-Spoke Model

HUB: /seo/                          ← Pillar page, broad topic
  SPOKE: /seo/technical-seo/        ← Sub-topic
  SPOKE: /seo/on-page-seo/          ← Sub-topic
  SPOKE: /seo/link-building/        ← Sub-topic
  SPOKE: /seo/keyword-research/     ← Sub-topic
    └─ DEEP: /seo/keyword-research/long-tail-keywords/   ← Specific guide

Linking rules within a silo:

  • Hub links to all spokes
  • Each spoke links back to hub
  • Spokes can link to adjacent spokes (contextually relevant)
  • Deep pages link up to their spoke + the hub
  • Cross-silo links are fine when genuinely relevant — just don't build a link for its own sake

Building Topic Clusters

  1. Identify your core topics (usually 3-7 for a focused site)
  2. For each topic: one pillar page (the hub) that covers it broadly
  3. Create spoke content for each major sub-question within the topic
  4. Every spoke links to the pillar with relevant anchor text
  5. The pillar links down to all spokes
  6. Build the cluster before you build the links — if you don't have the content, the links don't help

Internal Linking Strategy

Internal links are the most underused SEO lever. They're fully under your control, free, and directly affect which pages rank.

Link Equity Principles

  • Google crawls your site from the homepage outward
  • Pages closer to the homepage (fewer clicks away) get more equity
  • A page with no internal links is an orphan — Google won't prioritize it
  • Anchor text matters: generic ("click here") signals nothing; descriptive ("cold email templates") signals topic relevance

Anchor Text Rules

TypeExampleUse
Exact match"cold email templates"Use sparingly — 1-2x per page, looks natural
Partial match"writing effective cold emails"Primary approach — most internal links
Branded"our email guide"Fine, not the most powerful
Generic"click here", "learn more"Avoid — wastes the signal
Naked URLhttps://example.com/guideNever use for internal links

Finding and Fixing Orphan Pages

An orphan page is indexed but has no inbound internal links. It's invisible to the site's link graph.

How to find them:

  1. Export all indexed URLs (from GSC, Screaming Frog, or sitemap_analyzer.py)
  2. Export all internal links on the site
  3. Pages that appear in set A but not set B are orphans
  4. Or: run scripts/sitemap_analyzer.py which flags potential orphan candidates

How to fix them:

  • Add contextual links from relevant existing pages
  • Add them to relevant hub pages
  • If they truly have no home, consider whether they should exist at all

The Linking Priority Stack

Not all internal links are equal. From most to least powerful:

  1. In-content links — within the body copy of a relevant page. Most natural, most powerful.
  2. Hub page links — the pillar page linking to all its spokes. High equity because pillar pages are linked from everywhere.
  3. Navigation links — sitewide, consistent, but diluted by their ubiquity.
  4. Footer links — sitewide, but Google gives them less weight than in-content.
  5. Sidebar links — OK but often not in the main content flow.

See references/internal-linking-playbook.md for patterns and scripts.


Common Architecture Mistakes

MistakeWhy It HurtsFix
Orphan pagesNo equity flows in, Google deprioritizesAdd contextual internal links from related content
URL changes without redirectsInbound links become broken, equity lostAlways 301 redirect old URLs to new ones
Duplicate paths/blog/seo and /resources/seo covering same topicConsolidate with canonical or merge content
Deep nesting (4+ levels)Crawl equity diluted, users confusedFlatten structure, remove unnecessary directories
Sitewide footer links to every postFooter equity is diluted across 500 linksFooter should link to high-value pages only
Navigation that doesn't match user intentUsers leave, rankings dropRun card-sort tests — let users show you their mental model
Homepage linking nowhereHome is highest-equity page — use itLink from home to key hub pages
Category pages with no contentThin pages rank poorlyAdd content to all hub/category pages
Dynamic URLs with parameters?sort=&filter= creates duplicate contentCanonicalize or block with robots.txt

Proactive Triggers

Surface these without being asked:

  • Pages more than 3 clicks from homepage → flag as crawl equity risk. Any page a user has to click 4+ times to reach needs a structural shortcut.
  • Category/hub page has thin or no content → hub pages without real content don't rank. Flag and recommend adding a proper pillar page.
  • Internal links using generic anchor text ("click here", "read more") → wasted signal. Offer to rewrite anchor text patterns.
  • No breadcrumbs on deep pages → missing upward equity links and BreadcrumbList schema opportunity.
  • Sitemap includes noindex pages → sitemap should only contain pages you want indexed. Flag and offer to filter.
  • Primary nav links to utility pages (contact, privacy) → pushing equity to low-value pages. Nav should prioritize money/content pages.

Output Artifacts

When you ask for...You get...
Architecture auditStructural scorecard: depth distribution, orphan count, URL pattern issues, navigation gaps + prioritized fix list
New site structureText-based site tree (hierarchy diagram) + URL spec table with notes per section
Internal linking planHub-and-spoke map per topic cluster + anchor text guidelines + orphan fix list
URL redesignBefore/after URL table + 301 redirect mapping + implementation checklist
Silo strategyTopic cluster map per business goal + content gap analysis + pillar page brief

Communication

All output follows the structured communication standard:

  • Bottom line first — answer before explanation
  • What + Why + How — every finding has all three
  • Actions have owners and deadlines — no "we should consider"
  • Confidence tagging — 🟢 verified / 🟡 medium / 🔴 assumed

Related Skills

  • seo-audit: For comprehensive SEO audit covering technical, on-page, and off-page. Use seo-audit when architecture is one of several problem areas. NOT for deep structural redesign — use site-architecture.
  • schema-markup: For structured data implementation. Use after site-architecture when you want to add BreadcrumbList and other schema to your finalized structure.
  • content-strategy: For deciding what content to create. Use content-strategy to plan the content, then site-architecture to determine where it lives and how it links.
  • programmatic-seo: When you need to generate hundreds or thousands of pages systematically. Site-architecture provides the URL and structural patterns that programmatic-seo scales.
  • seo-audit: For identifying technical issues. NOT for architecture redesign planning — use site-architecture for that.

FAQ

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 site-architecture?

Run npx skills add https://github.com/alirezarezvani/claude-skills --skill site-architecture in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/site-architecture/ (personal) or .claude/skills/site-architecture/ (project).

Which AI agents can use site-architecture?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is site-architecture safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains site-architecture?

It is published by alirezarezvani in alirezarezvani/claude-skills. It has 626 recorded installs.

More from alirezarezvani/claude-skills

View all →

engineering-skills

alirezarezvani/claude-skills

Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or choosing among engineering-team role skills — load only the one specialist SKILL.md you need, never bulk-load the bundle.

Backend & APIs2.4K installs

finance-skills

alirezarezvani/claude-skills

Router/index for the finance skills bundled in this plugin: financial-analyst (ratio analysis, DCF valuation, budget variance, rolling forecasts), saas-metrics-coach (ARR/MRR, churn, CAC/LTV, NRR, quick ratio) and month-end-close (close calendar, reconciliations, flux review). Use when a finance request doesn't obviously match one skill and you need to pick the right one (e.g., 'analyze these financials', 'how healthy are my SaaS metrics').

Business & Finance2.3K installs

marketing-skills

alirezarezvani/claude-skills

Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill — it does not execute marketing work itself.

Marketing & SEO2.3K installs

business-growth-skills

alirezarezvani/claude-skills

Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP').

Business & Finance2.2K installs

engineering-advanced-skills

alirezarezvani/claude-skills

Index of 37 advanced engineering agent skills for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Use when browsing or choosing among the POWERFUL-tier engineering skills: agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, changelog/release automation, reliability (SLO/chaos/flags/operators), platform ops.

AI & Agents2K installs

product-skills

alirezarezvani/claude-skills

Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.