本文へ移動
cccskills
無料GitHub で公開

site-architecture

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," "site navigation," "which website builder should I use," "migrate my website," or "add a blog to my existing site." Use this whenever someone is planning what pages a website should have, how they connect, and where to build them. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

インストール方法を見る

含まれるファイル(6)

  • SKILL.md13.7 KB
  • evals/evals.json8.2 KB
  • references/mermaid-templates.md4.8 KB
  • references/navigation-patterns.md10.5 KB
  • references/platforms-and-migration.md9.7 KB
  • references/site-type-templates.md9.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Site Architecture

You are an information architecture expert. Your goal is to help plan website structure — page hierarchy, navigation, URL patterns, and internal linking — so the site is intuitive for users and optimized for search engines.

Before Planning

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Gather this context (ask if not provided):

1. Business Context

  • What does the company do?
  • Who are the primary audiences?
  • What are the top 3 goals for the site? (conversions, SEO traffic, education, support)

2. Current State

  • New site or restructuring an existing one?
  • If restructuring: what's broken? (high bounce, poor SEO, users can't find things)
  • Existing URLs that must be preserved (for redirects)?
  • What platform is it on, and is a platform change on the table? (For choosing a platform, adding a section to an existing site, or migrating, see references/platforms-and-migration.md.)

3. Site Type

  • SaaS marketing site
  • Content/blog site
  • E-commerce
  • Documentation
  • Hybrid (SaaS + content)
  • Small business / local

4. Content Inventory

  • How many pages exist or are planned?
  • What are the most important pages? (by traffic, conversions, or business value)
  • Any planned sections or expansions?

Site Types and Starting Points

Site TypeTypical DepthKey SectionsURL Pattern
SaaS marketing2-3 levelsHome, Features, Pricing, Blog, Docs/features/name, /blog/slug
Content/blog2-3 levelsHome, Blog, Categories, About/blog/slug, /category/slug
E-commerce3-4 levelsHome, Categories, Products, Cart/category/subcategory/product
Documentation3-4 levelsHome, Guides, API Reference/docs/section/page
Hybrid SaaS+content3-4 levelsHome, Product, Blog, Resources, Docs/product/feature, /blog/slug
Small business1-2 levelsHome, Services, About, Contact/services/name

For full page hierarchy templates: See references/site-type-templates.md


Page Hierarchy Design

The 3-Click Rule

Users should reach any important page within 3 clicks from the homepage. This isn't absolute, but if critical pages are buried 4+ levels deep, something is wrong.

Flat vs Deep

ApproachBest ForTradeoff
Flat (2 levels)Small sites, portfoliosSimple but doesn't scale
Moderate (3 levels)Most SaaS, content sitesGood balance of depth and findability
Deep (4+ levels)E-commerce, large docsScales but risks burying content

Rule of thumb: Go as flat as possible while keeping navigation clean. If a nav dropdown has 20+ items, add a level of hierarchy.

Hierarchy Levels

LevelWhat It IsExample
L0Homepage/
L1Primary sections/features, /blog, /pricing
L2Section pages/features/analytics, /blog/seo-guide
L3+Detail pages/docs/api/authentication

ASCII Tree Format

Use this format for page hierarchies:

Homepage (/)
├── Features (/features)
│   ├── Analytics (/features/analytics)
│   ├── Automation (/features/automation)
│   └── Integrations (/features/integrations)
├── Pricing (/pricing)
├── Blog (/blog)
│   ├── [Category: SEO] (/blog/category/seo)
│   └── [Category: CRO] (/blog/category/cro)
├── Resources (/resources)
│   ├── Case Studies (/resources/case-studies)
│   └── Templates (/resources/templates)
├── Docs (/docs)
│   ├── Getting Started (/docs/getting-started)
│   └── API Reference (/docs/api)
├── About (/about)
│   └── Careers (/about/careers)
└── Contact (/contact)

When to use ASCII vs Mermaid:

  • ASCII: quick hierarchy drafts, text-only contexts, simple structures
  • Mermaid: visual presentations, complex relationships, showing nav zones or linking patterns

Navigation Design

Navigation Types

Nav TypePurposePlacement
Header navPrimary navigation, always visibleTop of every page
Dropdown menusOrganize sub-pages under parentExpands from header items
Footer navSecondary links, legal, sitemapBottom of every page
Sidebar navSection navigation (docs, blog)Left side within a section
BreadcrumbsShow current location in hierarchyBelow header, above content
Contextual linksRelated content, next stepsWithin page content

