New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Audit, redesign, or plan their website's structure

Site Architecture & Internal Linking

by alirezarezvani · MIT license · ★ 26,349 on GitHub · updated Aug 30

Site Architecture & Internal Linking cover

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…

---
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
  author: Alireza Rezvani
  category: marketing
  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:**

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add alirezarezvani/claude-skills --skill site-architecture -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/alirezarezvani/claude-skills/tar.gz/19392f7a0826 \ | tar -xz -C ~/.claude/skills --strip-components=3 claude-skills-19392f7a0826/marketing-skill/skills/site-architecture
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/27f2d12a3c1a13db3c04/site-architecture.zip" -OutFile "$env:TEMP\site-architecture.zip"; Expand-Archive "$env:TEMP\site-architecture.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md13.7 KB
  • references/2 files · 16.8 KB
  • scripts/1 file · 14.8 KB
Read the files here
alirezarezvani/19392f74 files
SKILL.md
Show the full text290 lines

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
Depth Example Use When
Flat (1 level) /blog/cold-email-tips Blog posts, articles, standalone pages
Two levels /blog/email-marketing/cold-email-tips When category is a ranking page itself
Three levels /solutions/marketing/email-automation Product 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
Do Don'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-readable Long, 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
Zone Purpose SEO Role
Primary nav Core site sections, 5-8 items max Passes equity to top-level pages
Secondary nav Sub-sections within a section Passes equity within a silo
Breadcrumbs Current location in hierarchy Equity from deep pages upward
Footer nav Secondary utility links, key service pages Sitewide links — use carefully
Contextual nav In-content links, related posts, "next step" links Most powerful equity signal
Sidebar Related content, category listing Medium 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
Type Example Use
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 URL https://example.com/guide Never 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

