When a business starts attracting visitors from other countries, offering the website in their language is a natural next step. People are more comfortable reading and buying in their own language, and translated pages can rank in local search results that an English-only site would never reach.
But multilingual sites bring complexity that many owners underestimate. Every page, menu, form, email and product needs translating. Every new piece of content multiplies the work. Search engines need clear signals about which page serves which audience. And the plugin or structure you choose at the start is hard to change later.
I’ve built and maintained multilingual WordPress sites for several clients. Here’s how I approach the main decisions.
Translation versus localisation
Before choosing tools, understand what you’re actually doing.
Translation converts text from one language to another.
Localisation adapts the whole experience for a market: currency, date formats, measurement units, legal information, payment methods, cultural references, images and even which products or services you offer.
A site for customers in Germany might need prices in euros, German legal pages, different shipping options and examples that make sense locally. Simply translating the English site often isn’t enough.
Decide early whether you’re translating content for a language audience, or building localised experiences for specific countries. It affects your structure.
Choosing a URL structure
There are three main ways to organise languages in URLs.
Subdirectories
example.com/de/, example.com/fr/
- All languages on one domain, sharing its authority.
- Simple to set up and maintain on a single WordPress installation.
- The most common choice for multilingual WordPress sites.
Subdomains
de.example.com, fr.example.com
- Somewhat more separation between languages.
- Can be hosted separately if needed.
- Slightly more setup, especially for SSL and analytics.
Country-code domains
example.de, example.fr
- Strongest signal that a site targets a specific country.
- Each domain builds authority separately.
- Most expensive and complex to manage, with separate domain registrations and often separate sites.
For most businesses, subdirectories offer the best balance of simplicity and SEO strength. Country-code domains make sense for large businesses with significant, distinct operations in each country.
Avoid using URL parameters like ?lang=de for languages. They’re harder for search engines and users to work with.
Single site or Multisite?
Single site with a translation plugin
All languages live in one WordPress installation. A plugin links translations together and switches languages. It’s easier to manage, especially for smaller sites, and content relationships between languages are handled by the plugin.
WordPress Multisite
Each language is a separate site in a network. This gives more independence: different plugins, different content structures and separate editors per language. It suits large organisations where each language team works independently, or where language sites differ significantly. Linking translations across sites requires a plugin designed for Multisite multilingual setups.
For most businesses, a single site with a reputable translation plugin is the practical choice.
Choosing a translation plugin
Several established plugins handle multilingual WordPress, such as WPML, Polylang and TranslatePress, each with different approaches and pricing. When comparing, consider:
- How translations are stored. Some create separate posts for each language, linked together. Others store translations of strings and render them dynamically. This affects performance, compatibility and how easy it is to remove the plugin later.
- Editing experience. Some translate in the normal WordPress editor, others offer a visual front-end translation interface.
- Compatibility with your theme, page builder, WooCommerce, forms and SEO plugin.
- String translation for theme and plugin text, like buttons and labels.
- Machine translation integration, if you want automatic first drafts.
- Performance impact on large sites.
- Cost, including any per-word charges for machine translation.
Test your shortlisted plugins on a staging copy with your actual theme and key plugins before committing. Switching translation plugins after hundreds of pages are translated is painful.
Human versus machine translation
Machine translation has improved enormously and is useful for first drafts, internal content and getting a large volume of pages translated quickly. But for important pages, like your homepage, service pages, product descriptions and legal content, human review matters.
Machine translation can:
- Miss tone and brand voice.
- Mistranslate industry terms or product names.
- Produce text that’s technically correct but sounds unnatural to native speakers.
- Get legal and safety information dangerously wrong.
A practical approach is machine translation for a first draft, followed by review and editing by a fluent speaker, ideally someone who knows your industry. For key marketing pages, consider professional translation from the start.
Search engines have also become better at recognising low-quality, unreviewed automated content. Pages that read poorly are less likely to rank and less likely to convert.
International SEO and hreflang
When you have the same content in several languages, search engines need to know which version to show to which users. That’s what hreflang annotations do.
hreflang tells search engines that pages are equivalent versions in different languages or for different regions:
Key rules:
- Annotations must be reciprocal. Each page must reference all its alternatives, including itself.
- Use correct codes. Language codes like de, or language plus region like de-AT for German speakers in Austria.
- Include x-default for the version to show when no language matches, often a language selector or the main language.
- Point to canonical URLs, not redirected or noindexed pages.
Good translation plugins generate hreflang automatically. Check the output, because misconfigured hreflang is one of the most common international SEO problems.
Translate SEO elements too
Each language version needs its own:
- Page titles and meta descriptions.
- URL slugs in the local language, where appropriate.
- Image alt text.
- Structured data in the right language.
Do keyword research in each language rather than translating English keywords directly. People in different countries often search using different terms.
Don’t auto-redirect by location
Automatically redirecting visitors based on their IP address or browser language can stop search engines from crawling all versions, because crawlers often come from one location. It also frustrates users who prefer a different language. Instead, suggest the appropriate language with a banner or offer a clear language switcher, and let users choose.
The language switcher
Make it easy for visitors to switch languages:
- Place the switcher in a consistent, visible location, like the header.
- Show language names in their own language, like Deutsch and Français, rather than flags alone. Flags represent countries, not languages.
- Link to the equivalent page in the other language, not the homepage.
Multilingual WooCommerce
Multilingual stores add more complexity:
- Product names, descriptions, attributes and categories need translating.
- Checkout fields, emails and account pages need translating.
- Currency may need to change by market, requiring a multi-currency solution.
- Tax, shipping and payment methods may differ by country.
- Stock should be shared across translations of the same product.
Make sure your translation plugin explicitly supports WooCommerce, and test the complete purchase flow in every language, including emails.
Forms and emails
Forms, confirmation messages and notification emails are easy to forget. A customer who fills out a German form and receives an English confirmation has a jarring experience. Check that your form plugin integrates with your translation plugin, and translate all system emails, including WordPress and WooCommerce emails.
Performance considerations
Translation plugins add database queries and processing. On large sites with many languages, this can affect performance. Use page caching, which works well with language subdirectories, and a persistent object cache. Test performance with all languages active.
Maintaining a multilingual site
The ongoing work is often bigger than the initial translation:
- Every new page or post needs translating.
- Every update to existing content needs updating in every language.
- Outdated translations confuse visitors and harm credibility.
Plan a workflow: who translates, who reviews and how updates are flagged. Some translation plugins mark translations as needing updates when the original changes. Start with fewer languages done well rather than many languages poorly maintained.
Frequently asked questions
Which URL structure is best for SEO?
All three can work well. Subdirectories are the simplest and keep authority on one domain, which is why they’re the most common choice. Country-code domains give the strongest country signal but require more investment.
Can I just use automatic translation widgets?
Browser-based or widget translations that translate pages on the fly aren’t indexed as separate language pages, so they don’t help international SEO. They can be a convenience for visitors, but they’re not a substitute for proper translated pages.
Do I need hreflang if my languages are clearly different?
It’s still recommended. hreflang helps search engines show the right version, especially for similar languages or regional variants, and reduces the chance of the wrong version ranking.
How many languages should I start with?
Start with the languages where you have real demand and the capacity to maintain quality content. Adding languages later is easier than maintaining many poorly.
Final thoughts
A multilingual WordPress site can open genuine new markets, but it’s a long-term commitment. Choose a URL structure and translation plugin carefully, test them with your real setup, invest in quality translation for important content, implement hreflang correctly and plan how translations will be maintained. Done properly, your site will speak to customers in their own language, and they’ll respond.