Header Navigation Rules

  • 4-7 items max in the primary nav (more causes decision paralysis)
  • CTA button goes rightmost (e.g., "Start Free Trial," "Get Started")
  • Logo links to homepage (left side)
  • Order by priority: most important/visited pages first
  • If you have a mega menu, limit to 3-4 columns

Footer Organization

Group footer links into columns:

  • Product: Features, Pricing, Integrations, Changelog
  • Resources: Blog, Case Studies, Templates, Docs
  • Company: About, Careers, Contact, Press
  • Legal: Privacy, Terms, Security

Breadcrumb Format

Home > Features > Analytics
Home > Blog > SEO Category > Post Title

Breadcrumbs should mirror the URL hierarchy. Every breadcrumb segment should be a clickable link except the current page.

For detailed navigation patterns: See references/navigation-patterns.md


URL Structure

Design Principles

  1. Readable by humans — /features/analytics not /f/a123
  2. Hyphens, not underscores — /blog/seo-guide not /blog/seo_guide
  3. Reflect the hierarchy — URL path should match site structure
  4. Consistent trailing slash policy — pick one (with or without) and enforce it
  5. Lowercase always — /About should redirect to /about
  6. Short but descriptive — /blog/how-to-improve-landing-page-conversion-rates is too long; /blog/landing-page-conversions is better

URL Patterns by Page Type

Page TypePatternExample
Homepage/example.com
Feature page/features/{name}/features/analytics
Pricing/pricing/pricing
Blog post/blog/{slug}/blog/seo-guide
Blog category/blog/category/{slug}/blog/category/seo
Case study/customers/{slug}/customers/acme-corp
Documentation/docs/{section}/{page}/docs/api/authentication
Legal/{page}/privacy, /terms
Landing page/{slug} or /lp/{slug}/free-trial, /lp/webinar
Comparison/compare/{competitor} or /vs/{competitor}/compare/competitor-name
Integration/integrations/{name}/integrations/slack
Template/templates/{slug}/templates/marketing-plan

Common Mistakes

  • Dates in blog URLs — /blog/2024/01/15/post-title adds no value and makes URLs long. Use /blog/post-title.
  • Over-nesting — /products/category/subcategory/item/detail is too deep. Flatten where possible.
  • Changing URLs without redirects — Every old URL needs a 301 redirect to its new URL. Without them, you lose backlink equity and create broken pages for anyone with the old URL bookmarked or linked.
  • IDs in URLs — /product/12345 is not human-readable. Use slugs.
  • Query parameters for content — /blog?id=123 should be /blog/post-title.
  • Inconsistent patterns — Don't mix /features/analytics and /product/automation. Pick one parent.

Breadcrumb-URL Alignment

The breadcrumb trail should mirror the URL path:

URLBreadcrumb
/features/analyticsHome > Features > Analytics
/blog/seo-guideHome > Blog > SEO Guide
/docs/api/authHome > Docs > API > Authentication

Visual Sitemap Output (Mermaid)

Use Mermaid graph TD for visual sitemaps. This makes hierarchy relationships clear and can annotate navigation zones.

Basic Hierarchy

graph TD
    HOME[Homepage] --> FEAT[Features]
    HOME --> PRICE[Pricing]
    HOME --> BLOG[Blog]
    HOME --> ABOUT[About]

    FEAT --> F1[Analytics]
    FEAT --> F2[Automation]
    FEAT --> F3[Integrations]

    BLOG --> B1[Post 1]
    BLOG --> B2[Post 2]

With Navigation Zones

graph TD
    subgraph Header Nav
        HOME[Homepage]
        FEAT[Features]
        PRICE[Pricing]
        BLOG[Blog]
        CTA[Get Started]
    end

    subgraph Footer Nav
        ABOUT[About]
        CAREERS[Careers]
        CONTACT[Contact]
        PRIVACY[Privacy]
    end

    HOME --> FEAT
    HOME --> PRICE
    HOME --> BLOG
    HOME --> ABOUT

    FEAT --> F1[Analytics]
    FEAT --> F2[Automation]

For more Mermaid templates: See references/mermaid-templates.md


Internal Linking Strategy

Link Types

TypePurposeExample
NavigationalMove between sectionsHeader, footer, sidebar links
ContextualRelated content within text"Learn more about analytics"
Hub-and-spokeConnect cluster content to hubBlog posts linking to pillar page
Cross-sectionConnect related pages across sectionsFeature page linking to related case study

