Multilingual URL structure: subfolders, subdomains or domains
Short answer For most small businesses, put each language in a subfolder of the domain you already have: example.com/es/. Google lists it as easy and low maintenance, and Shopify and Wix steer you to it. Use a subdomain only if that language needs a separate server, and a separate domain only for a separate country. Never switch languages by cookie or ?lang=.
Want help applying this to your business? Talk it through on a free 30-minute call.
Book a callSubfolder, subdomain or separate domain: the short answer
Use a subfolder unless you have a reason not to. Your English pages stay where they are, and the Spanish ones live at example.com/es/.
Google compares the options in its guide to multilingual and multi-regional sites (Google Search Central):
| Setup | Example | What Google lists for it | Fits when |
|---|---|---|---|
| Subfolder | example.com/es/ | "Easy to set up", "Low maintenance (same host)" | Almost every small business |
| Subdomain | es.example.com | Easy to set up, can sit on a different server | One language is run by another team or system |
| Separate country domain | example.mx | "Clear geotargeting", but "Can only target a single country" and costs more | You serve a separate country, not just a language |
| URL parameter | example.com/?lang=es | "Not recommended" | Never, by choice |
Note what the table doesn't say: Google lists no ranking edge for any of them. The real differences are cost, upkeep, and whether a visitor can tell from the address what they'll get.
Does the language code in the URL help Google?
No. The /es/ is for people, not for Google. Google detects language by reading the page:
"We don't use any code-level language information such as lang attributes, or the URL." (Google Search Central: Managing multi-regional and multilingual sites)
Its hreflang guide says the same of subdomains: names like en-gb or de "are not used by Google to determine the target audience for the page; you must explicitly map the target audience" (Google Search Central). So whatever structure you pick, you still link each version to the others with hreflang tags. How to do that is in multilingual website SEO.
What the structure does decide is whether each language has its own address Google can find. That part matters a lot.
Why not one URL that switches language?
Because Google may never see your other languages. Google recommends separate URLs per language "rather than using cookies or browser settings to adjust the content language," and warns it "might not find and crawl all your variations" otherwise, since its crawler usually comes from the USA and sends no language preference (Google Search Central).
The same goes for sending visitors to a language by their browser or location. Google says to avoid automatic redirects between language versions (Google). Offer a visible language switch instead.
What your website builder already does
Most owners don't pick a structure from scratch: the platform offers a default. Check it before you build.
| Platform | Options | Default or advice |
|---|---|---|
| Shopify | Subfolder (example.com/en-ca), subdomain, country domain | Subfolders are "the best option" for a first setup; hreflang tags are added automatically (Shopify Help Center) |
| Wix Multilingual | Subfolder, subdomain, ?lang= parameter | Subfolders are the default; Wix warns parameters can hurt how you're found (Wix Help Center) |
| WordPress with WPML | Folders, a domain per language, ?lang= parameter | No default named; a parameter needs no server changes, a domain per language needs DNS setup (WPML documentation) |
On WordPress, the parameter is the easiest to switch on and the one Google calls not recommended. Pick folders.
Should English move to /en/?
Usually not. Leave your current language at the root (example.com/services) and add only the new ones (/es/servicios). Moving English to /en/ changes every address you already rank with. Google treats that as a site move: you need redirects, and "it can take a few weeks or more" for the new URLs to replace the old ones (Google Search Central: Site moves).
Starting a brand-new site? Then /en/ and /es/ side by side is fine. Either way, add a default page for visitors whose language you don't cover; Google's example is a home page with a language picker, marked x-default (Google).
Translate the page names too
Yes: /es/servicios/plomeria beats /es/services/plumbing. Google advises using "words in your audience's language in the URL" (Google Search Central: URL structure). It's fine to use localized words or a domain name in another script, as long as the URL uses UTF-8 encoding (Google).
For accented letters or Chinese characters, Google wants them percent-encoded in your links, so gemüse is written gem%C3%BCse (Google: URL structure). Most builders do this for you. The slug rules themselves are in URL slug best practices.
Language and country together: US and Canada
If one language serves two countries differently, add the country to the folder: /en-us/, /en-ca/, /fr-ca/. Shopify's subfolders work this way (Shopify). In hreflang, the code is language first, then the optional country, like en-CA (Google).
A Canadian business on a .ca domain should know Google treats that as a country domain, which "can only target a single country" (Google). French and English pages on the .ca both reach Canada fine. To target US customers too, the usual route is a generic domain such as a .com.
Example
A plumber adding Spanish
The site is plumberco.com. The owner adds /es/ with 8 translated pages: /es/servicios/destapar-drenajes and so on. English URLs don't change. Wix sets up the subfolder; hreflang links both ways.
A Montreal clinic on a .ca domain
English at the root, French at /fr/. One domain, one host, one bill. Both versions target Canada, which is where its patients are.
A store that turned on ?lang=es
Its WordPress plugin used parameters because they were easiest. Switching to /es/ folders changes every Spanish URL, so it needs 301 redirects from each old address, then a few weeks for Google to catch up.
FAQ
Are subdomains bad for SEO?
Google's comparison lists no ranking penalty for subdomains. Wix says search engines treat each subdomain as a separate site, so the main site's strength may not carry over (Wix Help Center). For a small site, a subfolder avoids the question.
Do I need a separate domain for each language?
No. A separate domain makes sense for a separate country, not a separate language. It costs more and, if it's a country domain, can only target that country (Google).
Can I change my URL structure later?
Yes, but it's a site move: redirect every old URL to its new one and expect results to wobble for weeks (Google: Site moves). Wix redirects old URLs automatically when you switch (Wix).
Will translated pages count as duplicate content?
No. Google says translated pages count as duplicates only if the main content stays untranslated (Google).
Can I put two languages on one page?
Google advises against side-by-side translations; keep one language per page (Google).
Different for you?
- You haven't translated anything yet, or need hreflang: Multilingual website SEO.
- You're moving languages to new URLs: Domain migration and 301 redirects and SEO.
- You want the site built in two languages: Website agent.
- You want each language found in search and AI answers: SEO & GEO agent.