Which URL structure is best for a multilingual website?

For most sites, language subdirectories on one domain (example.com/de/) are the simplest choice: one host to maintain, one set of analytics and tooling, and a clear URL per language. Subdomains and country-code domains make sense when you need separate infrastructure, legal entities or strong country targeting. Google documents all three as workable.

Do I need a country-code domain to rank in another country?

No. Google's documentation describes country-code domains as a strong geotargeting signal, but it also lists subdomains and subdirectories on a generic domain as valid options. Pair whichever structure you choose with hreflang annotations so Google can match each page to the right language or region.

Are URL parameters like ?lang=de a good way to switch languages?

Google lists URL parameters such as site.com?loc=de as not recommended for geotargeting, because they make URL-based segmentation difficult. Google also recommends separate URLs per language rather than cookies or browser settings. If you use parameters today, plan a move to folders or subdomains with redirects.

Can I mix structures, such as ccTLDs for big markets and folders for the rest?

Yes, a hybrid is technically fine as long as each language or region version has its own crawlable URL and your hreflang annotations are complete and reciprocal. The cost is operational: you maintain more than one pattern, and it is easy to create gaps in sitemaps, redirects and tracking.

Subdirectories vs Subdomains vs ccTLDs for SEO

For most multilingual websites, language subdirectories on a single domain (for example example.com/de/) are the best starting point, because they are simple to set up and maintain. Subdomains (de.example.com) and country-code domains (example.de) are also valid, and are worth the extra cost when you need separate infrastructure, local legal entities or the strongest possible country signal. URL parameters (?lang=de) are the option Google's documentation explicitly marks as not recommended.

What does Google say about multilingual URL structure?

Google's documentation on managing multi-regional and multilingual sites describes four options and does not crown a single winner. It asks you to pick a structure that makes it easy to geotarget the whole site, or parts of it, to different regions. Three points from that page matter most:

Google recommends a separate URL for each language version of a page, rather than using cookies or browser settings to change the language on one URL.
Localized words in URLs are fine, and internationalized domain names are fine.
You should still tell Google how the versions relate by using hreflang annotations or sitemaps. The URL structure alone does not replace them.

The same page says Google ignores locational meta tags such as geo.position, so do not rely on those.

The four options at a glance

The table below follows the pros and cons in Google's documentation, with a few operational notes added from common practice (marked in the last column).

Structure	Example	Main advantages	Main drawbacks	Common-practice note
Country-code domain (ccTLD)	`example.de`	Clear geotargeting; server location does not matter; easy to separate sites	Can be expensive; may be unavailable; some registries have strict rules; targets a single country	Each domain builds its own reputation, so a new domain starts without the links of your main site
Subdomain on a generic domain	`de.example.com`	Simple to set up; can be hosted in different locations; easy to separate sites	Users may not tell whether `de` means language or country	Often treated by teams as a separate site for analytics and tooling
Subdirectory on a generic domain	`example.com/de/`	Simple to set up; low maintenance on one host	Users may not recognize the geotargeting; single server location; harder to separate sites	Easiest to keep consistent when one team runs the CMS
URL parameter	`example.com?lang=de`	None listed by Google	Makes URL-based segmentation difficult; users may not recognize the geotargeting	Parameters are easy to break with caching, tracking and redirects

When should I use subdirectories?

Choose subdirectories when you have one brand, one CMS and one team, and you want the lowest ongoing cost. Everything lives on one host, so one TLS certificate, one robots.txt, one sitemap index and one Search Console property can cover all languages. It is also the pattern most CMS plugins and platform features produce by default, which reduces custom work.

A typical set of URLs looks like this:

https://example.com/            (default language, e.g. English)
https://example.com/de/         (German)
https://example.com/fr/         (French)
https://example.com/pt-br/      (Brazilian Portuguese)

