One Domain, Many Businesses: Structuring a Personal Brand Ecosystem

If you only do one thing, this is easy. Put it on your domain and move on.

The moment you run two things, you have an architecture decision. And most people make it accidentally — they register a new domain because it felt like the obvious move, and end up starting from zero on a second site while their first one had authority they could have shared.

I run a development practice, a barbering business, and a podcast. They live at ericjokl.com, barber.ericjokl.com, and podcast.ericjokl.com. That was a deliberate choice, and here is the reasoning behind it.

The three options

Subfolder. yourdomain.com/podcast. The new thing lives inside the existing site.

Subdomain. podcast.yourdomain.com. The new thing gets its own site under the same registered domain.

Separate domain. yourpodcast.com. The new thing is fully independent.

The SEO folklore says subfolders always win because they inherit the parent domain's authority most directly. That is roughly true and badly oversimplified, because it treats SEO as the only variable. It is not even the most important one.

Ask the audience question first

The real question is not technical. It is: do these two things share an audience?

If someone interested in thing A is plausibly interested in thing B, they belong together. A blog about web development and a services page for web development share an audience completely — those are subfolders, no debate.

If the audiences are unrelated, forcing them into one site makes both worse. Somebody booking a haircut does not want to scroll past a case study about conversion rates. Somebody evaluating me for a development contract does not need a price list for fades. Same person running both, entirely different visitors.

That is what subdomains are for: shared identity, separate experience.

What a subdomain actually costs and gives

The honest accounting.

It gets its own site. Own navigation, own design language if it needs one, own information architecture. This is the whole point. The barbering site is structured around booking. The portfolio is structured around evaluation. Those are different site shapes.

It is treated as a mostly separate property by search engines. This is the cost. Authority does flow between subdomains, but not as directly as within a single site. A new subdomain does not launch with the full weight of the parent domain behind it.

It keeps the brand together. Every visitor sees the same root domain. Someone who finds the podcast learns my name. Someone who finds the barbering business sees I also build software. That association is worth real money over time and it is the thing a separate domain throws away.

It is administratively cleaner. One registration, one renewal, one DNS zone, one set of certificates. This sounds minor until you are three properties in and one of them expires because it renewed to an old card.

When a separate domain is actually right

Two cases.

When the venture has to stand alone. If you are building something you might sell, raise money for, or hand to a partner, tying it to your personal domain creates a problem later. A business that needs its own identity should have its own domain from day one.

When association would hurt. If the two things genuinely do not belong to the same reputation, separate them. This is rare and people over-apply it, but it exists.

Everything else is usually better off on a subdomain.

Making a multi-property setup actually work

Here is where most people who choose subdomains leave value on the table. They set up the subdomain, launch the site, and never connect the properties.

Three things hold the ecosystem together.

Real, crawlable links in both directions. Every property links back to the main domain. The main domain links out to every property, from the footer of every page — not from one buried page. These are ordinary anchor tags, present in the server-rendered HTML.

This matters more than people realise, because a sitemap can only list URLs on its own host. Your main site's sitemap cannot include your subdomain's pages. Links are the discovery mechanism. If the only reference to your podcast subdomain is a button rendered by JavaScript after hydration, you have made it harder to find than it needs to be.

A hub page that explains the relationship. One page on the main domain that lists every property, says what each one is, and links to it. This does three jobs: it gives visitors a map, it gives crawlers a dense set of links in a relevant context, and it gives you a single page to point at when someone asks what you do.

Structured data that names the entity. In your schema markup, put every property in the sameAs array of your Person or Organization node. This is the explicit machine-readable statement that these hosts are the same entity. It is one array. Almost nobody fills it in properly.

Give people a short path

A small thing that pays off constantly: set up redirects on the main domain for the short paths people will guess.

yourdomain.com/podcast redirects to podcast.yourdomain.com. yourdomain.com/barber redirects to barber.yourdomain.com.

Now you have one thing to say out loud. On a call, in a video, on a business card, the short path works and you never have to explain a subdomain to somebody who does not know what one is.

Each property still has to earn its own traffic

The part people skip: a subdomain does not inherit rankings. It inherits association.

Each property needs its own content, its own reason to exist in search results, and its own internal structure. The podcast site needs episode pages. The barbering site needs service pages and a location page. Launching a subdomain and expecting the parent domain to carry it is the most common way this setup disappoints people.

What the shared root domain gives you is a head start on trust and a compounding brand — not a free pass on the work.

The rule I use

Same audience, same site. Put it in a folder.

Same person, different audience. Put it on a subdomain, and link it properly.

Different reputation, or built to stand alone. Give it its own domain.

The wrong answer is the accidental one: a scatter of unconnected domains that each start from nothing, sharing an owner but never sharing the benefit.