# A second product: same domain, subdomain, or a new site?

A second product on your existing domain starts with everything the first one earned. A new domain starts with nothing, and needs its own links, its own brand and its own patience. Pick on operations and audience, then structure the site so neither product hides the other.

Updated 2026-09-15 · Source: https://porteur.ai/guides/seo-for-a-second-product

## The three options, and what each costs

| Option | What it starts with | What it costs |
| --- | --- | --- |
| A folder on the same domain | Every link and every signal the domain already has | The site has to explain two products without confusing either audience |
| A subdomain | Usually most of what the domain has, since Google treats it as part of the site in most cases | A second navigation, a second sitemap, and an argument every quarter about which product owns the home page |
| A separate domain | Nothing. No links, no history, no brand demand | A second site to maintain: its own links, its own content, its own months of waiting |

The default for a small company is the folder. You have one team, one brand and a finite number of hours, and a folder is the only option that does not double the work.

## What Google says, and what it does not

Google has said repeatedly that subdomains and subdirectories both work and that the choice is yours. It does not publish a transfer rate, and there is no setting that shares authority between two hosts.

- A folder is unambiguously part of the site: the same host, the same crawl, the same internal links.
- A subdomain is treated as part of the site in most cases, but it can be seen as separate, and you cannot make that call for Google.
- A separate domain is a separate site by every measure, and every signal has to be earned again.
- Nothing you put in a file changes any of this. The structure is the decision.

The detail of the subdomain question has its own guide. What matters here is the second product's audience, not the hostname.

## When a second product deserves its own domain

There are real cases. They are fewer than founders think, and they are about the business, not about ranking.

- The audiences share nothing: a developer tool and a consumer app confuse each other's visitors in one navigation.
- You intend to sell one of them, and a clean separation is part of the deal.
- The brands must not be associated, for a legal or a market reason.
- The second product is an experiment you expect to kill, and you do not want the wreckage on the main domain.
- A regulator or a partner requires a separate entity and site.

> A weak reason: wanting an exact-match domain for the new category. Google's exact match domain system stopped rewarding that, and you would be trading real links for a keyword in a hostname.

## Structuring one site that holds two products

One home page, two product hubs, and everything under the hub it belongs to. The hubs are real pages, not menus.

```text
/                      the company: what both products are, who they are for
/product-a/            the hub: what it does, for whom, its pricing link
/product-a/pricing
/product-a/guides/...
/product-b/            the same, for the second product
/product-b/pricing
/product-b/guides/...
/about  /blog  /changelog     shared, and they say which product each entry is about
```

- Each product hub carries its own title, its own description and its own Product or SoftwareApplication markup.
- Guides live under the product they serve. A guide that serves both is a company-level page, linked from both hubs.
- Breadcrumbs say which product a page belongs to, so a visitor landing from search knows where they are.
- The pricing pages are separate URLs. One pricing page for two products ranks for neither.

The home page is the hard part. It has to name both products in the first screen without becoming a list, and it will rank for the company name, not for either category.

## The navigation and internal linking that keeps both findable

The failure mode is a second product buried three clicks down, linked only from the footer, crawled rarely and ranking for nothing.

1. **Put both hubs in the main navigation** As real anchors with href attributes. A menu built from buttons and script is not a link to a crawler.
2. **Link the hub from the home page body, not only the menu** A sentence with a descriptive anchor is worth more than a nav item, and it tells the reader what the product is.
3. **Link down from each hub to its own pages** The hub is the page that distributes crawling and ranking to the product's guides and pricing.
4. **Link across only where it helps a reader** A guide in product A links to product B when the same person needs both. Cross-linking everything to everything helps nobody.
5. **Keep click depth at three or less** Home to hub to page. Pages deeper than that are crawled and recrawled less often.

## The naming problem nobody plans for

Two products under one company means three names, and search treats each as a separate entity.

