Do You Need A Separate Domain Or Subdomain Per Language For Your Website?

Not necessarily. It depends on your setup and target markets. A subdirectory structure (example.com/fr/) works well for the majority of multilingual sites, consolidates SEO authority under one domain, and is cheaper to run than separate domains.

You have three real options when you add languages to your site:

• Subdirectories (example.com/fr/): translated content lives under the main domain
• Subdomains (fr.example.com): each language runs as a semi-independent site
• Country-code top level domains, or ccTLDs (example.fr): each region gets its own domain

Each option has a different impact on SEO, technical setup, and cost. Below, we break down what to pick, when to pick it, and the URL patterns to avoid along the way.

URL Structures To Avoid Before We Go Further

A few setups will hurt your multilingual visibility no matter how well you execute everything else. Skip these:

• Same URL with cookie or JavaScript language switching. If example.com/about shows French to one visitor and English to another based on browser settings, search engines can only index one version. Your translated content won't appear in search results, and any shared links will send people to the wrong language. Google specifically mentions this, too.
• Language parameters like ?lang=fr. Google's own documentation also recommends separate URLs for each language rather than parameters. Crawlers often ignore or deprioritize parameterized URLs.
• All languages displayed on one page. Search engines try to identify a single language per page. Stacking them confuses crawlers and creates a poor user experience.

Each language version of your site needs its own distinct, crawlable URL. That's where subdirectories, subdomains, and ccTLDs come in.

Understanding Your Three Options

Subdirectories (example.com/fr/)

Subdirectories keep every language under one main domain. That means all the backlinks, traffic, and authority your site already has flow to your translated pages too. For most businesses adding 2 to 10 languages, this is the simplest and most effective option.

Nike is a good example. They use subdirectories for both region and language: nike.com/ca/ for English Canada, nike.com/ca/fr/ for French Canada, and nike.com/fr/ for French France. One domain, layered paths, shared authority.

Subdirectories are also the cheapest to run. There's no extra DNS setup, no separate SSL certificates, and no new server configuration.

Subdomains (fr.example.com)

A subdomain is a child partition of your root domain. Search engines treat it as a semi-independent site: it inherits some authority from the main domain, but not all. You'll need to build some SEO signals for the subdomain separately.

Wikipedia uses subdomains (en.wikipedia.org, fr.wikipedia.org) and HubSpot uses them for content that behaves differently from the main site (blog.hubspot.com, developers.hubspot.com). Gap Inc. uses the same pattern for its brand family: Old Navy at oldnavy.gap.com and Banana Republic at bananarepublic.gap.com. Each brand keeps its own identity while sharing the parent infrastructure. The pattern makes sense when each language version has distinct content, branding, or editorial strategy.

The tradeoffs: subdomains require DNS records and sometimes dedicated hosting per language, which adds complexity.

Country-code top level domains (example.fr)

ccTLDs like .fr, .de, and .co.uk send the strongest possible geo-targeting signal to Google. A French visitor seeing a .fr URL immediately understands the site is for them, and search engines give ccTLDs a ranking advantage in their home country.

According to a 2024 study by GA Agency and SE Ranking, ccTLDs hold 56% of Google's top three ranking positions globally, rising above 80% in some European markets. It also dominated top positions, while subdomains showed up in only about 3% of SERPs.

The catch: each ccTLD starts from zero in terms of SEO authority. You'll need to build backlinks, manage separate DNS and SSL setup, and meet country-specific registration requirements (some ccTLDs like .de require a local administrative contact). L'Oréal Group uses this approach for its distinct brands (maybelline.com, lancome.com) because each targets a different audience. It works for them because they have the teams and budget to support it.

Comparison At a Glance

How Search Engines Actually Treat Each Structure

Google has been clear that subdomains and subdirectories aren't weighted differently in ranking algorithms. John Mueller, Google's Search Advocate, has said the choice comes down to what's sustainable long term for your setup.

That said, the real-world data tilts toward subdirectories for one reason: authority consolidation. SE Ranking's study found subdirectories accounted for roughly 20% of all SERP positions studied, while subdomains came in at just 3%.

Whichever structure you choose, you'll need hreflang tags to connect your language versions. They tell search engines which pages are translations of each other, so the right version shows up in the right market. Without them, search engines may treat your translated pages as duplicate content.

This is notoriously hard to get right. An Ahrefs study of 374,756 domains found 67% of websites struggle with hreflang implementation. Weglot handles hreflang automatically for every translated page, regardless of whether you use subdirectories or subdomains.

When Does a Separate Domain or Subdomain Actually Make Sense?

There are cases where going beyond subdirectories is the right call:

• Distinct legal entities per country. If you run a French GmbH with different product lines, pricing, or customer support from your US operations, a separate domain gives each entity its own digital home.
• Strong local teams and country-specific operations. Companies with offices, inventory, and marketing teams in each market (think regional retailers) benefit from ccTLDs that match local trust signals.
• Brand perception varies by region. A house-of-brands strategy like L'Oréal keeps Maybelline and Lancôme on separate domains because they serve very different customers.
• Technical necessity. If part of your site runs on a different platform or a third-party tool, a subdomain is sometimes the only practical option. Flodesk, for instance, uses help.flodesk.com for its third-party knowledge base.

For most SaaS and ecommerce businesses adding a few languages, none of these apply. A subdirectory structure is lighter, faster, and keeps your main domain working for you.

5 Questions To Help You Choose

1. Do I want my translated content to share authority with my main site? If yes, subdirectories.
2. How many languages am I adding? For 2 to 10 languages, subdirectories are typically the simplest path. For sites with dedicated regional teams, consider ccTLDs.
3. Do I have local teams managing content per country? Subdirectories and subdomains work well with a central team. ccTLDs give regional teams more independence, but require the investment to match.
4. What's my budget for DNS, SSL, and hosting? Subdirectories are cheapest. Subdomains add configuration. ccTLDs add registration, legal, and infrastructure costs.
5. Do I need to change it later? Migrating from a ccTLD or subdomain to a subdirectory requires extensive 301 redirects and typically disrupts rankings. Pick a structure you can stick with.

How Weglot Fits In

Whether you pick subdirectories or subdomains, Weglot creates them automatically (example.com/fr/, de.example.com) with no manual configuration. Either way, Weglot handles hreflang tags, translates your metadata, and serves SEO-friendly URLs without any developer time.

Behind the scenes, Weglot uses AI to translate your content instantly. Our AI Translation Model generates on-brand translations based on your brand guidelines, tone of voice, custom instructions, and your Glossary, which you or your team members can review and refine.

For a deeper comparison across the two options, see our guide on subdirectory vs subdomain.

Conclusion

For most websites, you don't need a separate domain or subdomain per language. A subdirectory structure handles multilingual SEO cleanly for the vast majority of businesses. Subdomains and ccTLDs have their place, but only when your setup calls for them: distinct legal entities, local teams, or content that genuinely functions as a separate site.

The structure matters less than what sits on top of it: good translations, hreflang done right, and a reason for each language version to exist.

Try Weglot free for 14 days to see how subdirectories and hreflang work on your site, with no DNS or setup work on your end.