Skill 詳細
site-architecture
SEO and marketing-site structure.
使用前に確認
自動レビューは関連性のみを確認し、安全性や推奨を保証しません。使用前に出典の説明を読んでください。
SKILL.md
これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。
--- 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:** 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 —GitHub で全文を読む (外部ページ)