Domain Architecture
Choose subfolder vs subdomain vs separate domains when you run multiple products or brands under one portfolio.
Overview
Domain Architecture is an agent skill most often used in Validate (also Idea research, Launch seo, Build integrations) that guides subfolder vs subdomain vs independent-domain decisions for multi-product brands.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill domain-architectureWhat is this skill?
- Compares subfolder (subdirectory), subdomain, and independent domain options
- Maps Branded House vs House of Brands and hub-spoke multi-domain patterns
- Initial assessment: product count, audience overlap, SEO goals, and migration appetite
- Cross-links domain-selection, website-structure, rebranding-strategy, and multi-domain-brand-seo
- Reads project context for product portfolio and growth goals when present
Adoption & trust: 730 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are adding another product or brand and do not know whether to use a subfolder, subdomain, or a new domain without breaking SEO or brand clarity.
Who is it for?
Indie founders planning a second SaaS, tool suite, or content property who need a clear URL and brand hierarchy before build.
Skip if: Pickling a first domain name only—use domain-selection; or single-site nav without multi-product concerns—use website-structure.
When should I use this skill?
User wants domain structure for multiple products or brands; or mentions subfolder vs subdomain, multiple websites, brand architecture, hub-spoke domain, or domain structure.
What do I get? / Deliverables
You leave with a documented domain-structure recommendation aligned to brand architecture and pointers to website-structure or multi-domain-brand-seo for the next step.
- Domain-structure recommendation (subfolder, subdomain, or separate domain)
- Brand-architecture framing (branded house vs house of brands)
- Pointers to follow-on skills for IA, migration, or brand SERP
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Domain architecture is a scope decision before you commit to URLs, SEO equity, and brand hierarchy—canonical Validate shelf. Scope covers how many products, how they relate, and what web presence shape you will build next.
Where it fits
Compare whether a new AI side project should live on the main domain or spin out before you buy hosting.
Lock subfolder vs subdomain before prototyping docs and app URLs for two related tools.
Plan hub-spoke linking so brand searches and product keywords do not cannibalize each other at go-live.
Align cookie domains and SSO return URLs with the chosen subdomain split.
How it compares
Strategic URL and brand-structure planning, not DNS/terraform provisioning or single-page copy generation.
Common Questions / FAQ
Who is domain-architecture for?
Solo builders and small teams with multiple products or brands deciding how those properties should live on the web for SEO and positioning.
When should I use domain-architecture?
When discussing subfolder vs subdomain, multiple products domain, brand architecture, hub-spoke domain, or where to host a product—during Validate scoping, Idea portfolio research, before Launch SEO splits, or when planning Build integrations across sites.
Is domain-architecture safe to install?
It provides decision frameworks only; review the Security Audits panel on this page and involve DNS/hosting providers before cutovers.
SKILL.md
READMESKILL.md - Domain Architecture
# 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 **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product portfolio and growth goals. 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 | Structure | Example | SEO Authority | Brand Independence | Typical Use | |-----------|---------|---------------|-------------------|-------------| | **Subfolder** | company.com/product-a | Shared with main domain | Low | Products under one brand; SMB; content consolidation | | **Subdomain** | product.company.com | Treated separately by Google | Medium | Separate product experience; tech isolation; support/docs | | **Independent domain** | product.ai | None shared | High | Acquired brands; different markets; distinct brand identity | ### When to Use Each | Choose | When | |--------|------| | **Subfolder** | Products share value proposition; want to strengthen main domain; SMB; blog, tools, features under one brand | | **Subdomain** | Need separate tech stack (e.g., app vs marketing); support portal; docs; distinct UX but same brand | | **Independent domain** | House 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 | Model | Description | Domain Tendency | Examples | |-------|-------------|-----------------|----------| | **Branded House** | One master brand; products use functional descriptors | Subfolder or subdomain | Google (google.com/search, google.com/maps), FedEx | | **House of Brands** | Each brand independent; parent hidden | Independent domains | Unilever (dove.com, axe.com) | | **Sub-brands / Endorsed** | Sub-brands with parent endorsement | Subdomain or independent | FedEx 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: | Role | Domain | Focus | |------|--------|-------| | **Hub** | company.com | Brand, About, Research, product matrix; brand queries | | **Spoke** | product.ai | Product 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