Site Architecture
alirezarezvani/claude-skills
When the user wants to audit, redesign, or plan their website's structure, URL hierarchy, navigation design, or internal linking strategy.
Information architecture, URL hierarchy, internal linking strategy, navigation design, and silo structure for websites.
Install Site Architecture
$ npx skills add borghei/Claude-Skills --skill site-architecture -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills site-architecture --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/site-architecture .claude/skills/site-architecture && rm -rf skills-srcUse ~/.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/
Install the "site-architecture" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/site-architecture into .claude/skills/site-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-architecture", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/marketing/site-architectureType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill site-architecture -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills site-architecture --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/site-architecture .agents/skills/site-architecture && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "site-architecture" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/site-architecture into .agents/skills/site-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-architecture", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill site-architecture -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills site-architecture --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/site-architecture .cursor/skills/site-architecture && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "site-architecture" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/site-architecture into .cursor/skills/site-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-architecture", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path marketing/site-architecture--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill site-architecture -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills site-architecture --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/site-architecture .gemini/skills/site-architecture && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "site-architecture" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/site-architecture into .gemini/skills/site-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-architecture", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills site-architectureInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill site-architecture -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/site-architecture .github/skills/site-architecture && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "site-architecture" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/site-architecture into .github/skills/site-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-architecture", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill site-architecture -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills site-architecture --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/site-architecture .opencode/skills/site-architecture && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "site-architecture" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/site-architecture into .opencode/skills/site-architecture/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "site-architecture", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
site-architecture- GitHub stars
- 881
- Token cost
- ~5.6k tokens
- SKILL.md length
- 2,378 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
Information architecture, URL hierarchy, internal linking strategy, navigation design, and silo structure for websites.
- Works in 3 steps: UX: Show users their location in the… → SEO: Create sitewide upward internal… → Rich results: Enable BreadcrumbList…
- Tasks that involve On-page SEO
- SKILL.md covers Table of Contents, Clarify First, Operating Modes and URL Structure Design, plus 5 more sections
- Runs Python scripts from its folder; calls python
What it does
Site Architecture is an agent skill from borghei/Claude-Skills. Information architecture, URL hierarchy, internal linking strategy, navigation design, and silo structure for websites. Covers architectural audits, new site planning, crawl equity optimization, and topic cluster mapping.
Its SKILL.md is about 5.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/link_mapper.py`, `scripts/redirect_checker.py` and `scripts/sitemap_analyzer.py`).
It sits in Marketing & SEO, covering On-page SEO, Content strategy and UX design. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Tasks that involve On-page SEO
- Tasks that involve Content strategy
- Tasks that involve UX design
Example prompts
- “/site-architecture”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- UX: Show users their location in the hierarchy
- SEO: Create sitewide upward internal links to hub/category pages
- Rich results: Enable BreadcrumbList schema for SERP breadcrumbs
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. 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 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
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 5.6k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 2,378 words of instructions outside code blocks.
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 borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 2,378 words, ~5,588 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
- Information architecture, URL hierarchy, internal linking strategy, navigation design, and silo structure for websites. Covers architectural audits, new site planning, crawl equity optimization, and topic cluster mapping.
- license
- MIT + Commons Clause
- metadata.version
- 1.0.0
- metadata.author
- borghei
- metadata.category
- marketing-growth
- metadata.updated
- 2026-03-31
- metadata.tags
- seo, information-architecture, internal-linking, url-structure, navigation, siloing
Site Architecture & Internal Linking
Production-grade website architecture framework covering URL hierarchy design, internal linking strategy, navigation optimization, silo structure, and crawl equity management. Handles architecture audits, new site planning, and restructuring existing sites.
Table of Contents
- Operating Modes
- URL Structure Design
- Navigation Architecture
- Silo Structure and Topic Clusters
- Internal Linking Strategy
- Crawl Equity Management
- Architecture Audit Framework
- Restructuring Playbook
- Architecture Patterns by Site Type
- Common Mistakes
- Output Artifacts
- Related Skills
Clarify First
Before generating the architecture, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Operating mode — audit current, plan new, internal-linking optimization, or URL restructuring — determines the artifact produced
- Site type — SaaS, e-commerce, blog/content, local, docs, or marketplace — selects the URL pattern and architecture template
- Core topics / silos — the 3-7 topic clusters the site covers — drives the hub-and-spoke and internal-linking plan
- Current URLs / crawl data — sitemap or URL export — required for audits and redirect mapping
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Operating Modes
Mode 1: Audit Current Architecture
Existing site needs structural assessment. Analyze depth distribution, orphan pages, link equity flow, and navigation effectiveness.
Mode 2: Plan New Architecture
Building from scratch or full redesign. Map business goals to site sections, design URL hierarchy, plan navigation, and define content silos.
Mode 3: Internal Linking Optimization
Structure is fine but link equity flow needs improvement. Identify hub pages, map spoke content, fix orphans, and optimize anchor text.
Mode 4: URL Restructuring
Changing URLs on an existing site. Plan the new structure, build redirect maps, and manage the migration.
URL Structure Design
Depth Guidelines
| Depth | Example | Use When | SEO Impact |
|---|---|---|---|
| 1 level (flat) | /cold-email-tips | Blog posts, standalone pages | Best crawl equity per page |
| 2 levels | /email-marketing/cold-email-tips | Category is a rankable page itself | Good, category page accumulates authority |
| 3 levels | /solutions/marketing/email-automation | Product families, nested services | Acceptable if each level has content |
| 4+ levels | /a/b/c/d/page | Never | Diluted equity, poor UX, crawl issues |
Decision rule: If the intermediate directory URL (/email-marketing/) will NOT be a real page with its own content and ranking target, do not create the directory. Flat is better than empty hierarchy.
URL Construction Rules
| Rule | Good | Bad | Why |
|---|---|---|---|
| Use hyphens | /seo-audit | /seo_audit | Underscores are not word separators for Google |
| Be descriptive | /pricing | /pricing-page | Redundant suffixes add nothing |
| Keep short | /guides/technical-seo | /guides/technical-seo-audit-checklist-complete-guide | Readability matters |
| Include keyword | /guides/seo-audit | /guides/article?id=4827 | Descriptive URLs rank better |
| Be consistent with trailing slashes | Pick one: /about or /about/ | Mix of both | Inconsistency creates duplicate content |
| Use lowercase | /about-us | /About-Us | Case sensitivity varies by server |
URL Patterns by Site Type
| Site Type | Pattern | Example |
|---|---|---|
| SaaS | /features/[feature], /solutions/[use-case], /integrations/[partner] | /features/analytics, /solutions/marketing, /integrations/slack |
| E-commerce | /[category]/[subcategory]/[product] | /mens/shoes/running-shoes-pro |
| Blog/Content | /blog/[slug] or /blog/[category]/[slug] | /blog/seo-audit-guide |
| Local business | /[service]/[location] | /plumbing/austin-tx |
| Documentation | /docs/[section]/[page] | /docs/api/authentication |
| Marketplace | /[category]/[listing] | /designers/john-smith |
Navigation Architecture
Navigation Zones
Every site has 6 navigation zones. Each serves a different purpose and carries different SEO weight.
| Zone | Items | SEO Weight | Design Rule |
|---|---|---|---|
| Primary nav | 5-8 items max | High (sitewide equity) | Only pages you want to rank for. Never "Resources" without a landing page. |
| Secondary nav | 3-7 per section | Medium | Sub-navigation within a section/silo |
| Breadcrumbs | Dynamic | High (upward equity) | Every non-homepage page. Each segment must be a real link. |
| Footer nav | 8-15 items max | Low-Medium | Key pages only. Not a dumping ground for every page. |
| Contextual (in-content) | 3-5 per page | Highest | Most powerful signal. Natural editorial links within body content. |
| Sidebar | 5-10 items | Low-Medium | Related content, category listing |
Primary Navigation Design
Rules:
- 5-8 items maximum. Cognitive overload starts at 9+ items.
- Every nav item links to a page you actively want to rank.
- Dropdown menus are fine, but the parent item must be a clickable, crawlable link (not just a hover trigger).
- Do not put utility pages (Contact, Privacy, Terms) in primary nav -- they belong in the footer.
- Mobile nav must expose the same structure as desktop nav (no hidden critical pages).
Breadcrumb Implementation
Add breadcrumbs to every non-homepage page. They serve three functions:
- UX: Show users their location in the hierarchy
- SEO: Create sitewide upward internal links to hub/category pages
- Rich results: Enable BreadcrumbList schema for SERP breadcrumbs
Format: Home > Category > Subcategory > Current Page
Rules:
- Every breadcrumb segment must be a real, crawlable link
- Never use breadcrumbs as styled text without links
- Add BreadcrumbList schema markup alongside visible breadcrumbs
- Breadcrumb hierarchy should match URL hierarchy
Silo Structure and Topic Clusters
Hub-and-Spoke Model
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.
┌──────────────────┐
│ HUB PAGE │
│ /seo/ │
│ (Pillar content)│
└────────┬─────────┘
┌────────────────┼────────────────┐
┌────┴────┐ ┌───┴────┐ ┌────┴────┐
│ SPOKE 1 │ │ SPOKE 2│ │ SPOKE 3 │
│technical│ │on-page │ │ link │
│ seo │ │ seo │ │building │
└────┬────┘ └───┬────┘ └────┬────┘
│ │ │
Cross-links Cross-links Cross-links
between between between
related related related
spokes spokes spokesBuilding Topic Clusters
Step 1: Identify 3-7 core topics for your site (these become your silos)
Step 2: For each topic, create one pillar page (the hub) that covers the topic broadly
Step 3: Create spoke content for each major sub-question or sub-topic
Step 4: Implement linking:
- Hub links DOWN to every spoke
- Every spoke links UP to the hub (with keyword-rich anchor text)
- Spokes link ACROSS to related spokes within the same silo
- Cross-silo links are fine when contextually genuine
Step 5: Build the content before building the links. Links to non-existent content are useless.
Silo Depth Guidelines
| Silo Size | Recommended Depth | Structure |
|---|---|---|
| 3-5 spokes | Flat | Hub + spokes, all at same level |
| 6-15 spokes | Shallow nested | Hub > Sub-hubs > Spokes |
| 16-50 spokes | Two-level | Hub > Category sub-hubs > Individual spokes |
| 50+ spokes | Paginated | Hub > Category sub-hubs > Paginated spoke listings |
Internal Linking Strategy
Link Equity Power Stack
Not all internal links carry equal weight. From most to least powerful:
| Rank | Link Type | Weight | When to Use |
|---|---|---|---|
| 1 | In-content contextual link | Highest | Natural editorial links within body copy |
| 2 | Hub page link | High | Pillar page linking to all its spokes |
| 3 | Navigation link | Medium | Sitewide, consistent, but diluted by ubiquity |
| 4 | Breadcrumb link | Medium | Upward equity flow, consistent |
| 5 | Footer link | Low | Sitewide, Google discounts these |
| 6 | Sidebar link | Low | Often not in main content flow |
Anchor Text Strategy
| Type | Example | Usage | Signal Strength |
|---|---|---|---|
| Partial match | "effective cold email strategies" | Primary approach (60-70% of links) | Strong |
| Exact match | "cold email templates" | Use sparingly (10-15% of links) | Strong but risky if overused |
| Branded | "our email guide" | Natural variation (10-15%) | Moderate |
| Descriptive | "this comprehensive guide" | Natural variation (5-10%) | Weak but natural |
| Generic | "click here", "learn more" | Avoid (< 5%) | None -- wasted signal |
| Naked URL | https://example.com/guide | Never for internal links | None |
Orphan Page Detection and Resolution
An orphan page is indexed in Google but has zero inbound internal links. It is invisible to the site's link graph.
Detection method:
- Export all indexed URLs (GSC Coverage or site: query)
- Export all internal link targets (crawl tool or link extraction)
- Pages in set A but not set B are orphans
Resolution actions:
| Orphan Type | Action |
|---|---|
| Valuable content, belongs in a silo | Add contextual links from 3+ related pages |
| Old content, still relevant | Link from hub page and 1-2 spokes |
| Outdated content, no value | Redirect to relevant page or noindex |
| Utility page (shouldn't be indexed) | Add noindex |
Internal Linking Audit Checklist
| Check | Pass Criteria |
|---|---|
| Every content page has 3-5 outbound internal links | No page links only to itself or navigation |
| Every target page has 3+ inbound internal links | No orphans in the indexed set |
| Hub pages link to all their spokes | Complete coverage |
| Anchor text is descriptive and varied | No > 30% exact match for any keyword |
| No broken internal links | 0 broken links |
| Link depth from homepage < 4 clicks | 95%+ of pages within 3 clicks |
Crawl Equity Management
Homepage Equity Distribution
The homepage is your highest-equity page. Use it wisely.
| Homepage Link Target | Priority |
|---|---|
| Hub/pillar pages (top of each silo) | Highest -- link from homepage content area |
| Key product/service pages | High -- link from homepage or primary nav |
| Top-performing content | Medium -- link if contextually relevant |
| Utility pages (contact, about) | Low -- footer links only |
| Blog index | Medium -- primary or secondary nav |
Crawl Budget Allocation
| Page Category | % of Crawl Budget | Optimization |
|---|---|---|
| Money pages (product, pricing, features) | 20-30% | Internal link from homepage + nav |
| Pillar content (hub pages) | 20-30% | Extensive internal linking |
| Spoke content (blog, guides) | 30-40% | Linked from hubs + contextual |
| Utility pages (about, contact, legal) | 5-10% | Footer links only, minimal crawl |
| Tag/archive/pagination | < 5% | Noindex if thin, limit crawling |
Architecture Audit Framework
Audit Scorecard
| Dimension | Weight | Check |
|---|---|---|
| Crawl depth | 20% | 95%+ pages within 3 clicks of homepage |
| Orphan pages | 20% | 0 orphan pages in indexed set |
| URL cleanliness | 15% | Clean, descriptive, consistent URLs |
| Navigation completeness | 15% | All key pages accessible via primary/secondary nav |
| Internal link coverage | 15% | Every page has 3+ inbound internal links |
| Silo coherence | 10% | Topic clusters are well-defined with clear hub-spoke relationships |
| Breadcrumb implementation | 5% | Present on all non-homepage pages with schema |
Show full SKILL.md (946 more words)Show less
Red Flag Indicators
| Signal | Severity | Action |
|---|---|---|
| Pages > 3 clicks from homepage | High | Create shortcuts via nav or hub page links |
| Hub page has no content (just links) | High | Add pillar content to all hub pages |
| Generic anchor text dominant (> 30%) | Medium | Rewrite anchor text to be descriptive |
| No breadcrumbs on deep pages | Medium | Implement breadcrumbs with BreadcrumbList schema |
| Sitemap includes noindex pages | Medium | Filter sitemap to only indexable pages |
| Primary nav links to utility pages | Low | Move Contact/Privacy to footer |
| Footer contains 50+ links | Low | Reduce to 8-15 key pages |
Restructuring Playbook
When to Restructure
| Signal | Restructure? | Alternative |
|---|---|---|
| Complete URL overhaul needed | Yes | -- |
| Adding 3 new sections | Partial -- new sections only | -- |
| Fixing orphan pages | No | Add internal links, no URL changes needed |
| Improving nav | No | Update navigation, keep URLs |
| Moving to new CMS | Yes (usually) | Keep URL structure if CMS supports it |
Restructuring Steps
- Crawl current site -- Export all URLs, internal links, and rankings
- Map current to new -- Create 1:1 URL redirect mapping
- Build redirect rules -- 301 redirects for every changed URL
- Chain existing redirects -- Update old redirects to point to final destination
- Update internal links -- Point to new URLs (do not rely on redirects for internal links)
- Update sitemap -- Reflect new URL structure
- Monitor for 60 days -- Watch for crawl errors, ranking changes, traffic impact
Architecture Patterns by Site Type
SaaS Website
/ Homepage
├── /features/ Features hub
│ ├── /features/analytics Analytics feature
│ └── /features/reporting Reporting feature
├── /solutions/ Solutions hub (by use case)
│ ├── /solutions/marketing Marketing use case
│ └── /solutions/sales Sales use case
├── /integrations/ Integrations hub
│ ├── /integrations/slack Slack integration
│ └── /integrations/salesforce Salesforce integration
├── /pricing Pricing page
├── /blog/ Blog index
│ ├── /blog/seo-guide Blog post
│ └── /blog/growth-tips Blog post
├── /docs/ Documentation
└── /about About pageE-commerce Site
/ Homepage
├── /[category]/ Category page (with content)
│ ├── /[category]/[subcategory]/ Subcategory (with content)
│ │ └── /[category]/[subcategory]/[product] Product page
│ └── /[category]/[product] Product (if no subcategory)
├── /brands/ Brand hub
│ └── /brands/[brand] Brand page
├── /blog/ Content hub
└── /sale/ Promotions hubContent/Media Site
/ Homepage
├── /[topic]/ Topic hub (pillar content)
│ ├── /[topic]/[subtopic] Subtopic article
│ └── /[topic]/[guide] In-depth guide
├── /authors/ Author hub
│ └── /authors/[name] Author page
├── /tools/ Free tools hub
│ └── /tools/[tool] Individual tool
└── /newsletter Newsletter signupCommon Mistakes
| Mistake | Why It Hurts | Fix |
|---|---|---|
| Orphan pages | No equity flows in, Google deprioritizes | Add contextual internal links from related content |
| URL changes without redirects | Lost link equity and broken backlinks | Always 301 redirect old URLs |
| Deep nesting (4+ levels) | Diluted crawl equity, confusing UX | Flatten structure |
| Empty category pages | Thin pages do not rank | Add pillar content to all category/hub pages |
| Homepage linking to nothing | Wastes highest-equity page | Link from home to all hub pages |
| Footer with 100+ links | Dilutes equity across too many targets | Limit footer to 8-15 key pages |
| Navigation not matching user mental model | Users leave, engagement drops | Run card-sort testing with real users |
| Dynamic parameter URLs | Creates duplicate content | Canonicalize or block with robots.txt |
| Sitewide sidebar links to every post | Diluted equity, adds noise | Remove or limit to "popular" posts |
Output Artifacts
| Artifact | Format | Description |
|---|---|---|
| Architecture Audit Scorecard | Weighted score table | Per-dimension scores with red flag indicators |
| Site Tree Diagram | Text-based hierarchy | Visual URL structure with annotations |
| URL Specification Table | Table | URL pattern, title template, parent page, schema type per section |
| Internal Linking Plan | Hub-spoke map | Topic cluster map with anchor text guidelines and orphan fix list |
| Redirect Map | Before/after URL table | 1:1 mapping for URL restructuring with 301 implementation |
| Navigation Spec | Zone-by-zone design | Primary, secondary, breadcrumb, footer, and contextual nav plans |
Related Skills
- seo-audit -- For comprehensive SEO audits where architecture is one of several problem areas. Use seo-audit for the full picture, site-architecture for deep structural work.
- schema-markup -- For adding BreadcrumbList and other structured data after architecture decisions are finalized.
- programmatic-seo -- For hub-and-spoke structures at scale when generating hundreds of template-based pages.
- content-creator -- For creating the pillar content that hub pages need to rank effectively.
Troubleshooting
| Problem | Likely Cause | Fix |
|---|---|---|
| Orphan pages appearing in Google index | Pages exist in sitemap or have external links but no internal links pointing to them | Add contextual internal links from 3+ related pages; update hub pages to include them |
| Crawl depth exceeds 4+ clicks for key pages | Flat navigation missing or hub pages not linking to spokes | Create shortcut links via primary nav, hub page content blocks, or featured sections |
| Category/hub pages ranking poorly | Hub pages have no substantive content — just link lists | Add 800+ words of pillar content to every hub page; they must rank on their own merit |
| Redirect chains after site migration | Old redirects not updated to point to final destination; chains accumulate over multiple migrations | Audit all existing redirects; collapse chains so every redirect points directly to the final URL |
| Internal links using generic anchor text | "Click here" and "learn more" anchor text dominating internal links | Rewrite anchors to be descriptive with partial-match keywords; aim for 60-70% partial match |
| New sections not getting crawled | No internal links from existing high-authority pages to new section | Add contextual links from homepage and related hub pages; submit new section sitemap |
Success Criteria
- Crawl depth: 95%+ of indexable pages reachable within 3 clicks from homepage
- Zero orphan pages: No indexed pages without at least 3 inbound internal links
- URL cleanliness: 100% of URLs follow the established pattern — lowercase, hyphenated, descriptive, consistent trailing slash policy
- Navigation coverage: All key revenue and pillar pages accessible via primary or secondary navigation
- Internal link density: Every content page has 3-5 outbound contextual internal links with descriptive anchor text
- Silo coherence: Each topic cluster has a defined hub page with bidirectional links to all spokes
- Breadcrumb coverage: BreadcrumbList schema present on 100% of non-homepage pages
Scope & Limitations
In scope:
- URL hierarchy design and restructuring
- Navigation architecture (primary, secondary, breadcrumb, footer, contextual, sidebar)
- Silo structure and topic cluster planning
- Internal linking strategy and optimization
- Crawl equity analysis and optimization
- Architecture audits with scored reports
- URL migration planning with redirect mapping
Out of scope:
- Content creation for hub pages (use Content Production)
- Schema markup implementation (use Schema Markup)
- Technical SEO beyond architecture (use SEO Audit)
- Visual design or UX design of navigation
- CMS development or template coding
- External link building
Known limitations:
- Crawl equity distribution is estimated — Google does not publish exact PageRank flow data
- Architecture changes on large sites (10K+ pages) require careful phased migration to avoid traffic loss
- Navigation testing (card sorts, tree tests) requires user research tools and participants
- Cross-silo linking recommendations are qualitative — no deterministic formula exists for optimal cross-linking density
Scripts
# Analyze sitemap for depth and structure issues
python scripts/sitemap_analyzer.py --file sitemap.xml --json
# Check URLs for redirect chains and patterns
python scripts/redirect_checker.py --file urls.txt --json
# Map internal link structure from a sitemap
python scripts/link_mapper.py --sitemap sitemap.xml --json© borghei, 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) in marketing/site-architecture of borghei/Claude-Skills.
- SKILL.md
- scripts/link_mapper.py
- scripts/redirect_checker.py
- scripts/sitemap_analyzer.py
Open the folder on GitHubat commit 4a698e8
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Site Architecture this skillborghei/Claude-Skills | 881 | — | ~5.6k | Automated safety check: Pass | MIT | |
| Site Architecturealirezarezvani/claude-skills | 28k | 1 repos | ~3.5k | Automated safety check: Pass | MIT | |
| SEO Keyword ClusteringAgriciDaniel/claude-seo | 18k | 2 repos | ~3.3k | Automated safety check: Pass | MIT | |
| SEO Content Brief GeneratorAgriciDaniel/claude-seo | 18k | 2 repos | ~2.6k | Automated safety check: Pass | MIT | |
| SEO Keyword Clusterseranking/seo-skills | 160 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Tools Page SEO Optimizersickn33/agentic-awesome-skills | 47k | 1 repos | ~596 | Automated safety check: Pass | MIT |
Similar skills
SEO Keyword Clustering
AgriciDaniel/claude-seo
Clusters keywords by how much their search results overlap and designs a hub-and-spoke content plan with an internal link matrix and an interactive cluster map.
SEO Content Brief Generator
AgriciDaniel/claude-seo
Builds research-backed SEO content briefs with competitor scoring, per-section word counts and page-type templates, for new pages or improving existing ones.
SEO Keyword Cluster
seranking/seo-skills
Build a content cluster plan from seed keywords — intent-grouped clusters, pillar+spokes architecture with H1/H2 suggestions per spoke, prioritised build order, and an internal-linking map.
Tools Page SEO Optimizer
sickn33/agentic-awesome-skills
Framework-agnostic SEO workflow for any site with multiple tool, product, or feature pages.
Content Brief Authoring
rampstackco/claude-skills
How to author a content brief that actually guides a writer (human or AI) to produce a piece that ranks, converts, or both.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Categories
Questions about Site Architecture
What does Site Architecture do?
Information architecture, URL hierarchy, internal linking strategy, navigation design, and silo structure for websites. Site Architecture is an agent skill from borghei/Claude-Skills. Information architecture, URL hierarchy, internal linking strategy, navigation design, and silo structure for websites.
When should I use Site Architecture?
Site Architecture fits situations like: tasks that involve On-page SEO; tasks that involve Content strategy; tasks that involve UX design.
How do I install Site Architecture in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill site-architecture -a claude-code`. Or copy the skill folder (marketing/site-architecture in borghei/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 borghei/Claude-Skills --skill site-architecture -a codex`. Or copy the skill folder (marketing/site-architecture in borghei/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 borghei/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 and the command-line tools its instructions call (python). 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 5.6k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Site Architecture?
Skills that share tags, products or a category with Site Architecture: Site Architecture (alirezarezvani/claude-skills, 28k stars), SEO Keyword Clustering (AgriciDaniel/claude-seo, 18k stars), SEO Content Brief Generator (AgriciDaniel/claude-seo, 18k stars) and SEO Keyword Cluster (seranking/seo-skills, 160 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Site Architecture?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/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.