Domain Name Style Guide: Consistency for Brand & UX
Codify how your organization evaluates, formats, and deploys domain names for products, campaigns, and internal tools.
By Brand Ops•8/6/2025•2 min read
stylebrandinggovernance
Domain Name Style Guide: Consistency for Brand & UX
Unstructured domain choices create brand drift and operational friction. Standardize early.
Naming Principles
- Human pronounceable
- Avoid ambiguous character pairs (1/l, 0/O)
- Prefer shorter; descriptive only when needed
- No hyphens unless keyword clarity gain > 2 "readability points"
Structural Conventions
Use Case | Pattern | Example |
---|---|---|
Marketing campaign | campaign-YYYY-short | launch-2025-beta.example.com |
Internal tool | tool.function | status.api.example.com |
Regional site | region code | de.example.com |
Environment | env prefix | staging.example.com |
TLD Policy
- Primary brand: .com
- Innovation / AI product lines: .ai allowed
- Country-specific launches: matching ccTLD if ≥ 15% revenue forecast
- Blocklist: .zip, .mov (phishing risk) unless exception granted
Subdomain Depth
Limit to 3 labels unless documented exception. More layers degrade trust & performance.
Approval Workflow
- Request via naming form (business purpose, lifespan)
- Review by Brand + Security
- SLA: 2 business days
- Log to central registry
Central Registry Fields
DomainEntry {
id, fqdn, ownerTeam, purpose, environment, createdAt,
reviewDate, status: [active, sunset_planned, deprecated],
linkedServices: [...], dnsProvider
}
Sunset Process
- Identify zero traffic / unused campaigns quarterly
- Schedule 301 or decom depending on inbound links
- Archive DNS record diff
Common Anti-Patterns
Pattern | Why Avoid |
---|---|
Random subdomain experiments | Sprawl, security blind spots |
Overusing vanity TLDs | Dilutes brand consistency |
Hyphen-chaining | Lowers memorability |
Need an internal registry schema or form component? Let’s add it.