Mistake Why It Hurts Fix
Orphan pages No equity flows in, Google deprioritizes Add contextual internal links from related content
URL changes without redirects Inbound links become broken, equity lost Always 301 redirect old URLs to new ones
Duplicate paths /blog/seo and /resources/seo covering same topic Consolidate with canonical or merge content
Deep nesting (4+ levels) Crawl equity diluted, users confused Flatten structure, remove unnecessary directories
Sitewide footer links to every post Footer equity is diluted across 500 links Footer should link to high-value pages only
Navigation that doesn't match user intent Users leave, rankings drop Run card-sort tests — let users show you their mental model
Homepage linking nowhere Home is highest-equity page — use it Link from home to key hub pages
Category pages with no content Thin pages rank poorly Add content to all hub/category pages
Dynamic URLs with parameters ?sort=&filter= creates duplicate content Canonicalize 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 audit Structural scorecard: depth distribution, orphan count, URL pattern issues, navigation gaps + prioritized fix list
New site structure Text-based site tree (hierarchy diagram) + URL spec table with notes per section
Internal linking plan Hub-and-spoke map per topic cluster + anchor text guidelines + orphan fix list
URL redesign Before/after URL table + 301 redirect mapping + implementation checklist
Silo strategy Topic 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.
1---
2name: "site-architecture"
3description: "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)."
4license: MIT
5metadata:
6 version: 1.0.0
7 author: Alireza Rezvani
8 category: marketing
9 updated: 2026-03-06
10---
11 
12# Site Architecture & Internal Linking
13 
14You 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.
15 
16## Before Starting
17 
18**Check for context first:**
19If `.claude/product-marketing-context.md` exists, read it before asking questions.
20 
21Gather this context:
22 
23### 1. Current State
24- Do they have an existing site? (URL, CMS, sitemap.xml available?)
25- How many pages exist? Rough estimate by section.
26- What are the top-performing pages (if they know)?
27- Any known problems: orphan pages, duplicate content, poor rankings?
28 
29### 2. Goals
30- Primary business goal (lead gen, e-commerce, content authority, local search)
31- Target audience and their mental model of navigation
32- Specific SEO targets — topics or keyword clusters they want to rank for
33 
34### 3. Constraints
35- CMS capabilities (can they change URLs? Does it auto-generate certain structures?)
36- Redirect capacity (if restructuring, can they manage bulk 301s?)
37- Development resources (minor tweaks vs full migration)
38 
39---
40 
41## How This Skill Works
42 
43### Mode 1: Audit Current Architecture
44When a site exists and they need a structural assessment.
45 
461. Run `scripts/sitemap_analyzer.py` on their sitemap.xml (or paste sitemap content)
472. Review: depth distribution, URL patterns, potential orphans, duplicate paths
483. Evaluate navigation by reviewing the site manually or from their description
494. Identify the top structural problems by SEO impact
505. Deliver a prioritized audit with quick wins and structural recommendations
51 
52### Mode 2: Plan New Structure
53When building a new site or doing a full redesign/restructure.
54 
551. Map business goals to site sections
562. Design URL hierarchy (flat vs layered by content type)
573. Define content silos for topical authority
584. Plan navigation zones: primary nav, breadcrumbs, footer nav, contextual
595. Deliver site map diagram (text-based tree) + URL structure spec
60 
61### Mode 3: Internal Linking Strategy
62When the structure is fine but they need to improve link equity flow and topical signals.
63 
641. Identify hub pages (the pillar content that should rank highest)
652. Map spoke pages (supporting content that links to hubs)
663. Find orphan pages (indexed pages with no inbound internal links)
674. Identify anchor text patterns and over-optimized phrases
685. Deliver an internal linking plan: which pages link to which, with anchor text guidance
69 
70---
71 
72## URL Structure Principles
73 
74### The Core Rule: URLs are for Humans First
75 
76A 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.
77 
78### Flat vs Layered: Pick the Right Depth
79 
80| Depth | Example | Use When |
81|-------|---------|----------|
82| Flat (1 level) | `/blog/cold-email-tips` | Blog posts, articles, standalone pages |
83| Two levels | `/blog/email-marketing/cold-email-tips` | When category is a ranking page itself |
84| Three levels | `/solutions/marketing/email-automation` | Product families, nested services |
85| 4+ levels | `/a/b/c/d/page` | ❌ Avoid — dilutes crawl equity, confusing |
86 
87**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.
88 
89### URL Construction Rules
90 
91| Do | Don't |
92|----|-------|
93| `/how-to-write-cold-emails` | `/how_to_write_cold_emails` (underscores) |
94| `/pricing` | `/pricing-page` (redundant suffixes) |
95| `/blog/seo-tips-2024` | `/blog/article?id=4827` (dynamic, non-descriptive) |
96| `/services/web-design` | `/services/web-design/` (trailing slash — pick one and be consistent) |
97| `/about` | `/about-us-company-info` (keyword stuffing the URL) |
98| Short, human-readable | Long, generated, token-filled |
99 
100### Keywords in URLs
101 
102Yes — include the primary keyword. No — don't stuff 4 keywords in.
103 
104`/guides/technical-seo-audit` ✅
105`/guides/technical-seo-audit-checklist-how-to-complete-step-by-step` ❌
106 
107The keyword in the URL is a minor signal, not a major one. Don't sacrifice readability for it.
108 
109### Reference docs
110See `references/url-design-guide.md` for patterns by site type (blog, SaaS, e-commerce, local).
111 
112---
113 
114## Navigation Design
115 
116Navigation serves two masters: user experience and link equity flow. Most sites optimize for neither.
117 
118### Navigation Zones
119 
120| Zone | Purpose | SEO Role |
121|------|---------|----------|
122| Primary nav | Core site sections, 5-8 items max | Passes equity to top-level pages |
123| Secondary nav | Sub-sections within a section | Passes equity within a silo |
124| Breadcrumbs | Current location in hierarchy | Equity from deep pages upward |
125| Footer nav | Secondary utility links, key service pages | Sitewide links — use carefully |
126| Contextual nav | In-content links, related posts, "next step" links | Most powerful equity signal |
127| Sidebar | Related content, category listing | Medium equity if above fold |
128 
129### Primary Navigation Rules
130 
131- 5-8 items maximum. Cognitive load increases with every item.
132- Each nav item should link to a page you want to rank.
133- Never use nav labels like "Resources" with no landing page — it should be a real, rankable resources page.
134- Dropdown menus are fine but crawlers may not engage them deeply — critical pages need a clickable parent link.
135 
136### Breadcrumbs
137 
138Add breadcrumbs to every non-homepage page. They do three things:
1391. Show users where they are
1402. Create site-wide upward internal links to category/hub pages
1413. Enable BreadcrumbList schema for rich results in Google
142 
143Format: `Home > Category > Subcategory > Current Page`
144 
145Every breadcrumb segment should be a real, crawlable link — not just styled text.
146 
147---
148 
149## Silo Structure & Topical Authority
150 
151A 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.
152 
153### Hub-and-Spoke Model
154 
155```
156HUB: /seo/ ← Pillar page, broad topic
157 SPOKE: /seo/technical-seo/ ← Sub-topic
158 SPOKE: /seo/on-page-seo/ ← Sub-topic
159 SPOKE: /seo/link-building/ ← Sub-topic
160 SPOKE: /seo/keyword-research/ ← Sub-topic
161 └─ DEEP: /seo/keyword-research/long-tail-keywords/ ← Specific guide
162```
163 
164**Linking rules within a silo:**
165- Hub links to all spokes
166- Each spoke links back to hub
167- Spokes can link to adjacent spokes (contextually relevant)
168- Deep pages link up to their spoke + the hub
169- Cross-silo links are fine when genuinely relevant — just don't build a link for its own sake
170 
171### Building Topic Clusters
172 
1731. Identify your core topics (usually 3-7 for a focused site)
1742. For each topic: one pillar page (the hub) that covers it broadly
1753. Create spoke content for each major sub-question within the topic
1764. Every spoke links to the pillar with relevant anchor text
1775. The pillar links down to all spokes
1786. Build the cluster before you build the links — if you don't have the content, the links don't help
179 
180---
181 
182## Internal Linking Strategy
183 
184Internal links are the most underused SEO lever. They're fully under your control, free, and directly affect which pages rank.
185 
186### Link Equity Principles
187 
188- Google crawls your site from the homepage outward
189- Pages closer to the homepage (fewer clicks away) get more equity
190- A page with no internal links is an orphan — Google won't prioritize it
191- Anchor text matters: generic ("click here") signals nothing; descriptive ("cold email templates") signals topic relevance
192 
193### Anchor Text Rules
194 
195| Type | Example | Use |
196|------|---------|-----|
197| Exact match | "cold email templates" | Use sparingly — 1-2x per page, looks natural |
198| Partial match | "writing effective cold emails" | Primary approach — most internal links |
199| Branded | "our email guide" | Fine, not the most powerful |
200| Generic | "click here", "learn more" | Avoid — wastes the signal |
201| Naked URL | `https://example.com/guide` | Never use for internal links |
202 
203### Finding and Fixing Orphan Pages
204 
205An orphan page is indexed but has no inbound internal links. It's invisible to the site's link graph.
206 
207How to find them:
2081. Export all indexed URLs (from GSC, Screaming Frog, or `sitemap_analyzer.py`)
2092. Export all internal links on the site
2103. Pages that appear in set A but not set B are orphans
2114. Or: run `scripts/sitemap_analyzer.py` which flags potential orphan candidates
212 
213How to fix them:
214- Add contextual links from relevant existing pages
215- Add them to relevant hub pages
216- If they truly have no home, consider whether they should exist at all
217 
218### The Linking Priority Stack
219 
220Not all internal links are equal. From most to least powerful:
221 
2221. **In-content links** — within the body copy of a relevant page. Most natural, most powerful.
2232. **Hub page links** — the pillar page linking to all its spokes. High equity because pillar pages are linked from everywhere.
2243. **Navigation links** — sitewide, consistent, but diluted by their ubiquity.
2254. **Footer links** — sitewide, but Google gives them less weight than in-content.
2265. **Sidebar links** — OK but often not in the main content flow.
227 
228See `references/internal-linking-playbook.md` for patterns and scripts.
229 
230---
231 
232## Common Architecture Mistakes
233 
234| Mistake | Why It Hurts | Fix |
235|---------|-------------|-----|
236| Orphan pages | No equity flows in, Google deprioritizes | Add contextual internal links from related content |
237| URL changes without redirects | Inbound links become broken, equity lost | Always 301 redirect old URLs to new ones |
238| Duplicate paths | `/blog/seo` and `/resources/seo` covering same topic | Consolidate with canonical or merge content |
239| Deep nesting (4+ levels) | Crawl equity diluted, users confused | Flatten structure, remove unnecessary directories |
240| Sitewide footer links to every post | Footer equity is diluted across 500 links | Footer should link to high-value pages only |
241| Navigation that doesn't match user intent | Users leave, rankings drop | Run card-sort tests — let users show you their mental model |
242| Homepage linking nowhere | Home is highest-equity page — use it | Link from home to key hub pages |
243| Category pages with no content | Thin pages rank poorly | Add content to all hub/category pages |
244| Dynamic URLs with parameters | `?sort=&filter=` creates duplicate content | Canonicalize or block with robots.txt |
245 
246---
247 
248## Proactive Triggers
249 
250Surface these without being asked:
251 
252- **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.
253- **Category/hub page has thin or no content** → hub pages without real content don't rank. Flag and recommend adding a proper pillar page.
254- **Internal links using generic anchor text ("click here", "read more")** → wasted signal. Offer to rewrite anchor text patterns.
255- **No breadcrumbs on deep pages** → missing upward equity links and BreadcrumbList schema opportunity.
256- **Sitemap includes noindex pages** → sitemap should only contain pages you want indexed. Flag and offer to filter.
257- **Primary nav links to utility pages (contact, privacy)** → pushing equity to low-value pages. Nav should prioritize money/content pages.
258 
259---
260 
261## Output Artifacts
262 
263| When you ask for... | You get... |
264|---------------------|------------|
265| Architecture audit | Structural scorecard: depth distribution, orphan count, URL pattern issues, navigation gaps + prioritized fix list |
266| New site structure | Text-based site tree (hierarchy diagram) + URL spec table with notes per section |
267| Internal linking plan | Hub-and-spoke map per topic cluster + anchor text guidelines + orphan fix list |
268| URL redesign | Before/after URL table + 301 redirect mapping + implementation checklist |
269| Silo strategy | Topic cluster map per business goal + content gap analysis + pillar page brief |
270 
271---
272 
273## Communication
274 
275All output follows the structured communication standard:
276- **Bottom line first** — answer before explanation
277- **What + Why + How** — every finding has all three
278- **Actions have owners and deadlines** — no "we should consider"
279- **Confidence tagging** — 🟢 verified / 🟡 medium / 🔴 assumed
280 
281---
282 
283## Related Skills
284 
285- **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.
286- **schema-markup**: For structured data implementation. Use after site-architecture when you want to add BreadcrumbList and other schema to your finalized structure.
287- **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.
288- **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.
289- **seo-audit**: For identifying technical issues. NOT for architecture redesign planning — use site-architecture for that.
290 
View all files on GitHub →

