Site Architecture

Definition

Site architecture encompasses page hierarchy structure, URL design, and internal link patterns on a website. It defines how users and search engine crawlers find and navigate information across the site.

Good architecture is designed so Google discovers and indexes all important pages, efficiently transfers authority between pages, and users reach desired information quickly.

Summary

Site architecture core principles: ①All important pages within 3–4 clicks from home → ②Logical, predictable URL hierarchy → ③Pillar–Cluster internal link structure → ④XML sitemap + breadcrumb as dual safety net. When these four are satisfied, crawl budget waste and authority dispersion are naturally prevented.

4 Site Architecture Models

1. Flat Structure

All pages sit within 1–2 clicks from home. Suitable for small sites (50 pages or fewer).

Home
├── Page A
├── Page B
└── Page C

Pros: Simple, highest crawl efficiency
Cons: Hard to build topic authority as content grows

2. Silo Structure

Content is isolated by topic category (silo). Internal links occur only within each silo.

Home
├── SEO Silo
│   ├── Keyword Research
│   └── On-Page SEO
└── AEO Silo
    ├── What is AEO?
    └── AI Optimization

Pros: Topic authority concentration, clear topic clusters
Cons: Limited connection of related content across silos

3. Pyramid Structure

Home → category → subcategory → individual page hierarchy. Common for large content sites and ecommerce.

Home
└── Category (Level 2)
    └── Subcategory (Level 3)
        └── Individual post/product (Level 4)

Pros: Suitable for large content management, logical hierarchy
Cons: Crawl budget and authority transfer efficiency decrease with depth

4. Graph/Hub Structure

Mutual linking between Pillar pages and Cluster pages. Most recommended approach in current content marketing.

Pillar: Complete SEO Guide
├── Cluster: Keyword Research Methods
├── Cluster: On-Page Optimization
├── Cluster: Link Building
└── Cluster: Technical SEO
    (all link back to Pillar)

Pros: Topic authority building, AEO-friendly, internal link authority circulation
Cons: Complex design and maintenance

5 Principles of Good Site Architecture

Principle 1: Limit Depth to 3–4 Clicks

Any important page should be reachable within 3–4 clicks from the homepage. Pages deeper than 5 clicks are hard for Googlebot to reach and receive little authority transfer.

Diagnosis: Crawl with Screaming Frog and check the "Crawl Depth" report. If depth 5+ pages are important content, structural redesign is needed.

Principle 2: Logical URL Hierarchy

URLs should reflect page location in a predictable way.

✅ Good: /seo/keyword-research/long-tail-keywords
❌ Bad: /post?id=4829&cat=12&lang=ko

URLs alone should indicate location. See URL Slug for details.

Principle 3: Consistent Internal Link Structure

Internal links determine authority flow within the site. Pillar pages should receive links from all related Clusters, and Pillars should link down to Clusters.

[FLOW_DIAGRAM: Pillar → Cluster → Pillar internal link authority circulation]

See Internal Linking for details.

Principle 4: XML Sitemap + Breadcrumb

Sitemaps tell Googlebot "these pages are important." Breadcrumbs explicitly show page hierarchy to both users and bots.

See Breadcrumb for details.

Principle 5: Prevent Duplicates with Canonical

Use canonical tags to specify canonical URLs so URL parameters, sort options, and pagination do not create duplicate URLs.

See Canonical Tag and Pagination for details.

5 Steps to Design Site Architecture

Step 1: Topic Cluster Design

Derive core topics (Pillars) and supporting content (Clusters) the site will build authority on, based on keyword research. See Keyword Mapping for details.

Step 2: Decide URL Structure

Decide subdomain vs subdirectory, category inclusion, and URL depth. See Subdomain vs Subdirectory for details.

Step 3: Navigation Design

Design global navigation (main menu), local navigation (sidebar/related posts), and breadcrumbs.

Step 4: Internal Link Plan

Create a Pillar-Cluster matrix planning which pages should link to which.

Step 5: Set Crawl Priority

Limit areas not to crawl with robots.txt and prioritize important pages in the sitemap. See Crawl Budget for details.

Site Architecture and Topic Authority

Entity Authority Concentration

When Google evaluates a site’s authority on a topic, it looks at connectivity among pages on that topic. Well-designed Pillar-Cluster structure strongly signals to Google that "this site is an expert on this topic." See Entity SEO for details.

Site Architecture in AEO

When AI answer engines query a topic, they prioritize content from sites with high topic authority. Pillar-centric architecture increases AI citation potential. See Query Fan-Out for details.

Common Site Architecture Mistakes

Error 1: Orphan Pages

Pages with no internal links. Googlebot cannot reach them without a sitemap. Discover in regular crawl audits and add internal links.

Error 2: Excessive Hierarchy Depth

URL paths with 5+ levels (/a/b/c/d/e/page). Simplify category structure or remove intermediate levels.

Error 3: Duplicate Structure

Multiple URL paths for the same content. Common on WordPress sites where tags and categories both include the same post. Resolve with canonical.

Error 4: Missing Internal Links

Publishing content without linking to it from existing content. Publishing without an internal link plan accumulates orphan pages.

Korea Market Application

Architecture Considerations in Korean CMS Platforms

WordPress: Category, tag, and archive pages auto-generate and easily create duplicate structure. noindex archive pages or apply canonical in Yoast/Rank Math.

Cafe24/Godo Mall: Ecommerce CMS filter parameters (?color=red&size=M) mass-generate duplicate URLs. Set clear URL parameter handling policy.

Imweb: Default structure is relatively simple on small sites, but hreflang handling is needed for multilingual settings.

Naver vs Google Architecture Strategy

Naver tends to evaluate individual posts directly rather than whole domains, so for Naver-centric sites individual post optimization matters more. For Google-centric sites, whole-site authority and architecture are core.

Frequently Asked Questions

Q. Will changing site architecture drop rankings?
A. Large URL structure changes can cause short-term ranking fluctuations. Always set 301 redirects, update XML sitemap, and change all internal link URLs to new URLs. Changing architecture without sufficient preparation causes serious traffic loss.

Q. How many pages before I need to think about architecture?
A. Above 50 pages, structure should be clearly designed. Sites with 10 pages or fewer are most efficient with flat structure. Once blogs exceed 100 posts, authority dispersion worsens without Pillar-Cluster structure.

Q. Can I use only tags without categories?
A. Categories create URL hierarchy for clear structure; tags mainly connect related content. If using only one, categories are more SEO-favorable. Tag archive pages often become thin content — noindex is recommended.

Q. Which is better for architecture, subdomain or subdirectory?
A. In most cases subdirectories (example.com/blog/) share domain authority and are more favorable for architecture. Subdomains (blog.example.com) are treated as separate sites and authority is split. See Subdomain vs Subdirectory for details.

Q. How should architecture be designed for single-page applications (SPA)?
A. SPAs render content with JavaScript, so Googlebot takes extra time to crawl. Use server-side rendering (SSR) or static generation (SSG) to improve crawlability; each page needs a unique URL. Manage URLs correctly with the HTML History API.

Related Sources

• Google Search Central (2024). Site structure. https://developers.google.com/search/docs/crawling-indexing/site-structure
• Moz (2024). Website Architecture and SEO. Moz Blog.
• Ahrefs (2024). Website Architecture: How to Build an SEO-Friendly Structure. Ahrefs Blog.