Website Development

WordPress Multilingual Sites: WPML, Polylang, and Multilingual SEO Setup

A multilingual WordPress site opens markets a single-language site cannot reach. Here is the complete guide — from choosing your plugin to getting...

Athar Ahmad
Reviewed by Athar AhmadFounder & CEO · Written by the SA Solutions team
Published March 22, 2026 Updated October 17, 2026 5 min read
On this page
  1. The multilingual approach: translation plugins vs multisite
  2. WPML — the premium multilingual standard
  3. Polylang — the free alternative
  4. Setting up a multilingual WordPress site with Polylang
  5. Multilingual SEO — what you must get right
  6. Translation workflow
  7. Need a multilingual WordPress site built and configured?
  8. Frequently asked questions

A multilingual WordPress site opens markets a single-language site cannot reach. Here is the complete guide — from choosing your plugin to getting hreflang right.

  • WPML — 1M+ sites — multilingual standard
  • Polylang — free alternative with strong community
  • hreflang — critical for multilingual SEO
  • Site.com/fr/ — directory prefix — most SEO-friendly URL structure

A multilingual WordPress site can access markets that a single-language site cannot reach. Whether you are expanding into new countries, serving a multilingual community, or meeting legal requirements for content in multiple languages, WordPress supports every multilingual configuration — with or without specialist plugins.

The multilingual approach: translation plugins vs multisite

Approach How it works Best for
Translation plugin (WPML, Polylang) Single WordPress install; each post/page has language variants Most sites — simplest to manage
WordPress Multisite Separate sub-site per language (en.site.com, fr.site.com) Large sites with genuinely distinct content per language
Separate installs Completely independent WordPress sites per language Maximum independence; most management overhead
Automatic translation only Machine-translated content, no human review Never recommended — harms SEO and credibility

WPML — the premium multilingual standard

WPML (WordPress Multilingual Plugin) is the most widely used multilingual plugin for WordPress, with over 1 million active installations. It supports every content type including custom post types, taxonomies, WooCommerce products, and Elementor page builder layouts.

  • Price: from $39/year (Multilingual Blog) to $199/year (CMS plan with WooCommerce support)
  • Translates posts, pages, custom post types, taxonomies, menus, widgets, and theme strings
  • Integrates with Elementor, Divi, Beaver Builder, and Gutenberg for visual translation editing
  • WooCommerce multilingual: translates products, variations, attributes, and checkout
  • Language switcher widget, shortcode, and automatic menu integration
  • Compatibility tested with hundreds of WordPress plugins

Polylang — the free alternative

Polylang is a free multilingual plugin with strong community support. It handles the most common multilingual requirements — post and page translation, multilingual menus, and language switching — without the premium cost of WPML.

  • Price: free core; Polylang Pro from $99/year for WooCommerce support and theme string translation
  • Translates posts, pages, categories, tags, and menus
  • Language detection: automatically redirects visitors based on browser language preference
  • Compatible with most major WordPress plugins
  • For WooCommerce multilingual support, Polylang Pro or the Lingotek translation add-on is required

Setting up a multilingual WordPress site with Polylang

Install and activate Polylang

Go to Plugins › Add New, search ‘Polylang’, install and activate the free plugin.

Configure your languages

Go to Languages › Languages. Add your primary language and all additional languages. Set your primary language as the default.

Set URL structure

Choose how language URLs are structured: a directory prefix (site.com/fr/page), a subdomain (fr.site.com), or a different domain per language. The directory prefix is the most SEO-friendly and simplest to configure.

Add the language switcher

Go to Appearance › Widgets and add the Polylang Language Switcher widget to your header area, or use the Polylang shortcode in your navigation menu.

Create translations for each post and page

Open any post or page. The Polylang panel on the right shows language status. Click the + next to each language to create the translation. Translate title, content, and meta description for each language variant.

Configure hreflang tags

Polylang automatically adds hreflang tags to the head of each page — these tell Google which language version to show to which users. Verify they are present by viewing the page source and checking for rel=’alternate’ hreflang tags.

Multilingual SEO — what you must get right

Multilingual SEO is significantly more complex than single-language SEO. The critical requirements:

  • Hreflang tags: tell Google which language/country version to serve to which users. Without correct hreflang implementation, Google may serve the wrong language version or treat language variants as duplicate content. Both WPML and Polylang handle hreflang automatically.
  • Separate URL per language: each language version must have its own URL (site.com/fr/ not ?lang=fr). Query-string language switching is not reliably indexed by Google.
  • Translate meta titles and descriptions: do not leave English meta titles on French pages. Every page’s meta title and description must be in the page’s language.
  • Submit language sitemaps to Search Console: WPML and Polylang generate language-specific sitemaps. Submit each to Google Search Console as a separate property or as sitemap entries under the main property.
  • Avoid machine translation for ranking content: Google can detect machine-translated content and may not rank it well. Invest in professional human translation for your highest-value pages at minimum.

Translation workflow

For most sites, the practical translation workflow is:

  • Translate core pages (Homepage, About, Services, Contact, Pricing) yourself or with an agency — these are high-value and need accurate human translation
  • Use a service like Weglot (translation-as-a-service) or WPML’s built-in translation management to order professional translations directly from WordPress
  • For blog content: prioritise translating your highest-traffic posts rather than translating everything — machine translate the rest with human review if budget allows
  • Establish a process for keeping translations in sync when the original-language content updates

Need a multilingual WordPress site built and configured?

Simple Automation Solutions builds multilingual WordPress sites with WPML or Polylang, hreflang configuration, and multilingual SEO setup for businesses worldwide.

Book a Free Call View Our Work →

Frequently asked questions

Does a multilingual WordPress site rank in multiple countries? +

Yes, when configured correctly. Separate language URLs with correct hreflang tags allow Google to serve the appropriate language version to users in different countries or speaking different languages. A site with English and French versions, correctly configured, can rank in both English and French search results independently. The quality and completeness of each language’s content determines its ranking potential in that language’s search results.

How much does translating a WordPress site cost? +

Professional human translation costs approximately $0.08-0.15 per word. A typical business website with 5,000 words of content costs $400-750 to translate into one language. WPML’s Translation Management module allows ordering translations from professional translators directly within WordPress. Weglot offers a SaaS-based translation service starting at €15/month that handles automatic translation with human editing. Machine translation via DeepL API is the most affordable option but requires human review for customer-facing content.

Can I translate only some pages of my WordPress site? +

Yes. WPML and Polylang allow you to translate specific pages and leave others untranslated. Untranslated pages are typically hidden from the language version’s navigation or shown in the original language as a fallback. For most sites, it is better to translate all key pages and leave only lower-priority content (old blog posts) untranslated rather than presenting a site that is partially translated — partial translations can undermine the credibility of the localised experience.

Athar Ahmad
Athar AhmadFounder & CEO, SA Solutions · Certified Bubble.io Developer

Athar has spent more than 8 years building digital products and leads every SA Solutions project, from Bubble.io apps to AI automation for small and growing businesses. Read our editorial standards.

Other posts

Need help with your website or app?

Book a free 30-minute call and get honest advice and a clear next step.

Book a free callSee our services