- Decide the canonical spelling of each product name and use it everywhere: the site, the app, the docs, the listings, the social profiles.
- Decide whether the product is "Product A by Company" or a standalone name, and keep it consistent. Searchers will type what they saw.
- The company page carries Organization markup; each product hub carries its own product markup. One entity for the company, one per product.
- Expect the second product's brand searches to start at nothing. Launches, listings and mentions build them, not the site.

## If you already split and regret it

Merging two sites into one is a site move with all the usual care: a one-to-one redirect map, one hop each, both properties verified, the old sitemap kept listed for a while, and internal links updated to the final URLs.

Do it when the second site has enough pages to be worth moving and few enough links to make the map manageable. Do it once, and change nothing else that month, so a drop has one suspect.

> Moving a site with almost no links costs almost nothing and gains the parent domain's history. Moving one with many links is still usually right, but plan it as a migration.

## A worked example

Say yourproduct.com sells an invoicing tool and adds a time tracker. The audiences overlap: freelancers who bill clients. That settles it, one domain.

The structure becomes /invoicing/ and /time-tracking/, each with its own hub, pricing page and guides. The home page says the company makes two tools for freelancers who bill by the hour, and links both hubs in the first screen. A guide about hourly rates sits at the company level and links to both. Six months later the two hubs rank for their own categories, and the company name brings people who then choose.

## Questions

### Is a subdomain bad for SEO?

No, but it is not free either. Google has said both subdomains and subdirectories work and treats a subdomain as part of the site in most cases. A folder removes the ambiguity and the second set of maintenance, which is why it is the usual answer for a small company.

### Will a second product dilute my rankings?

Not by existing. It dilutes attention, which is the real constraint. What hurts is a second product buried in the footer with three thin pages, not the fact that the domain now covers two things.

### Should the home page sell both products?

It should name both plainly and send people to the right hub quickly. The home page will rank for your company name; the product hubs are what rank for the categories, so that is where the selling belongs.

### Can I use the same blog for both products?

Yes, if every post says which product it is about and links to that hub. One page per topic still applies: do not write the same guide twice, once per product.

### When should I move a separate product site back onto the main domain?

When you are maintaining two sets of everything for no reason the business can name. Treat it as a migration: a one-to-one redirect map, both properties verified, and no other change that month.

## Read next

- [Subdomain vs subdirectory: what Google says and what to choose](https://porteur.ai/guides/subdomain-vs-subdirectory): Google says both can work. Here is how to choose for blogs, docs, languages and new products, and how to move with clean redirects.
- [Site architecture for a small product: shallow, linked, and honest](https://porteur.ai/guides/site-architecture): A site is a graph of links, not a folder tree. Hubs that are real pages, navigation a crawler can follow, and a worked map for two hundred pages.
- [URL structure: the decisions you make once](https://porteur.ai/guides/url-structure): Folders that mean something, slugs made of words, the variants that create duplicates, and a table of good and bad URLs for a product site.
- [Internal linking for a small site: which pages link to which](https://porteur.ai/guides/internal-linking-for-seo): Decide which pages rank. Build hubs, write clear anchors, fix orphans, and crawl your site to map links you control.
- [Website migration SEO checklist: before, during, after](https://porteur.ai/guides/website-migration-seo-checklist): Run a safe website migration: crawl and export, build and test one-to-one redirects, switch cleanly, submit sitemaps, use Search Console, and watch the data.
- [Brand search: the traffic you earn everywhere else](https://porteur.ai/guides/brand-search-demand): Why branded queries convert best, where the demand comes from, how to read yours in Search Console, and the pages that must win your own name.
- [Click depth](https://porteur.ai/glossary/click-depth): Click depth is the clicks from home to a page. Keep key pages within three clicks. Learn how to measure it and cut depth without spammy links.

Paste the URL of either product and the free check reads the site and the searches around it in about thirty seconds, then shows which one search actually knows about. Free check: https://porteur.ai/