The trade-offs are the ones Google lists: a single server location and less obvious geotargeting to people reading the URL. Neither is usually a blocker, since a CDN handles the first and hreflang handles the second for search engines.

When should I use subdomains?

Use subdomains when a language or region needs to run on separate infrastructure or by a separate team, while still sharing a brand. Examples include a regional store with its own checkout and stock system, or a regional marketing team that deploys independently.

Be aware of what you are signing up for. Search Console properties, analytics views, certificates and redirects now exist per subdomain. Whether a subdomain "shares" authority with the main site is something Google has not published a firm rule on in the pages we reviewed, so avoid choosing subdomains on the assumption that they inherit or isolate ranking strength. Treat that as unverified.

When should I use country-code domains?

Use a ccTLD when targeting a specific country is the main goal and you can sustain a separate site for it. Google describes ccTLDs as a clear signal for geotargeting. Typical reasons to pay for the extra overhead:

You have a local company, local payment methods or local legal requirements.
Customers in that market strongly prefer a local domain.
You run each market as an independent business.

Two cautions. First, a ccTLD targets one country, so example.de does not naturally serve German speakers in Austria or Switzerland. Second, not every country-code domain is treated as one. Google's documentation says that .eu and .asia are generally treated as generic, and that some ccTLDs such as .tv and .me are also treated as generic, with .io, .co and .fm in the same list; Google notes the list may change. Check the current page before buying a domain for geotargeting.

Why are URL parameters a bad idea for languages?

Google's table lists no advantages for parameters and marks them "Not recommended". In practice, parameter-based switching makes it hard to segment reports by language, is easy to strip accidentally in redirects or caches, and tempts developers to serve different content on the same URL depending on a cookie. Google recommends separate URLs instead, and notes that locale-adaptive pages (content that changes by visitor location or language) may not be fully crawled, partly because Googlebot does not send an Accept-Language header.

If you are on parameters now, moving to folders is usually worth it. Use permanent server-side redirects from the old URLs, which is the approach Google's redirect documentation recommends for permanent moves.

Which structure fits my situation?

Situation	Reasonable default	Why
Small business or blog adding two to five languages	Subdirectories	Lowest cost and maintenance
WooCommerce, Shopify or similar store with translated catalog	Subdirectories (what most platform features generate)	Keeps one checkout and one admin
Distinct regional business units with separate stacks	Subdomains or ccTLDs	Separate deployment and ownership
One or two flagship countries with local presence	ccTLD for those, folders for the rest	Strong country signal where it pays off
Existing `?lang=` site	Migrate to subdirectories	Parameters are not recommended

This table is our inference from Google's documented trade-offs, not an official ranking.

What stays the same whichever structure you pick?

The structure is only the container. These tasks apply to all of them:

Give every language version its own crawlable URL, and link between them with plain <a href> links.
Add reciprocal hreflang annotations, including a self-reference, and a fallback x-default where it fits.
Keep canonical tags pointing to the same-language page, not to the default language.
Decide your slug translation policy before you launch, since slugs are expensive to change later.
Run through the multilingual SEO checklist before and after launch.

Moving between structures later is possible but requires a full redirect map and careful monitoring, so it is worth deciding deliberately now.

Key takeaways

Google documents ccTLDs, subdomains and subdirectories as workable, and marks URL parameters as not recommended.
Subdirectories on one domain are the simplest default for most sites.
Subdomains and ccTLDs add operational overhead, justified by separate infrastructure, teams or strong country targeting.
A ccTLD targets one country; some country-code domains (such as .tv and .me) are treated as generic by Google.
Whatever you choose, give each version its own URL and add reciprocal hreflang annotations.

Sources

Managing multi-regional and multilingual sites – URL structure options, pros and cons, ccTLD handling, separate URLs per language
Localized versions of your pages – hreflang annotations and how versions relate
Locale-adaptive pages – crawling limits for content that varies by visitor locale
Redirects and Google Search – permanent redirects when moving URLs