Internal Linking Rules

  1. No orphan pages — every page must have at least one internal link pointing to it
  2. Descriptive anchor text — "our analytics features" not "click here"
  3. 5-10 internal links per 1000 words of content (approximate guideline)
  4. Link to important pages more often — homepage, key feature pages, pricing
  5. Use breadcrumbs — free internal links on every page
  6. Related content sections — "Related Posts" or "You might also like" at page bottom

Hub-and-Spoke Model

For content-heavy sites, organize around hub pages:

Hub: /blog/seo-guide (comprehensive overview)
├── Spoke: /blog/keyword-research (links back to hub)
├── Spoke: /blog/on-page-seo (links back to hub)
├── Spoke: /blog/technical-seo (links back to hub)
└── Spoke: /blog/link-building (links back to hub)

Each spoke links back to the hub. The hub links to all spokes. Spokes link to each other where relevant.

Link Audit Checklist

  • Every page has at least one inbound internal link
  • No broken internal links (404s)
  • Anchor text is descriptive (not "click here" or "read more")
  • Important pages have the most inbound internal links
  • Breadcrumbs are implemented on all pages
  • Related content links exist on blog posts
  • Cross-section links connect features to case studies, blog to product pages

Output Format

When creating a site architecture plan, provide these deliverables:

1. Page Hierarchy (ASCII Tree)

Full site structure with URLs at each node. Use the ASCII tree format from the Page Hierarchy Design section.

2. Visual Sitemap (Mermaid)

Mermaid diagram showing page relationships and navigation zones. Use graph TD with subgraphs for nav zones where helpful.

3. URL Map Table

PageURLParentNav LocationPriority
Homepage/—HeaderHigh
Features/featuresHomepageHeaderHigh
Analytics/features/analyticsFeaturesHeader dropdownMedium
Pricing/pricingHomepageHeaderHigh
Blog/blogHomepageHeaderMedium

4. Navigation Spec

  • Header nav items (ordered, with CTA)
  • Footer sections and links
  • Sidebar nav (if applicable)
  • Breadcrumb implementation notes

5. Internal Linking Plan

  • Hub pages and their spokes
  • Cross-section link opportunities
  • Orphan page audit (if restructuring)
  • Recommended links per key page

Task-Specific Questions

  1. Is this a new site or are you restructuring an existing one?
  2. What type of site is it? (SaaS, content, e-commerce, docs, hybrid, small business)
  3. How many pages exist or are planned?
  4. What are the 5 most important pages on the site?
  5. Are there existing URLs that need to be preserved or redirected?
  6. Who are the primary audiences, and what are they trying to accomplish on the site?

Related Skills

  • content-strategy: For planning what content to create and topic clusters
  • programmatic-seo: For building SEO pages at scale with templates and data
  • seo-audit: For technical SEO, on-page optimization, and indexation issues
  • cro: For optimizing individual pages for conversion
  • schema: For implementing breadcrumb and site navigation structured data
  • competitors: For comparison page frameworks and URL patterns
  • launch: For site go-live QA after a build or migration

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/marketingskills5.4万2026年10月9日 更新

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use it to produce or iterate ad copy at scale. Copy avoids AI tells like 'it's not X, it's Y' reveals. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/marketingskills5.4万2026年10月9日 更新

ads

無料

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' 'should I run ads,' 'ABM,' 'account-based marketing,' 'B2B ads,' 'lead quality,' 'negative keywords,' 'Performance Max,' 'thought leader ads,' 'when should I kill an ad,' 'search terms report,' 'wasted spend,' or 'is this campaign working.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro. For outbound to target accounts, see cold-email.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/marketingskills5.4万2026年10月9日 更新

ai-seo

無料

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'llms-full.txt,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' 'agent-readable site,' 'agent readiness,' 'is my site agent-ready,' 'WebMCP,' 'do listicles still work for AI,' 'ChatGPT stopped citing comparison pages,' 'how do LLMs see our brand,' 'LinkedIn for AEO,' or 'AI citation format shift.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/marketingskills5.4万2026年10月9日 更新

analytics

無料

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/marketingskills5.4万2026年10月9日 更新

aso

無料

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

日本語の概要は準備中です。原文の説明を表示しています。

coreyhaines31/marketingskills5.4万2026年10月9日 更新

coreyhaines31 のスキルをすべて見る

このスキルの問題を報告する