Building a Multilingual WordPress Website: What Businesses Need to Get Right

Intro

Expanding a website to serve audiences in multiple languages sounds straightforward in principle. In practice it involves a set of technical, content, and strategic decisions that catch many businesses off guard. The mistakes tend to follow predictable patterns, and most of them are easier to avoid at the planning stage than to fix after a site has been built and launched.

Wesley Cude, founder of WordPress development company Cude Design, has built multilingual WordPress sites for clients across the UK and internationally. "The technical side of multilingual WordPress is well-supported by the available plugins," he says. "Where projects tend to go wrong is in the decisions that happen before a single line of code is written. Which languages, which URL structure, who owns the translations, how the site handles currency and regional differences. Getting those decisions right at the start saves a significant amount of rework later."

This article covers the key decisions involved in building a multilingual WordPress website, the technical approaches available, and the ongoing considerations that determine whether a multilingual site actually serves its intended audiences effectively.

Choosing the Right URL Structure

The first significant decision in a multilingual WordPress project is how to structure the URLs for each language version. There are three main approaches and each has implications for SEO, hosting, and ongoing management.

Subdirectories use a folder structure to separate language versions, with the main language at the root and other languages in subdirectories. A UK English version might sit at domain.com while a French version sits at domain.com/fr/. This approach keeps everything on a single domain, which means all the domain's authority applies to all language versions. It is the most common approach for businesses that are expanding into additional languages without a strong reason to treat each market as a completely separate entity.

Subdomains place each language version on its own subdomain, such as fr.domain.com for French. Search engines treat subdomains as separate entities with their own authority, which means a new subdomain starts with no accumulated authority even if the main domain has strong rankings. This approach is more technically complex to manage and generally only makes sense when there are strong reasons to treat each language as genuinely separate, such as significantly different content strategies for each market.

Country code top-level domains use separate domain registrations for each country, such as domain.fr for France or domain.de for Germany. This sends the strongest geographic signal to search engines and can be effective for businesses with a substantial presence in each market. It also carries the highest cost and complexity, as each domain effectively needs its own SEO strategy and link building programme.

For most businesses building a multilingual WordPress site for the first time, subdirectories are the right starting point. They are the simplest to implement, keep all authority on a single domain, and are straightforward to extend as additional languages are added.

Plugin Selection and Configuration

WordPress has two dominant multilingual plugins: WPML and Polylang. Both are capable of handling complex multilingual sites but they take different approaches to implementation and have different implications for site performance and ongoing management.

WPML is the more fully-featured option. It handles translation management, string translation for theme and plugin text, WooCommerce compatibility, and complex multilingual setups including right-to-left languages. It integrates with translation services for professional translations and provides detailed control over which content is translated and how. The trade-off is that it is one of the heavier plugins in terms of database queries and can affect site performance if not configured carefully on large sites.

Polylang is a lighter-weight alternative that handles the core multilingual functionality with less overhead. For sites that do not need the full feature set of WPML, it performs the translation management role with a smaller performance impact. It has a free version with meaningful functionality, making it a reasonable starting point for simpler multilingual projects.

The choice between them depends on the complexity of the site, the WooCommerce integration requirements, and the translation workflow the client intends to use. A site with a small number of static pages in two languages has different requirements from a WooCommerce store selling products across five European markets with different pricing, VAT rates, and payment gateway requirements for each.

Hreflang Implementation

Hreflang is the HTML attribute that tells search engines which language and regional version of a page to serve to which users. Correct hreflang implementation is essential for multilingual SEO and is one of the areas where multilingual sites most commonly have errors.

Each page in a multilingual site should include hreflang tags pointing to all other language versions of that page, including itself. A page that exists in English, French, and German needs hreflang tags for all three versions on every version of the page. Missing or incorrectly formatted hreflang tags result in search engines potentially serving the wrong language version to users or treating the different language versions as duplicate content.

