Skip to content
Agentmart
Submit a tool

domain-architecture

When the user wants to decide domain structure for multiple products or brands—subfolder vs subdomain vs independent domain.

Skill by kostja94

IndexedMIT★ 1,061
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/kostja94-domain-architecture

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

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.

Use cases: design, marketing

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md and code. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/domain-architecture

What's inside

Skill 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.
License
MIT
Metadata
version: 1.0.1
Instructions
75 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# 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

| 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

From kostja94/marketing-skills, MIT.

More from kostja94/marketing-skills

Signals

Stars
1,061
Forks
150
Open issues
3
Last commit (this folder)
Sep 25, 2026 (1 month ago)
Last release
Mar 11, 2026 (7 months ago)

From GitHub (fetched Oct 24, 2026).

Details

Version
1.0.1
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

Same skill elsewhere

Copies of this SKILL.md published by others; search shows only one of them.

More from kostja94

Cite this page

domain-architecture skill. Agent Mart. https://agentmart.dev/skills/kostja94-domain-architecture (last updated 2026-10-24)