WordPress cannot handle several languages without a plugin. That choice commits the site for years: switching midway often means redoing every translation. Before comparing tools, you therefore need to answer two questions: who translates, and how Google should find each version.
Two ways to translate
The first approach creates separate content per language: each English page is a real WordPress page, linked to its French version. This is how WPML and Polylang work. The second translates the displayed page, sentence by sentence, from the original version: this is how TranslatePress and Weglot work. The first gives more freedom to adapt content to a market, the second is easier to keep up to date.
The four main plugins
- WPML: the most complete, paid, widespread on large sites and compatible with most themes and WooCommerce. Heavier on the database.
- Polylang: same principle as WPML, with a solid free version. Ideal for a brochure site or a blog run by a small team.
- TranslatePress: translation directly on the rendered page, in a visual editor. Very handy for also translating plugin and theme strings.
- Weglot: an external subscription service, set up in minutes, with machine translation and pricing based on word count.
For the record, the site you are reading runs on TranslatePress in five languages, including an English version served on a separate domain for the UAE market.
Structuring URLs for SEO
Three structures are possible: a subfolder such as /en/, a subdomain such as en.example.com, or one domain per country. The subfolder is the simplest and concentrates the domain's authority. A domain per country sends the strongest local signal, but each domain has to build its own reputation. In every case, also translate the slugs, SEO titles and meta descriptions: an English page with a French URL ranks less well.
Hreflang tags
Hreflang tags tell Google which version to serve depending on the user's language and country. They must be reciprocal: each version lists all the others, itself included, plus an x-default fallback. Good plugins generate them automatically, but check them after any structural change, because a reciprocity error makes Google ignore the whole set.
The classic pitfalls
- Redirecting automatically by IP address: Googlebot mostly crawls from the United States and would only see one version. Suggest the language, do not force it.
- Publishing machine translation without review: it is a starting point, but titles, calls to action and sales pages must be reviewed by someone fluent in the language.
- Forgetting emails, forms and error messages, which stay in the original language.
Frequently asked questions
Which plugin for a WooCommerce shop?
WPML and TranslatePress handle products, variations and order emails well. For multiple currencies, add a multi-currency plugin compatible with the one you choose.
Can I switch plugins later?
Yes, but it is a real migration project: translations are stored differently from one tool to another, and URLs must be kept or redirected so as not to lose the rankings you have earned.
Author
Walid SadfiWalid Sadfi is the founder of Evolurise, a team of engineers deployed on site with its clients: custom development (WordPress, Drupal, React, Laravel), AI agents, DevOps and team training. With 8 years of experience, he supports SMEs and large companies, from understanding the problem to deploying the solution. On this blog he shares practical, field-tested insights.