domain-architecture

$npx mdskill add kostja94/marketing-skills/domain-architecture

Decides domain structure for multiple products or brands.

  • Solves whether to use subfolder, subdomain, or independent domain.
  • Depends on project context files and brand architecture models.
  • Evaluates product count, brand strategy, and growth goals.
  • Delivers a structured recommendation with rationale.

SKILL.md

.github/skills/domain-architectureView on GitHub ↗
---
name: domain-architecture
description: 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.
metadata:
  version: 1.0.1
---

# 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 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

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
affiliate-marketingWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generatorWhen the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-trackingWhen the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
alternatives-page-generatorWhen the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.