By Mehdi HassanShould a multilingual website use subdirectories, subdomains or country domains?
A multilingual startup website should use subdirectories by default: example.com/de/, example.com/fr/, example.com/es/. It's the cheapest to build, the easiest to maintain, and it pools all your search authority on one domain. Subdomains and country domains are exceptions you choose for a specific reason, not upgrades.
This is the part of our multilingual website guide that people most often get stuck on, because each option has someone online arguing for it. The research we drew on for this cluster agrees on subdirectories for most sites, and so does our own build experience across Framer, Webflow and Next.js. The rest of this page explains the exceptions honestly, so you can tell whether you're one of them.
How do the three international URL structures compare?
The three international URL structures differ in how strongly they signal a country, how they share authority, and how much work they add. Subdirectories win on cost and shared authority; ccTLDs win on local signal; subdomains sit in between and rarely win outright.
Factor | Subdirectory (/de/) | Subdomain (de.) | ccTLD (.de) |
|---|---|---|---|
Example | example.com/de/ | de.example.com | example.de |
Shares domain authority | Yes, fully | Partly, treated more separately | No, each domain starts alone |
Country signal | Via hreflang and content | Via hreflang and content | Strongest, built into the domain |
Build and hosting | One site, one deploy | Often separate configs | Separate domains, DNS and certificates |
Analytics and consent | One property | Cross-subdomain setup needed | Cross-domain setup per market |
Platform support | Native in Webflow, Framer, Next.js | Possible, more setup | Possible, most setup |
Best for | Most startups and SaaS | Separately run regional teams | Local-first brands, regulated markets |
Google's documentation on managing multi-regional sites lists all of these as valid options with pros and cons. It doesn't punish any of them. The difference is practical: how much work each one creates, and whether that work buys you anything.
Why are language subfolders the right default for startups?
Language subfolders are the right default because a startup's scarcest resource is attention, and subfolders cost the least of it. Every backlink, mention and piece of content strengthens one domain, and every language ships from one codebase with one design system.
- Shared authority. A link to your English blog helps your German pricing page too, because both live on the same domain.
- One build. Components, analytics, cookie consent and deploys exist once. Adding a locale is a content task, not an infrastructure project.
- Native platform support. Webflow and Framer localization both publish languages as subfolders, and Next.js routes them with a locale segment, as our guide to Next.js i18n shows.
- Easy to change later. Moving a subfolder to its own domain is a known redirect project. Merging five country domains into one is a much bigger one.
The main argument against subfolders is the weaker country signal. In practice, hreflang, local content, local currency and local links supply that signal well enough for most B2B and SaaS sites. Get the hreflang setup right and the structure stops being the deciding factor.
When does a subdomain make sense for international SEO?
A subdomain makes sense when a regional site is genuinely run as a separate property: a different team, a different CMS, or a different product catalog. Choose it for organizational reasons, not because you expect an SEO gain.
For example, a company that acquired a Japanese business might keep that team's site on jp.example.com because it runs on different infrastructure and has its own release cycle. Forcing it into a subfolder would mean a proxy or a migration nobody has time for. That's a fair reason.
Pros
- Lets a regional team host and deploy independently
- Can live on different infrastructure or a different platform
- Keeps the main brand domain
- Clear separation for access and permissions
Cons
- Search engines treat it more like a separate site, so authority is shared less fully
- Analytics, consent and cookies need cross-subdomain configuration
- Design and components drift unless one team owns them
- Gives no stronger country signal than a subfolder
Many teams end up regretting subdomains for blogs and help centers for the same reasons, which is why moving them back is a common project. Our guide to subdomain to subfolder migration covers that process if you're already there.
When is a ccTLD vs subfolder the better choice?
A ccTLD beats a subfolder when the local market expects a local domain, when regulation or payments require a local entity and presence, or when you're building a separate brand in that country. For a global SaaS selling the same product everywhere, those conditions rarely apply.
- Local trust is part of the purchase. In some consumer markets, shoppers trust a local domain more for delivery, returns and support. If research with real customers shows this, it's worth the cost.
- You operate as a local business. A separate legal entity, local pricing, local terms and a local support team already exist, so the site mirrors a real split.
- The domain is the brand. You're launching under a different name in a market and want it to stand alone.
The costs are real. Each ccTLD starts with no authority, needs its own links, and multiplies DNS, certificates, consent banners and analytics. If none of the three conditions apply, a subfolder plus hreflang gets you nearly all of the benefit for a fraction of the effort.
Hypothetical example: choosing a structure for a three-market launch
For example, suppose a seed-stage B2B SaaS company sells in English and is adding German and French. Its sales team is in one office, it has one product and one price list in two currencies, and its marketing site runs on Next.js.
None of the ccTLD conditions apply: no local entity, no separate brand, no evidence that buyers want a .de domain. No separate regional team exists either, so a subdomain would only add setup. The verdict is /de/ and /fr/ subfolders, with hreflang generated from the routes, x-default on the English pages, and localized pricing and case-study sections.
Two years later the company opens a German subsidiary with local sales. It can still keep the subfolder, because the URL structure doesn't limit what the German pages say. A move to example.de would only make sense if the German business started operating as its own brand.
Does international URL structure change how you design and build the site?
Yes. The structure decides how many sites you're actually maintaining, which drives build cost and the ongoing work after launch. One domain with subfolders is one design system and one deploy; three ccTLDs can mean three of everything.
That's why we decide structure before design starts. It affects the navigation and language switcher, the CMS model, how analytics and consent are set up, and how redirects work if you ever change your mind. It's also one of the biggest inputs into what a multilingual website costs, because separate domains rarely share as much work as people hope.
Which international SEO structure should you choose?
Choose subdirectories unless you can name a specific reason for something else. A separate regional team points to a subdomain. A real local business or local-first brand points to a ccTLD. Wanting a better country signal on its own doesn't, because hreflang and local content supply that.
