Agent skill

Site Architecture

by alirezarezvani in alirezarezvani/claude-skills

When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy.

MITAuto-check passedMarketing & SEO

Install Site Architecture

skills CLI
$ npx skills add alirezarezvani/claude-skills --skill site-architecture -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install alirezarezvani/claude-skills site-architecture --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing-skill/skills/site-architecture .claude/skills/site-architecture && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
site-architecture
GitHub stars
28k
Used in
1 other repo
Token cost
~3.5k tokens
SKILL.md length
1,749 words
Files
4 (incl. scripts, references)
Skills in repo
342
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy.

  • Works in 3 steps: Current State → Goals → Constraints
  • Plan their websites structure
  • SKILL.md covers Before Starting, How This Skill Works, URL Structure Principles and Navigation Design, plus 5 more sections
  • Runs Python scripts from its folder

What it does

Site Architecture is an agent skill from alirezarezvani/claude-skills. 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…

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/internal-linking-playbook.md`, `references/url-design-guide.md` and `scripts/sitemap_analyzer.py`).

It sits in Marketing & SEO, covering Content strategy, On-page SEO and Schema markup. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.

When your agent uses it

  • Plan their websites structure
  • Navigation design
  • Internal linking strategy
  • The user mentions site architecture

Example prompts

  • “site architecture,”
  • “URL structure,”
  • “internal links,”
  • “/site-architecture”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Current State
  2. Goals
  3. Constraints

What it can do on your machine

Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Site Architecture loads about 3.5k tokens when it runs, and up to ~7.8k if it reads all its reference files. Until then it costs about 153 tokens; SKILL.md has 1,749 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~153
When it runs · the whole SKILL.md, loaded when a task matches
~3.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~7.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 1,749 words, ~3,482 tokens.

Download SKILL.mdSave it as .claude/skills/site-architecture/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
site-architecture
description
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).
license
MIT
metadata.version
1.0.0
metadata.author
Alireza Rezvani
metadata.category
marketing
metadata.updated
2026-03-06

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.

  • 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
Show full SKILL.md (687 more words)Show less
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

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

© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts, references) in marketing-skill/skills/site-architecture of alirezarezvani/claude-skills.

  • SKILL.md
  • references/internal-linking-playbook.md
  • references/url-design-guide.md
  • scripts/sitemap_analyzer.py

Open the folder on GitHubat commit 19392f7

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in alirezarezvani/claude-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Site Architecture next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Site Architecture compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Site Architecture this skillalirezarezvani/claude-skills28k1 repos~3.5kAutomated safety check: PassMIT
SEO Geoericrisco/rsc-harness180—~2.8kAutomated safety check: PassMIT
Site ArchitectureAvdLee/RocketSimApp80511 repos~3.3kAutomated safety check: PassCustom licence
SEOaffaan-m/ECC276k2 repos~1.1kAutomated safety check: PassMIT
SEO Optimizeraiskillstore/marketplace4331 repos~2.9kAutomated safety check: PassNone
SEOgridaco/grida2.7k—~2.1kAutomated safety check: PassApache-2.0

Similar skills

  • SEO Geo

    ericrisco/rsc-harness

    A skill your agent uses when one existing page needs to rank in Google AND get cited by AI answer engines — auditing a URL for on-page SEO, structured-data JSON-LD, GEO citation levers, Core Web…

    180 GitHub stars~2.8k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Site Architecture

    AvdLee/RocketSimApp

    When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking.

    805 GitHub starsUsed in 11 repos~3.3k tokens
    Marketing & SEOAuto-check passed
  • SEO

    affaan-m/ECC

    Audit, plan, and implement SEO improvements across technical SEO, on-page optimization, structured data, Core Web Vitals, and content strategy.

    276k GitHub starsUsed in 2 repos~1.1k tokens
    Marketing & SEOAuto-check passed
  • SEO Optimizer

    aiskillstore/marketplace

    Search Engine Optimization specialist for content strategy, technical SEO, keyword research, and ranking improvements.

    433 GitHub starsUsed in 1 repo~2.9k tokens
    Marketing & SEOAuto-check passed
  • SEO

    gridaco/grida

    SEO best practices for the Grida project across Next.js pages, blog posts, and documentation.

    2.7k GitHub stars~2.1k tokensUpdated yesterday
    Marketing & SEOAuto-check passed
  • Product Page SEO

    nexscope-ai/eCommerce-Skills

    Optimize e-commerce product pages for search engine visibility.

    1.1k GitHub stars~600 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

More from alirezarezvani/claude-skills

All 342 skills in this repo
  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Auto-check passed
  • Product Strategist

    alirezarezvani/claude-skills

    OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.

    28k GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • App Store Optimization

    alirezarezvani/claude-skills

    App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.

    28k GitHub starsUsed in 1 repo~4.2k tokens
    Auto-check passed
  • AWS Solution Architect

    alirezarezvani/claude-skills

    Design AWS architectures for startups using serverless patterns and IaC templates.

    28k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Campaign Analytics

    alirezarezvani/claude-skills

    Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.

    28k GitHub starsUsed in 1 repo~2.1k tokens
    Auto-check passed
  • Code to PRD

    alirezarezvani/claude-skills

    Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.

    28k GitHub starsUsed in 1 repo~4.9k tokens
    Auto-check passed

Questions about Site Architecture

What does Site Architecture do?

When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy. Site Architecture is an agent skill from alirezarezvani/claude-skills. When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy.

When should I use Site Architecture?

Site Architecture fits situations like: plan their websites structure; navigation design; internal linking strategy; the user mentions site architecture.

How do I install Site Architecture in Claude Code?

Run `npx skills add alirezarezvani/claude-skills --skill site-architecture -a claude-code`. Or copy the skill folder (marketing-skill/skills/site-architecture in alirezarezvani/claude-skills) into .claude/skills/site-architecture in your project. Claude Code loads it when a task matches its description.

How do I install Site Architecture in Codex?

Run `npx skills add alirezarezvani/claude-skills --skill site-architecture -a codex`. Or copy the skill folder (marketing-skill/skills/site-architecture in alirezarezvani/claude-skills) into .agents/skills/site-architecture in your project. Codex loads it when a task matches its description.

Can I use Site Architecture in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill site-architecture -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/site-architecture, .gemini/skills/site-architecture, .github/skills/site-architecture and .opencode/skills/site-architecture in your project.

What does Site Architecture need to run?

Going by SKILL.md and its folder, Site Architecture needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Site Architecture access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Site Architecture safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Site Architecture use?

Site Architecture is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Site Architecture use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.3k tokens, read only when the agent opens those files.

What are the alternatives to Site Architecture?

Skills that share tags, products or a category with Site Architecture: SEO Geo (ericrisco/rsc-harness, 180 stars), Site Architecture (AvdLee/RocketSimApp, 805 stars), SEO (affaan-m/ECC, 276k stars) and SEO Optimizer (aiskillstore/marketplace, 433 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Site Architecture?

alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,938 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.

Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.