Details

Updated
Aug 30, 2026
License
MIT
Stars on the repo
★ 26,349
Checked
Source
alirezarezvani/claude-skills ↗
Creator
alirezarezvani · 363 listings
View creator

Similar skills

See all →
SkillThe Lighthouse Agentic Browsing fractionAgentic Browsing ReadinessAgriciDaniel/claude-seo · by AgriciDanielAudit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).★ 17.4k GitHub starsSkillReferring domains, anchor text distributionBacklink Profile AnalysisAgriciDaniel/claude-seo · by AgriciDanielBacklink profile analysis: referring domains, anchor text distribution, toxic link detection, competitor gap analysis. Works with free APIs (Moz, Bing Webmaster, Common Crawl) and DataForSEO extension. Use when user says backlinks, link profile, referring domains, anchor text, toxic links, link gap, link building, disavow, or backlink audit.★ 17.4k GitHub starsSkillConnect a CMS to notfair SEO tools/setup-cmsnowork-studio/notfair-plugin · by nowork-studioConnect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my CMS", "set up WordPress", "configure Strapi", "add Contentful", "connect Ghost", or "CMS setup". Also trigger if the user asks why no CMS data appears in a seo-analysis report.★ 3.9k GitHub starsSkillBacklink profile for any domainBacklink checkRyze-AI-Adgent/open-seo-mcp-skills · by Ryze-AI-AdgentBacklink profile for any domain — referring domains, authority, anchors, new/lost links, and a side-by-side vs a competitor. Use when asked "check my backlinks", "backlink profile of X", "who links to them", or "link gap vs competitor".★ 3.1k GitHub starsSkillOptimize Core Web Vitals for better page experienceCore Web Vitals optimizationaddyosmani/web-quality-skills · by addyosmaniOptimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".★ 2.8k GitHub starsSkillRun an SEO page observation-action-review loopRun the SEO page looptsingyuai/growth-lab · by tsingyuaiRun an SEO page observation-action-review loop with persistent Memory by coordinating demand research, page creation, adversarial review, image generation, IndexNow submission, and performance review. Use when taking an SEO page from opportunity discovery through publication, measurement, iteration, or continuing a previous SEO loop from Memory.★ 2k GitHub stars

