Use the root domain
Keep marketing pages, solution pages, and indexable guides on the main domain so authority compounds in one place.
Architecture Guide
Design sub apps so they help the main site instead of fragmenting it.
The fastest way to lose momentum with a new domain is to scatter your best pages across disconnected properties. Treat the root site as the authority hub, then give a workflow its own app surface only when the product boundary is real.
Pick the URL model based on product boundaries, not convenience.
Use subdirectories
Choose subdirectories for public-facing product surfaces that share the same brand, navigation, and content strategy.
Use subdomains carefully
Reserve subdomains for apps that need separate authentication, infrastructure, or release cycles.
Guardrails for indexable workflow pages
- Give every public page a distinct title, description, and canonical URL.
- Link each sub app from a relevant root-domain page, not just the global nav.
- Keep public guide pages crawlable even if the actual app requires login.
- Publish a sitemap entry for every public launch page and solution page.
- Do not hide important pages behind client-only rendering without crawlable HTML.
What should stay on the root site
- Core positioning and category pages
- Use-case pages that answer real search queries
- Launch guides, integration pages, and case studies
- Public documentation that can earn links and rankings
Recommended default for Takyon
Keep takyon.app as the primary brand and discovery hub. If a workflow needs its own app later, publish a public explanation page on the root domain and link into the live app from there. That keeps your main site useful to both users and search engines.