Both WPML and Polylang handle hreflang generation automatically when configured correctly, but the automatic implementation should be verified rather than assumed. Common errors include missing x-default tags, hreflang tags that point to redirected URLs rather than canonical URLs, and hreflang implementations that do not match the URL structure being used.

Rank Math and Yoast SEO both provide additional hreflang management capabilities when used alongside multilingual plugins. The important thing is to ensure that the SEO plugin and the multilingual plugin are configured to work together correctly rather than generating conflicting markup.

Content Strategy and Translation Quality

The technical implementation of a multilingual WordPress site is the more straightforward part of the project. The content strategy is where many multilingual sites fail to achieve their intended purpose.

Machine translation has improved significantly and for some content types it produces acceptable results. For commercial content, particularly the service descriptions, product copy, and conversion-focused pages that are most important to the business, machine translation is rarely sufficient without human review and editing. Text that reads awkwardly or contains culturally inappropriate phrasing undermines the credibility that the multilingual site is intended to build.

The ongoing translation workflow is a consideration that is often underestimated at the planning stage. Adding a new blog post or product page to a multilingual site means producing translated versions of that content, which takes time and carries a cost. Sites that launch with comprehensive translated content and then fail to maintain the translations end up with language versions that are outdated compared to the primary language version. This creates a worse experience than having no translation at all.

A realistic content strategy for a multilingual site should include clear ownership of the translation process, a defined workflow for new content, and honest decisions about which content genuinely needs to be translated. Not every page on a site needs a translated version. Prioritising the pages that are most important to international users and maintaining those translations properly is more effective than attempting comprehensive translation and failing to keep it current.

WooCommerce and Multilingual eCommerce

Multilingual WooCommerce sites introduce additional complexity beyond the standard multilingual WordPress considerations. Prices, shipping rules, payment gateways, and tax configurations may all vary by market. Currency display needs to match user expectations in each region. Product availability may differ between markets. Customer communications including order confirmations and shipping notifications need to be sent in the customer's language.

WPML has dedicated WooCommerce multilingual support that handles product translation, currency switching, and checkout localisation. The configuration is more involved than a standard multilingual site and should be treated as a distinct project scope rather than an extension of a standard WooCommerce build.

Payment gateway availability varies significantly by country. Stripe and PayPal are available across most markets but local payment methods matter in specific regions. iDEAL is dominant in the Netherlands, Sofort in Germany, and Carte Bancaire in France. A WooCommerce store targeting European markets that only offers international card payment options will underperform against local competitors that support the preferred payment methods of their specific market.

Performance Considerations

Multilingual sites are inherently larger than their single-language equivalents. More pages, more database records, and more plugin overhead all contribute to increased server load and potential performance issues. These should be planned for rather than addressed reactively after launch.

Caching configuration needs to account for language detection to avoid serving cached pages in the wrong language to users. Server-side language detection that operates before the cache is served is generally more reliable than client-side detection, but the specific approach depends on the hosting environment and caching plugin being used.

For sites serving multiple countries, a content delivery network that caches content at edge locations geographically close to each target market reduces latency for international users. This is particularly relevant for sites targeting markets that are geographically distant from the primary hosting location.

Database optimisation becomes more important on multilingual sites because the translation tables used by plugins like WPML add significant database overhead as content volume grows. Regular database maintenance and appropriate indexing are more critical on a large multilingual site than on a comparable single-language site.

Testing Before Launch

Multilingual sites require more thorough testing than single-language sites because there are more combinations of language, URL, and content to verify. A structured testing approach should cover language switching functionality across all pages, correct hreflang implementation verified with Google Search Console after launch, translation completeness for all commercial pages, correct currency display and checkout flow for each market in WooCommerce implementations, and mobile performance for each language version.

The investment in thorough pre-launch testing is justified by the cost and complexity of fixing issues on a live multilingual site, where changes to URL structure or hreflang implementation can affect search rankings across multiple markets simultaneously.