Multilingual Corporate Site Architecture: Subdirectory, Subdomain or ccTLD

A comparison of subdirectories, subdomains and ccTLDs for a multilingual website, WordPress setup models, the translation workflow and the risks of automatic language redirection.
Technical summary
Technology
hreflang, WordPress, WordPress Multisite, translation plugins, CDN
Topic
Deciding the URL structure, CMS model and translation workflow for a multilingual site
Level
Intermediate
Prerequisites
  • Basic technical SEO knowledge
  • WordPress administration experience
In this article7 sections

On a multilingual corporate website, the first decision isn’t the translation plugin but the URL structure. This decision determines SEO signals, infrastructure, the content workflow and the cost of a migration years later all at once; changing it afterwards means changing every URL. Below, we treat the subdirectory, subdomain and ccTLD options, the implementation models in WordPress and the translation workflow as an architecture decision. It’s for technical teams preparing to add a new language or wanting to simplify their existing multilingual setup.

The difference between language and region targeting

An “English site” and a “Germany site” aren’t the same need. In language targeting, the content is for everyone who speaks that language; prices, legislation, contact details and service scope don’t change. In region targeting, the same language is presented with different content in different countries: the currency, legal texts, phone number, delivery terms or product range change.

This distinction is reflected directly in the hreflang values. If only the language is targeted, en is used; if the region is targeted too, language–region codes such as en-GB or de-AT are used. A region code can’t be used on its own; it’s always written together with a language code. On most corporate service sites, the need is language targeting. Opening unnecessary region variants produces groups of pages that duplicate each other and extra maintenance work.

One question is enough for the decision: will the content really be different in two country versions in the same language? If the answer is no, a single language version is enough.

Comparing URL structure options

Google’s multi-regional and multilingual sites guide lists these options neutrally. The choice is more an operational and organizational decision than a technical one.

Structure Example Strength Limitation
Subdirectory example.com/en/ One domain, one infrastructure, shared authority Weak country signal; a single server location
Subdomain en.example.com Separate hosting and publishing possible Separate DNS, certificate, monitoring
ccTLD example.de Strong country signal, local perception Domain and authority separate in each country
URL parameter example.com/?lang=en Easy to set up Not recommended; parsing and caching problems

Dimensions to weigh in addition to the table:

  • Organization: Will the languages be managed by the same team, or will country offices publish their own content?
  • Infrastructure: Will all languages run behind the same server and CDN? When a CDN is used, the effect of the server’s physical location on region targeting is already limited.
  • Analytics and monitoring: Each ccTLD needs a separate property in Search Console; subdomains can be grouped under a domain property, but URL-prefix properties are also opened for separate reporting per language. ccTLDs require cross-domain measurement configuration in analytics.
  • Future migration: Changing the structure later changes every URL. That’s an extensive redirect project.

On corporate websites managed by a single team, a subdirectory is often the most balanced option: one certificate, one DNS record, one monitoring point. If there’s a separate legal entity, a separate product range and a local marketing team per country, a ccTLD can be considered. A subdomain makes sense when the language versions need to be technically separate (a different platform, a different release cycle).

Multilingual setup options in WordPress

Once the URL structure is decided, there are three main models on the CMS side:

Model How it works When it fits
Single site + translation plugin Translations in the same database, content linked together Same structure, same team, small to medium content
Multisite, one site per language Each language a separate subsite; mapping via a plugin or custom code The languages’ structure and permissions diverge
Headless CMS Content from an API, the front end handles localization Multichannel content, custom front end

In the single-site model, the translation plugin (such as Polylang or WPML) keeps track of which language each piece of content is in and which content it’s paired with; it offers separate translation interfaces for menu, widget and theme strings. Its advantages are a single admin panel and automatic hreflang generation. Its limitation is that the plugin permeates the whole site; compatibility issues with the page builder, caching and custom queries depend on plugin updates. The picture we encounter most often in the field: after a plugin update, one language’s menu comes up empty, or the cache plugin writes two languages to the same cache key.

In the Multisite model, each language has its own options, menu and user permissions; language teams can’t break each other’s content. On the other hand, mapping between pages doesn’t come automatically: for hreflang, which page corresponds to which page on which site must be kept separately. Themes, page builder templates and global styles aren’t shared automatically between subsites either. Without a deliberate synchronization method, the languages drift apart visually.

The headless model is considered in projects where content also goes to channels other than the web or the front end is a custom application. A general assessment is in the what is a headless CMS and when to choose one article.

Translation workflow and content mapping

