Domain Architecture

by kostja948dd89c57395eNo license1K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 days ago

When the user wants to decide domain structure for multiple products or brands—subfolder vs subdomain vs independent domain. Also use when the user mentions "subfolder vs subdomain," "subdirectory vs subdomain," "multiple products domain," "multiple websites," "brand architecture," "branded house," "house of brands," "where to host product," "domain structure," or "hub-spoke domain." For brand SERP, use multi-domain-brand-seo.

AI-generated overview

Guides domain structure decisions for multiple products or brands: subfolder, subdomain, or independent domain.

What it does
This skill provides a decision framework for choosing between subfolders, subdomains, and independent domains when a company has multiple products or brands. It covers brand architecture models (Branded House, House of Brands, sub-brands) and Hub-Spoke principles for companies where a main site and product sites coexist. It produces a recommendation with rationale, a brand architecture fit, a domain mapping, and Hub-Spoke guidance.
When to use it
Use it when deciding where to host a product or how to structure domains across multiple products or brands. It also fits discussions of subfolder versus subdomain, brand architecture, or hub-and-spoke domain setups.
Requirements
No scripts or special tooling. It optionally reads a root contextus.md project file when present; otherwise it works from available project material or user-provided facts.

Strategy: Domain Architecture

Guides domain structure decisions for multiple products or brands: subfolder (subdirectory), subdomain, or independent domain. Covers brand architecture (Branded House vs House of Brands) and Hub-Spoke principles when multiple domains coexist. See domain-selection for initial domain choice (Brand/PMD/EMD, TLD); website-structure for single-domain page planning; rebranding-strategy for domain change and migration; multi-domain-brand-seo for brand search optimization.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Initial Assessment

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

Identify:

  1. Product count: Single product vs multiple products/brands
  2. Brand strategy: Unified brand vs distinct brands
  3. Current state: Planning from scratch vs consolidating existing domains
  4. Constraints: Tech stack, team, budget

Domain Structure Options

StructureExampleSEO AuthorityBrand IndependenceTypical Use
Subfoldercompany.com/product-aShared with main domainLowProducts under one brand; SMB; content consolidation
Subdomainproduct.company.comTreated separately by GoogleMediumSeparate product experience; tech isolation; support/docs
Independent domainproduct.aiNone sharedHighAcquired brands; different markets; distinct brand identity

When to Use Each

ChooseWhen
SubfolderProducts share value proposition; want to strengthen main domain; SMB; blog, tools, features under one brand
SubdomainNeed separate tech stack (e.g., app vs marketing); support portal; docs; distinct UX but same brand
Independent domainHouse of Brands; acquired company; different audience; different TLD (e.g., .ai for AI product)

SEO consensus: Subfolders typically outperform subdomains for most cases—authority flows to the main domain. Subdomains require separate SEO effort.

Brand Architecture

ModelDescriptionDomain TendencyExamples
Branded HouseOne master brand; products use functional descriptorsSubfolder or subdomainGoogle (google.com/search, google.com/maps), FedEx
House of BrandsEach brand independent; parent hiddenIndependent domainsUnilever (dove.com, axe.com)
Sub-brands / EndorsedSub-brands with parent endorsementSubdomain or independentFedEx Express, Marriott Bonvoy

Decision factors: Business strategy, market positioning, product overlap, resource availability.

Hub-Spoke (Multiple Domains Coexist)

When company main site (company.com) and product site (product.ai) both exist:

RoleDomainFocus
Hubcompany.comBrand, About, Research, product matrix; brand queries
Spokeproduct.aiProduct features, pricing, signup; product queries

Principles:

  • Hub links to Spoke (Products section); Spoke links back (About, Footer, "A [Company] product")
  • Spoke avoids competing for brand queries in Title; Hub avoids competing for product keywords
  • See multi-domain-brand-seo for brand search optimization.

Output Format

  • Recommendation (subfolder / subdomain / independent) with rationale
  • Brand architecture fit (Branded House / House of Brands / Sub-brands)
  • Domain mapping (e.g., product A → company.com/product-a)
  • Hub-Spoke guidance (if multiple domains)
  • Related next steps (website-structure, rebranding-strategy)

Related Skills

  • domain-selection: Initial domain choice (Brand/PMD/EMD, TLD); single-site use case
  • website-structure: Plan pages within a domain; single-domain structure
  • rebranding-strategy: Domain change, 301 redirects, migration
  • multi-domain-brand-seo: Brand search control when Hub and Spoke coexist
  • branding: Brand strategy, positioning; domain architecture implements brand structure

Source and attribution

Source:kostja94/marketing-skillsinskills/strategies/commercial/domain/domain-architectureat commit8dd89c5

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal