How to Create a Multi-Language Website in WordPress (Polylang, WPML, TranslatePress)

A multi-language website lets visitors read your content in their own language, which can open new markets and improve conversions. Done properly, each language version can also rank in local Google results. Here is how to set one up in WordPress.

Step 1: Choose a translation plugin

• Polylang: free, lightweight; you write each translation as a linked post or page.
• TranslatePress: free core; translate visually on the front end, with optional automatic translation.
• WPML: paid; broad compatibility with page builders and WooCommerce.

Use only one translation plugin.

Step 2: Choose the URL structure

The SEO-friendly default is a subdirectory per language: yourdomain.com/ for English and yourdomain.com/hi/ for Hindi, for example. Each language version has its own URL, so Google can index it. Avoid setups that switch language with cookies only; search engines cannot see those versions.

Step 3: Add languages and translate

1. In the plugin settings, add your languages and set the default.
2. Translate the most important pages first: home, services, contact, top blog posts.
3. Translate menus, widgets and theme strings (footer text, buttons).
4. Translate SEO titles and meta descriptions too; most plugins integrate with Rank Math and Yoast.

Tip: machine translation is a starting point. Have a fluent speaker review key pages before launch.

Step 4: Add a language switcher

Add the plugin's switcher to the header menu or as a widget. Show language names (English, हिन्दी) rather than only flags, because flags represent countries, not languages.

Step 5: Check hreflang and sitemaps

• View the page source and confirm hreflang tags list each language version.
• Make sure the sitemap includes all languages, then submit it in Search Console.
• Do not automatically redirect visitors based on their location; let them choose, and let Googlebot reach every version.

Common mistakes

• Half-translated pages mixing two languages.
• Translating content but not menus, forms and emails.
• Forgetting to translate the slug, title and meta description.

Planning your site structure first? See building a WordPress website without coding.