Technical Implementation of Multilingual Sites

A Sri Lankan tea exporter launched a German version of their website by simply duplicating their English pages and running them through Google Translate. They did not set up hreflang tags, did not create a German sitemap, and did not tell Google the German version existed. After six months, Google was still showing the English version to German buyers searching in German. The exporter had spent time and money on a German version that almost nobody found through search.

A multilingual website requires technical implementation that signals to Google which language version to show in each market. Without proper technical setup, even excellent localised content will not reach its intended audience. The technical foundation of a multilingual site is just as important as the quality of the translations.

URL Structure Decisions

Three URL structure options exist for multilingual sites, and your choice affects both SEO and maintenance. Subdirectories (yoursite.com/de/, yoursite.com/fr/) are the most common and recommended approach. They keep all content under one domain, consolidating SEO authority, and are simple to implement and maintain. Subdomains (de.yoursite.com, fr.yoursite.com) are treated as separate sites by Google, which means each subdomain must build its own SEO authority independently — this is harder for new markets. Separate domains (yoursite.de, yoursite.fr) provide the strongest local signal but require managing multiple domains, SSL certificates, and hosting configurations.

For most exporters, use subdirectories. They offer the best balance of SEO effectiveness, ease of implementation, and ongoing maintenance. Reserve subdomains for cases where your content management system forces that structure. Use separate domains only when targeting markets with strong local domain preferences (.de for Germany, .jp for Japan, .cn for China) and when you have the resources to manage them properly.

Whichever structure you choose, be consistent. Language codes in URLs should follow ISO 639-1 standard (de, fr, ja, zh, etc.). Use the same structure for all pages — if your product page is yoursite.com/de/products/product-name, keep that pattern consistently, not mixing yoursite.com/fr/product-name and yoursite.com/products-fr/product-name.

Hreflang Implementation

Hreflang tags tell Google which language and regional version of a page to serve to users based on their language and location. Without hreflang tags, Google may show the wrong language version in search results — showing your English page to French searchers or your German page to Austrian searchers who should see a tailored version. Hreflang tags are the most commonly overlooked technical element of multilingual sites.

Implement hreflang in one of three ways: in the HTML head (link rel="alternate" hreflang="de" href="..."), in the HTTP header (for non-HTML files like PDFs), or in the XML sitemap. The HTML head method is simplest and most common. Each page must link to all language versions, including itself. Include an x-default entry that specifies which page to show when no language matches — typically your English version.

Common hreflang mistakes to avoid: using incorrect language codes (use ISO 639-1, not country codes alone), missing reciprocal links (if page A links to page B, page B must link back to page A), forgetting the x-default entry, and mixing URLs between hreflang and canonical tags (they must be consistent). After implementing hreflang, test it using Google Search Console's URL inspection tool or an online hreflang validator.

Language Switcher Design

The language switcher is one of the most important UI elements on a multilingual site. It must be easy to find — users should not have to search for it. Place it in a consistent location on every page, typically the top right corner of the header. Use language names in their native script (Deutsch, Français, 中文, 日本語), not flags — flags represent countries, not languages, and using a French flag for a French-language version may offend users from Switzerland, Belgium, or Canada.

When a user selects a language, remember their choice. Do not override it based on IP detection on subsequent visits — nothing frustrates a user more than being redirected away from their chosen language version. Store the preference in a cookie or the user's browser settings. If you use IP-based language detection for first-time visitors, show a clear prompt asking if they want to switch rather than redirecting them automatically.

Make the language switcher accessible on every page, not just the homepage. Include it in the mobile navigation as well. For pages that have not been translated yet, either hide them from the language switcher or show a clear indicator (greyed out or marked as "coming soon") rather than sending users to an English page from their chosen language version.