Running Three Content Sites on One Domain — A Next.js Sub-Path Architecture Guide

When you've been running a content site for a while, a natural need arises: I want to start a second site, a third site.

The normal approach is to buy a domain for each — $6-10 per year per domain. Three sites = $18-30. Not a huge amount, but it adds up. And managing multiple domains and multiple Vercel projects is a hassle.

I worked out a better approach: using Next.js's sub-path architecture to run multiple content sites under one domain, hosted for free on Vercel.

Step 1: How Sub-Path Architecture Works

Your main domain is agentclaw.sale (or whatever). Under this domain, assign different paths to different content sites.

tool.agentclaw.sale for tool-related content wear.agentclaw.sale for apparel content ops.agentclaw.sale for operations content

Each sub-path looks like an independent site, but they all share the same project, same domain, and same infrastructure.

Step 2: Benefits of This Architecture

Save money: Domain costs drop from $18-30 per year to $6-10 — saving two-thirds.

SEO advantages: All content is under one domain. Google accumulates authority to the root domain. Every sub-site benefits from the parent domain's credibility. New sites don't start from zero.

Easy management: One GitHub repo. No switching between multiple Vercel projects. One push updates all sites simultaneously.

Step 3: Next.js Implementation

Using App Router (Next.js 13+)

Create directory groups under /app, each independently maintaining layout and page files:

/app/(tool)/ /app/(wear)/ /app/(ops)/

Each site can use different themes and layouts. The tool site might have listing pages, the wear site shows articles, the ops site displays a data dashboard.

Middleware Routing

Use middleware.ts to route requests to the correct content module based on path. Different sites can have completely independent URL structures.

Shared Components

Common components can be extracted and reused — top navbar, footer, SEO configuration, database connections. All sites share the same setup. Change one component, all three sites update simultaneously.

Step 4: Database Design

If each site needs independent data, use separate tables or prefix-based distinction.

My approach: use Feishu Bitable to manage content metadata. Add a "site" field to each article record. The frontend filters content based on the current path's site value. One data source supports three sites — no separate databases needed.

Step 5: Domain Binding

In your domain registrar's dashboard, add CNAME records pointing to Vercel's DNS target:

• CNAME record tool → cname.vercel-dns.com
• CNAME record wear → cname.vercel-dns.com
• CNAME record ops → cname.vercel-dns.com

Then in Vercel's project settings, add all three domains to the Domains list. Vercel automatically generates SSL certificates for each. The whole process takes under 10 minutes.

Step 6: Differentiated Content Strategy

Each sub-site should have a distinct content and monetization strategy:

• Tool site: Tool reviews and comparisons (SEO tools, writing tools) — suitable for AdSense
• Wear site: Apparel content (buying guides, style tips) — suitable for CPS affiliate monetization
• Ops site: Operations content (solo entrepreneur experience) — suitable for courses or consulting

While they share the codebase and domain, their monetization, audience, and content style can be completely different.

Step 7: Advanced Configuration

Rewrites

Configure rewrites in next.config.js for cleaner URL structures. Map long paths to short, memorable URLs.

Different Cache Strategies

Configure headers to return different caching strategies per sub-site. The tool site might need high dynamism while the ops site benefits from strong caching.

Independent Sitemaps

Generate separate sitemaps for each sub-site and submit them independently to Google Search Console.

Step 8: Mobile and PWA

Vercel supports one-click PWA configuration, letting users add your site to their phone home screen. All sub-sites share one service worker — users install once and access all sub-sites.

FAQ

Q: Does this architecture affect SEO?

A: Not only does it not hurt — it helps. All content under the same domain means Google accumulates authority at the root level. However, if your sub-sites cover wildly different topics (e.g., fitness and coding), Google may get confused about your site's overall theme. Keep sub-sites logically related.

Q: Does Vercel's free plan support multiple domain binding?

A: Yes. Vercel only cares about which domain you deploy to, not how you structure URLs. One project supports multiple domains.

Q: Does one site's content affect another's rankings?

A: Yes, positively. All content shares the same root domain's authority. High-quality content on one site boosts the entire domain's trust, helping other sites rank better.

Q: Is this suitable for very different content topics?

A: Not really. Google judges topical authority based on overall site content. Mixing too many unrelated topics under one domain can dilute authority. Best to keep sub-sites thematically connected.

Q: Do I need separate GSC for each site?

A: No. All sub-sites are under the same domain. Configure one site (the root domain) in GSC, then view each path's performance data within the same property.

Summary

Running three content sites on one domain: Next.js sub-path architecture + Vercel free hosting.

• Cost: From $18-30/year for three domains down to $6-10/year — save two-thirds
• Management: One GitHub repo, one Vercel project for all sites
• SEO: Authority concentrated on root domain, every sub-site benefits
• Efficiency: One push updates all sites, shared components

If you're planning multi-site operations, this solution is worth trying. The technical barrier from one site to many is low. The real challenge is replicating your operational capability.

First get profitable with one direction. Only when traffic is consistently above 500 daily UV and revenue covers your time cost should you start a second site. Don't start with three — you won't be able to manage it.