Technical SEO
WordPress Multilingual SEO: Hreflang and Translation Plugins Compared (WPML, Polylang, TranslatePress, Weglot)
The plugin decides your URL structure, hreflang output and how translations are stored. Choose with those in mind, not just price.
WordPress has no built-in multilingual system, so plugins fill the gap. The leading options differ in where translations live (in your database or a hosted service), how URLs are structured and how much control you get over hreflang.
Google’s requirements are the same whatever you use: separate URLs per language, one language per page, hreflang with return links and no automatic redirects by language.
Short answer: For WordPress multilingual SEO, choose a plugin that creates separate URLs per language (subfolders like /fr/ are simplest), outputs correct hreflang with self-references, return links and x-default, translates titles, meta descriptions, slugs and structured data, and adds translated pages to sitemaps. WPML and Polylang store translations as WordPress content; TranslatePress translates on the front end and stores translations in your database; Weglot is a hosted service. Avoid running two plugins that both output hreflang, and test with URL Inspection after setup.
Key Takeaways
- Separate URLs per language are required.
- Check hreflang output, including return links and x-default.
- Translate SEO fields and slugs, not just body text.
- Only one plugin should output hreflang.
- Hosted translation services add a dependency.
What to compare
| Factor | Why it matters |
|---|---|
| URL structure options | Subfolders, subdomains or separate domains per language |
| Hreflang output | Correct codes, self-reference, return links, x-default |
| SEO plugin integration | Translated titles, descriptions, canonicals and sitemaps in Rank Math or Yoast |
| Where translations are stored | In WordPress (portable) or a hosted service (subscription dependency) |
| Machine translation and review workflow | Quality control before publishing |
| Performance impact | Extra queries or scripts on every page |
How the main plugins differ
- WPML: paid; translations are separate posts and terms, with broad theme and plugin compatibility.
- Polylang: free core with a paid Pro version; translations are separate posts linked as language versions.
- TranslatePress: translate visually on the front end; translations stored in your database.
- Weglot: hosted translation service; translations served via the service, with subscription tiers by word count.
Check each plugin’s current documentation for features, since they change often.
Setup checks
- Language versions on separate URLs, each in one language.
- Hreflang tags list every version plus itself, with GB not UK for Britain.
- Translated slugs, titles, descriptions and image alt text.
- Sitemaps include each language version.
- No automatic redirect by browser language; a visible language switcher instead.
- Validate with URL Inspection and the hreflang guide.
Frequently asked questions
Can I use machine translation?
As a starting point, with human review. Google’s guidance on generative AI content applies to translations made to manipulate rankings.
Do I need hreflang with only two languages?
It’s still recommended so Google shows the right version.
Can I switch plugins later?
Yes, but it’s a migration: keep URLs or redirect them, and check hreflang afterwards.
Expanding into other countries?
We plan language and country targeting, implement hreflang correctly and avoid duplicate-content problems across markets.
Sources
- Google Search Central: Tell Google about localized versions of your page
- Google Search Central: Managing multi-regional and multilingual sites
- Google Search Central: Guidance on using generative AI content
Last reviewed October 19, 2026.
Table of Contents
Need Technical SEO Help?
We find what stops Google from crawling and indexing your important pages, and fix the cause.
Related Guides
Free SEO Audit
A manual on-page and technical SEO review of your website, with prioritized fixes.