Domain Architecture
- 757 installs
- 787 repo stars
- Updated June 9, 2026
- kostja94/marketing-skills
domain-architecture is a marketing strategy skill that compares subfolder, subdomain, and separate-domain setups for developers who run multiple products or brands under one web presence.
About
domain-architecture is a Claude Code skill from kostja94/marketing-skills at version 1.0.1 that guides subfolder versus subdomain versus independent-domain decisions for multi-product or multi-brand sites. The skill walks through branded-house and house-of-brands patterns, hub-spoke routing, and SEO tradeoffs so developers pick a URL structure before building or migrating properties. Developers reach for domain-architecture when launching a second product, splitting brands, or debating whether docs, apps, and marketing should share a root domain. It pairs conceptually with multi-domain-brand-seo for SERP-focused follow-up work.
- Guides subfolder vs subdomain vs independent domain decisions
- Evaluates Branded House versus House of Brands architecture
- Applies Hub-Spoke principles for coexisting domains
- Reads project-context.md to incorporate portfolio and growth goals
- References related skills including domain-selection, website-structure, rebranding-strategy and multi-domain-brand-seo
Domain Architecture by the numbers
- 757 all-time installs (skills.sh)
- +6 installs in the week ending Jul 25, 2026 (Skillselion tracking)
- Ranked #614 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kostja94/marketing-skills --skill domain-architectureAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 757 |
|---|---|
| repo stars | ★ 787 |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 9, 2026 |
| Repository | kostja94/marketing-skills ↗ |
Subfolder vs subdomain vs separate domain for products?
Decide whether to organize multiple products or brands using subfolders, subdomains, or separate domains.
Who is it for?
Developers planning URL structure for multiple SaaS products, sub-brands, or regional sites who need an SEO-aware architecture decision before implementation.
Skip if: Teams that already finalized DNS and routing who only need CDN, TLS, or infrastructure configuration without SEO structure changes.
When should I use this skill?
The user mentions subfolder vs subdomain, multiple products on one domain, brand architecture, hub-spoke domains, or where to host a new product.
What you get
A documented domain-structure recommendation covering subfolder, subdomain, or independent-domain choice with brand-architecture rationale.
- Domain structure recommendation
- Brand architecture rationale
By the numbers
- Skill metadata version 1.0.1 in kostja94/marketing-skills
Files
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
Related skills
Seo AuditRun structured SEO audits on their SaaS site or content hub and receive a prioritized action plan.173k42.2kCopywritingGenerate, rewrite, or strengthen persuasive website and landing-page copy that converts visitors into users.164k42.2k
Viral Short FormQuickly generate high-retention hooks, scripts, and outlines for TikTok, Reels, YouTube Shorts, and carousels.132k67Viral HooksWrite and critique viral hooks for short-form video opening sequences.123k67Viral Captions And CtasOptimize social media captions and CTAs for viral short-form video reach and saves.123k67Viral Youtube ShortsWrite and diagnose YouTube Shorts for Shorts Feed and long-form funnel.123k67How it compares
Use domain-architecture for structural URL and brand-architecture decisions; follow with multi-domain-brand-seo when the primary goal is brand SERP coverage.
FAQ
What domain patterns does domain-architecture compare?
domain-architecture compares subfolder (subdirectory), subdomain, and independent-domain setups for multiple products or brands. The skill frames tradeoffs across brand architecture models like branded house and house of brands.
When should developers invoke domain-architecture?
domain-architecture fits early planning when a team adds another product, brand, or regional site and must decide URL structure before DNS, routing, and content migration. It focuses on strategic structure, not CDN or certificate setup.
Is Domain Architecture safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.