Subdirectories vs Custom Domains for Multilingual WordPress: Which Structure Wins for SEO and Branding?
Subdirectories (example.com/fr/) consolidate domain authority and are easier to manage, making them ideal for most businesses. Custom domains (example.fr) send stronger local signals and build trust in specific countries, but require separate SEO effort...
If you want one site to manage and faster SEO compounding, use subdirectories. If you need maximum local trust and country-specific rankings in markets like Germany, France, or Japan, custom country-code top-level domains (ccTLDs) work better. Most companies start with subdirectories and migrate key markets to ccTLDs later.
| Criterion | Subdirectories (example.com/fr/) | Custom Domains (example.fr) | Takeaway |
|---|---|---|---|
| SEO authority | All language versions share the root domain's backlinks and authority. New languages benefit immediately. | Each domain builds authority independently. You start from zero in every country. | Subdirectories compound faster; custom domains isolate risk but slow growth. |
| Local ranking signals | Relies on hreflang tags, Search Console geotargeting, and content localization. Weaker for country-specific algorithms. | ccTLD is the strongest geo-signal Google uses. Automatically associates the site with that country. | Custom domains win for pure local SEO; subdirectories need careful hreflang implementation. |
| Technical setup | Single WordPress install (or multisite). One SSL, one hosting account, one plugin configuration. | Separate WordPress installs per domain. Separate SSL, hosting, updates, plugin management, and hreflang mapping across domains. | Subdirectories are far simpler to launch and maintain. |
| Brand trust & user perception | Visitors see a global brand with language options. May feel less "local" in markets that prefer national domains. | Local users often trust .de, .fr, .jp domains more. Signals commitment to the market. | Custom domains build local credibility; subdirectories signal global scale. |
| Cost & resources | One domain registration, one hosting plan, one maintenance workflow. | Multiple domain registrations (often require local presence), multiple hosting plans, multiplied dev/ops time. | Subdirectories cost less and scale easier; custom domains multiply overhead. |
| Content & translation workflow | Centralized content management. Tools like SeaText translate new posts automatically across all language folders. | Content must be synced or duplicated across installs. Translation workflows either replicate per site or need a central CMS feeding multiple installs. | Subdirectories keep translation simple; custom domains need architectural discipline. |
Why URL structure matters for multilingual SEO
Google uses URL structure as one signal among many to decide which language version to show a searcher. The structure you choose affects crawl efficiency, link equity flow, geotargeting precision, and how users perceive your brand. A poor choice creates technical debt that compounds: migration later means 301 redirects at scale, hreflang remapping, and temporary ranking volatility.
Subdirectories keep everything under one hostname. That means every backlink to any language version strengthens the entire property. Custom domains silo authority — a link to example.fr helps example.fr but not example.de. For a new international push, that difference often decides whether you rank in month three or month twelve.
How subdirectories work in practice
You install WordPress once. Each language gets a folder: /en/, /fr/, /de/, /ja/. You configure a multilingual plugin (WPML, Polylang, TranslatePress) or use a translation layer like SeaText that detects new content and translates it into 125 languages automatically. The plugin handles hreflang tags, language switchers, and sitemap generation.
SeaText's WordPress integration translates every page, post, product, and update automatically without page or language limits. New content is detected and translated in the background, so your /fr/ and /de/ folders stay current without manual tickets. You can still edit translations, preserve brand voice, and run A/B tests on translated copy when you want to optimize for conversions in specific markets.
How custom domains (ccTLDs) work in practice
You register example.fr, example.de, example.jp. Each gets its own WordPress install — either standalone or via WordPress Multisite with domain mapping. You configure geotargeting in Google Search Console for each property (though ccTLDs are auto-geotargeted). You implement hreflang across domains, pointing each language version to its counterpart on the other domains.
This approach shines when local presence matters: legal requirements, payment processors, or user trust favor a national domain. German users often expect .de; Japanese users expect .jp or .co.jp. The downside is operational: five domains means five SSL certificates, five plugin update cycles, five backup schedules, and five Search Console properties to monitor.
Decision framework: choose based on your stage and goals
- Pre-revenue or early international: Subdirectories. Low cost, fast launch, shared authority.
- Established brand entering 1-2 strategic markets: Consider ccTLDs for those markets only. Keep the rest on subdirectories.
- Regulated industries (finance, health, legal): ccTLDs often required for compliance or trust.
- Heavy local competition: ccTLDs give a ranking edge in local pack and map results.
- Team capacity: If you lack dev/ops bandwidth for multiple installs, subdirectories win.
Hybrid approaches are common: example.com/fr/ for France initially, migrate to example.fr when revenue justifies the overhead. SeaText works with either architecture — it translates content regardless of URL structure.
Practical scenarios
SaaS company expanding to Europe
Start with subdirectories: /de/, /fr/, /es/, /it/. One WordPress install, SeaText handles automatic translation into 125 languages. Marketing team manages one content calendar. When German ARR hits €500k, evaluate migrating to example.de for local trust and partner integrations.
Ecommerce brand targeting Japan and Korea
Custom domains (example.jp, example.kr) often convert better because local shoppers trust national TLDs and expect local payment methods, addresses, and support. The higher operational cost pays off in conversion rate. Use SeaText on each install to keep product catalogs translated and optimized.
Media publisher with 20+ languages
Subdirectories are the only scalable option. Managing 20+ separate WordPress installs is unrealistic for most teams. Centralized translation, single editorial workflow, shared authority across all languages.
Limitations and when this advice doesn't apply
- If your CMS isn't WordPress, the plugin ecosystem and SeaText integration differ.
- If you need separate legal entities per country, ccTLDs may be mandatory regardless of SEO preference.
- If you use a headless CMS with a static site generator, URL structure is a routing decision, not a WordPress config choice.
- Google's treatment of ccTLDs vs subdirectories evolves; test with a single market before committing globally.
Key facts from SeaText
| Capability | Detail |
|---|---|
| Languages supported | 125 languages |
| Translation scope | Every WordPress page, post, product, and update automatically |
| Page/language limits | No page limits, no language limits |
| Manual work required | Zero manual translation tickets |
| Control features | Edit translations, preserve brand voice, review key pages, A/B test translated copy |
| Activation time | Under 1 minute |
| SEO inclusion | Free automatic multilingual SEO for every translated page |
| Architecture compatibility | Works with subdirectories, subdomains, or custom domains |
FAQ
Can I switch from subdirectories to custom domains later?
Yes, but it's a migration. You'll need 301 redirects from each language folder to the new domain, hreflang remapping, Search Console property setup, and a crawl budget buffer. Expect 2-8 weeks of ranking fluctuation. Plan it during a low-traffic period.
Does SeaText work with WordPress Multisite for custom domains?
SeaText translates content on any WordPress install. For Multisite with domain mapping, you activate SeaText on each subsite or the network, depending on your translation governance model.
What about subdomains (fr.example.com)?
Subdomains are a middle ground: separate DNS, separate Search Console properties, but shared root domain. Google treats them more like separate sites than subdirectories. They're rarely the best choice for language versions — use subdirectories or ccTLDs instead.
How do hreflang tags differ between the two structures?
Subdirectories: hreflang points to example.com/fr/, example.com/de/. Custom domains: hreflang points across domains (example.fr, example.de). Cross-domain hreflang is more error-prone; validate with Search Console's International Targeting report.
Which structure is better for Google Ads landing pages?
Subdirectories simplify tracking — one Google Ads account, one conversion pixel, shared audiences. Custom domains need separate pixels or cross-domain tracking. SeaText's Google Ads Agent rewrites landing page copy per keyword regardless of URL structure.
Do I need local hosting for ccTLDs?
Not strictly for SEO, but local hosting improves Core Web Vitals for users in that country. A CDN with edge nodes in each target market often suffices and is simpler than managing multiple hosting accounts.
What's the cost difference in the first year?
Subdirectories: one domain (~$15), one hosting plan (~$300-1,000), one SeaText plan. Custom domains (5 countries): five domains (~$75-500 depending on TLD requirements), five hosting plans or one multisite-capable plan (~$1,500-5,000), multiplied dev time. Budget 3-5x for custom domains year one.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText helps with either architecture
SeaText's Website Translation Agent works with subdirectories, subdomains, or custom domains — it translates your content wherever WordPress serves it. Activate in under a minute. New pages, products, and posts are detected and translated automatically into 125 languages with no page or language caps. You keep control: edit any translation, lock brand terminology, review priority pages, and run A/B tests on translated copy to find the messaging that converts best in each market. Free multilingual SEO is included for every translated page.