Which URL Structure Is Best for Multilingual SEO? A Decision Framework
Subdirectories (example.com/es/) are usually the best starting point for most sites because they consolidate authority, simplify hreflang, and work with a single domain. Subdomains (es.example.com) and country-code top-level domains (example.es) make sense when you...
If you are launching a multilingual site today, start with subdirectories under a generic top-level domain (gTLD) such as example.com/es/, example.com/de/. This structure keeps all link equity on one domain, makes hreflang implementation straightforward, and avoids the overhead of managing multiple properties. Subdomains and separate country-code domains (ccTLDs) are valid alternatives when you have specific technical, legal, or branding requirements that subdirectories cannot satisfy.
What URL structure means for multilingual SEO
URL structure is the first signal search engines use to understand which audience a page serves. It also determines how authority flows across language versions, how you configure hreflang tags, and what infrastructure you need to maintain. A structure that matches your operational reality reduces ongoing friction; a mismatch creates technical debt that compounds with every new market.
Google treats each of the three main structures as separate sites for crawling and indexing purposes, but it handles authority consolidation differently. Subdirectories inherit the root domain's authority by default. Subdomains are often treated as separate hosts, though Google has improved at associating them. ccTLDs send the strongest geo-targeting signal but require building authority from scratch for each domain.
The three main options at a glance
| Structure | Example | Best for | Authority handling | Geo-targeting signal | Operational complexity |
|---|---|---|---|---|---|
| Subdirectory (gTLD) | example.com/es/ | Most businesses targeting multiple languages or countries with a single brand | Consolidated on root domain | Weak (requires Search Console setting or hreflang) | Low — single CMS, single hosting, one hreflang map |
| Subdomain | es.example.com | Teams needing separate hosting, tech stacks, or content workflows per language | Partially shared; often treated as separate host | Weak (requires Search Console setting or hreflang) | Medium — separate DNS, potentially separate CMS instances |
| ccTLD | example.es | Brands with legal entities, distinct products, or strong local trust requirements per country | Fully separate; each domain builds its own authority | Strongest — automatic country association | High — multiple domains, hosting, SSL, Search Console properties, link-building per domain |
Decision criteria: match structure to your constraints
Use the following checklist to narrow the choice. Each "yes" pushes you toward the structure listed.
- Single team, single CMS, shared design system? → Subdirectories.
- Need to launch fast with minimal dev work? → Subdirectories.
- Regional teams own their own content, hosting, or tech stack? → Subdomains.
- Legal requirement to host data in-country? → Subdomains or ccTLDs.
- Brand operates as distinct local entities (different pricing, products, compliance)? → ccTLDs.
- Strong local competitor landscape where users expect a local domain? → ccTLDs.
- Targeting languages, not countries (e.g., Spanish for all of Latin America)? → Subdirectories with language codes (es/, es-mx/, es-ar/).
- Targeting specific countries with distinct search behavior? → Subdirectories with country codes (es-mx/, es-ar/) or ccTLDs.
If you answer "yes" to criteria in different columns, prioritize the one that represents the hardest constraint to change later. Hosting and legal requirements are harder to change than CMS workflows.
How hreflang works with each structure
Hreflang tags tell search engines which language or regional version of a page to serve. The structure you choose changes how you write and maintain these tags.
Subdirectories
One hreflang map covers all versions. Example for a Spanish page:
<link rel="alternate" hreflang="es" href="https://example.com/es/" />
<link rel="alternate" hreflang="en" href="https://example.com/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />All URLs share the same domain, so you can generate hreflang programmatically from your URL pattern. This is the lowest maintenance approach.
Subdomains
Same tag format, but each subdomain is a separate host. You must ensure every subdomain returns the full hreflang set, including cross-references to other subdomains. If you use separate CMS instances, each must be configured to output the complete map.
ccTLDs
Each domain needs its own hreflang map referencing all other ccTLDs. You also need to verify each domain in Google Search Console and set the international targeting country (though Google now relies more on hreflang). The operational burden scales linearly with the number of countries.
Practical scenarios
Scenario A: SaaS company expanding from English to Spanish, French, German
One marketing team, one Webflow site, shared design system. Goal: launch in three months. Choose subdirectories (/es/, /fr/, /de/). Authority stays consolidated. Hreflang is a single template. SeaText's Webflow translation agent can activate all three languages in minutes and keep new pages translated automatically.
Scenario B: E-commerce brand with separate warehouses, pricing, and compliance per EU country
Regional teams manage their own product catalogs and promotions. Legal requires data residency in Germany and France. Choose subdomains (de.example.com, fr.example.com) or ccTLDs if brand trust depends on local domains. Subdomains let you point each to regional infrastructure while keeping a common root brand.
Scenario C: Local services business entering Mexico and Argentina
Users in each country expect a .mx or .ar domain. Competitors all use ccTLDs. Choose ccTLDs (example.mx, example.ar). Budget for separate link-building, hosting, and Search Console management. The geo-targeting signal is automatic.
Common mistakes to avoid
| Mistake | Why it hurts | Fix |
|---|---|---|
| Mixing structures (subdirectories for some languages, subdomains for others) | Confuses crawlers, fragments authority, makes hreflang error-prone | Pick one primary structure; use subdirectories for language variants under a subdomain or ccTLD if needed |
| Using URL parameters for language (?lang=es) | Google may not crawl or index parameter-based versions reliably | Use path-based structures (/es/) instead |
| Skipping x-default hreflang | Users from unspecified regions get no clear fallback | Always include x-default pointing to your primary language version |
| Assuming ccTLDs guarantee rankings | Each domain starts with zero authority; you must build links locally | Plan 6–12 months of dedicated local SEO per ccTLD |
| Forgetting to update hreflang when adding a new language | New version stays invisible to search engines | Automate hreflang generation from your CMS routing table |
Key facts
| Fact | Detail |
|---|---|
| SeaText Webflow translation | Activates 125 languages automatically with no page or language limits |
| Translation automation | New Webflow pages, products, posts, and updates are detected and translated in the background |
| URL structure support | Works with subdirectories, subdomains, or ccTLDs — SeaText adapts to your chosen structure |
| Hreflang handling | SeaText generates and maintains hreflang tags for all translated versions automatically |
| Free activation | One-click install on Webflow with unlimited free translation |
| Translation control | Users can override important translations while AI handles the rest |
Limitations and when this advice does not apply
- Single-language sites: URL structure for multilingual SEO is irrelevant if you serve one language.
- App-only or API-first products: If your content lives behind authentication or in native apps, public URL structure matters less for SEO.
- Regulatory environments with mandatory local domains: Some countries (e.g., China with .cn ICP license) effectively require a ccTLD. The decision is made for you.
- Migrations from an existing structure: Changing URL structure on a live site carries migration risk. The best structure for a new launch may not justify the cost of migrating an established site.
- JavaScript-heavy SPAs without server-side rendering: Hreflang and crawlability depend on rendering setup more than URL pattern.
Terminology
- gTLD (generic top-level domain): Domain extensions like .com, .net, .org that are not tied to a specific country.
- ccTLD (country-code top-level domain): Two-letter domain extensions like .es, .de, .jp that signal a specific country.
- Subdirectory: A folder path under the root domain (example.com/es/).
- Subdomain: A prefix before the root domain (es.example.com).
- Hreflang: An HTML link attribute that tells search engines the language and optional regional targeting of a page.
- x-default: A special hreflang value indicating the fallback page for users whose language/region isn't explicitly covered.
- Geo-targeting: Configuring a site or section to target users in a specific country, done via Search Console, ccTLD, or hreflang.
FAQ
Can I use subdirectories for languages and subdomains for countries?
Yes. For example, example.com/es/ for Spanish globally, and mx.example.com/es/ for Mexico-specific Spanish content. Keep the hierarchy consistent and generate hreflang for every combination. This adds complexity; only do it if you have distinct country-level content that cannot live under a single gTLD.
Does Google penalize subdomains for multilingual sites?
No. Google treats subdomains as separate hosts but can associate them with the root domain. The main downside is diluted authority and more complex hreflang management. Many large brands (e.g., Wikipedia language subdomains) rank well with subdomains.
How long does it take for a new ccTLD to rank?
Expect 6–12 months of dedicated local link-building, content, and technical SEO before a new ccTLD competes with established local domains. The ccTLD gives you the geo signal, not instant authority.
What if I already use subdirectories but need to move to ccTLDs later?
Plan a careful migration: 301 redirect each subdirectory URL to its ccTLD equivalent, update hreflang maps, verify each ccTLD in Search Console, and monitor crawl errors. Run the migration per country to isolate risk.
Can I use automatic translation with any URL structure?
Yes. SeaText's translation agent works with subdirectories, subdomains, and ccTLDs on Webflow. It detects your URL pattern and generates translations and hreflang tags accordingly.
Do I need separate Search Console properties for each subdomain or ccTLD?
Yes. Each subdomain and ccTLD should be verified as a separate property. For subdirectories, a single domain property covers all languages; use the International Targeting report to monitor hreflang.
What about language codes vs. country codes in subdirectories?
Use language codes (es/, fr/) when targeting a language globally. Use country codes (es-mx/, es-ar/) or combined codes (es-MX/, es-AR/) when content differs by country. Match the code format in your hreflang values.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Learn more
Visit the website for more information.