What breaks over time on a multilingual site is content parity more than infrastructure: the translation of a page updated in the source language stays old, and a new page is published in one language and forgotten in the others. Two years later, the English version describes a different company. To prevent this, manage content mapping as data.

  • Source language rule: Every piece of content has a source language, and translations are derived from the source. Cross-editing (from English to German, then from there to Turkish) isn’t done.
  • Status tracking: When the source content changes, the translations should drop to “update needed” status.
  • Glossary: Approved equivalents per language are kept for service names, product terms and brand phrases; if machine translation is used, this glossary is also given to the translation engine.
  • Localized slugs: URLs should be in the target language; mixed structures like /en/hizmetler/ give users and search engines an inconsistent signal.
  • Missing translation policy: How a page without a translation behaves in that language is decided in advance.

When the mapping is kept correctly, every page can generate hreflang links listing all its language equivalents, including itself:

<link rel="alternate" hreflang="tr" href="https://www.example.com/hizmetler/ag-kurulumu/" />
<link rel="alternate" hreflang="en" href="https://www.example.com/en/services/network-installation/" />
<link rel="alternate" hreflang="de" href="https://www.example.com/de/leistungen/netzwerkinstallation/" />
<link rel="alternate" hreflang="x-default" href="https://www.example.com/hizmetler/ag-kurulumu/" />

These links must be reciprocal: if page A points to B, B must point to A too. One-way hreflang is ignored. Each version’s canonical should point to itself, not to another language version; an English version given a canonical to the Turkish page drops out of the index. Validating the tag and its common errors are covered in detail in the hreflang implementation: common errors and validation article.

The risks of automatic language redirection

Automatically sending visitors to a language version based on their IP address or the browser’s Accept-Language header looks attractive. It has three serious side effects.

  1. Crawling problem: Search engine crawlers usually don’t send an Accept-Language header and mostly crawl from IPs in specific countries. Forced redirection can lead to some language versions never being crawled. That’s why Google recommends offering users a link rather than redirecting automatically based on the detected language.
  2. User control: A Turkish user abroad or an engineer using an English browser is forced into a version they don’t want and can’t get back.
  3. Cache mismatch: The same URL responding differently depending on the header requires a Vary: Accept-Language header in the response and the CDN cache key to include that header, which lowers the cache hit rate. Otherwise one user’s language redirect is served to others from the cache.

The language switcher needs attention too. A flag isn’t a language; show the language name in its own language (Deutsch, English). On every page, the switcher should go to the current page’s equivalent, not to the language’s home page. On pages without an equivalent, it should be clear to the user that they’re going to the language’s home page.

Multilingual site decision checklist

  • The targeting type is clear: language only, or language and region?
  • The URL structure was assessed in terms of organization, infrastructure and analytics, and the decision was put in writing.
  • The CMS model has been chosen; where the mapping data will be kept is clear.
  • Slugs, menus and category names have been localized for each language.
  • The source language rule, glossary and translation approval step have been defined.
  • The missing translation policy has been set.
  • hreflang is reciprocal, the canonical points to itself in every version; the x-default decision has been made.
  • There’s no forced automatic redirection; the language switcher goes to the page’s equivalent.
  • All language versions are in the sitemap; Search Console properties were opened according to the structure.
  • Forms, email notifications, legal texts and structured data were checked separately in each language.

The last item on the list is the one most often skipped: the contact form on the English page sends a Turkish confirmation email and nobody notices. If adding a new language or changing the existing structure involves URL changes, plan the transition with the preventing SEO loss when migrating a website steps. In projects where the architecture decision and the implementation need to be handled together, we start our multilingual and multi-regional websites work with this checklist.

Frequently asked questions

Is a subdirectory or a subdomain better for a multilingual site?

For corporate sites managed by a single team and running on the same infrastructure, a subdirectory usually has the lowest operating cost and shares the domain’s existing authority. If the languages will be managed by separate teams, on separate infrastructure or with separate publishing schedules, a subdomain may be more suitable.

Is a ccTLD required for local SEO?

No. A ccTLD gives a strong country signal but requires a separate domain, certificate, DNS and authority management for each country. Targeting can also be done with hreflang and localized content; a ccTLD makes more sense when there’s a separate legal entity and operation per country.

Is it right to redirect visitors automatically based on browser language?

Forced automatic redirection isn’t recommended. Search engine crawlers may not be able to reach the language versions, and users can’t stay on the version they want. A safer approach is a dismissible information bar suggesting the appropriate language and a visible language switcher on every page.

What should be done with pages that have no translation?

A written policy is needed: either the page isn’t published in that language at all and the language switcher leads to that language’s home page, or the page goes live only when its translation is complete. Publishing the source-language text in place of a translation breaks the user experience and hreflang consistency.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Web

We build and maintain corporate websites, WordPress and CMS platforms, intranet and SharePoint portals, document management, and form and approval workflows, and keep them secure and up to date.

Knowledge Center

Other articles