More from alirezarezvani

SkillResume a paused experiment/ar:ar-resume — Resume Experimentalirezarezvani/claude-skills · by alirezarezvaniResume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment.★ 26.3k GitHub starsSkillShow experiment dashboard with results, active loops/ar:ar-status — Experiment Dashboardalirezarezvani/claude-skills · by alirezarezvaniShow experiment dashboard with results, active loops, and progress. Use when the user runs /ar:ar-status or asks how an autoresearch experiment is going.★ 26.3k GitHub starsSkillStart an autonomous experiment loop with user-selected/ar:loop — Autonomous Experiment Loopalirezarezvani/claude-skills · by alirezarezvaniStart an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.★ 26.3k GitHub starsSkillRun a single experiment iteration/ar:run — Single Experiment Iterationalirezarezvani/claude-skills · by alirezarezvaniRun a single experiment iteration. Edit the target file, evaluate, keep or discard. Use when the user runs /ar:run or asks for one manual autoresearch iteration.★ 26.3k GitHub starsSkillSet up a new autoresearch experiment interactively/ar:setup — Create New Experimentalirezarezvani/claude-skills · by alirezarezvaniSet up a new autoresearch experiment interactively. Collects domain, target file, eval command, metric, direction, and evaluator. Use when the user runs /ar:setup or asks to start optimizing a file with the autoresearch loop.★ 26.3k GitHub starsSkill/cs:boardroom <brief/cs:boardroom — Multi-Role Boardroom Deliberationalirezarezvani/claude-skills · by alirezarezvani/cs:boardroom <brief> — 6-phase multi-role deliberation across the C-suite with Phase 2 isolation, critic pre-screen, and synthesis. Outputs a board memo. Use when a decision spans multiple executive domains — e.g. a pricing change touching finance, positioning, and product, or a raise-vs-cut runway call.★ 26.3k GitHub stars