All About Multilingual WordPress Sites

Adding a second language to your WordPress site is one of the most direct ways to grow organic traffic, because you’re effectively doubling your keyword coverage. A page optimized in English for “best running shoes” competes in English-language search results only. Add a Spanish version of that same page optimized for “mejores zapatillas para correr” and you enter a completely separate set of search results with less competition and an audience that converts well because you’re speaking their language.

Beyond SEO, there are practical business reasons to go multilingual. If you run a WooCommerce store, serving customers in their own language reduces checkout friction and cart abandonment. If you publish tutorials or documentation, translated content extends its useful life across new markets. Even a basic blog can see engagement lift when readers can follow along in their first language rather than translating mentally as they read.

The WordPress plugin ecosystem makes all of this achievable at different budget levels. Polylang is free and gives you manual control over each translation. WPML is the premium standard for large sites and eCommerce. TranslatePress offers a front-end visual editor. You don’t need a translator on retainer to start – machine translation through DeepL or Google Translate is available through most of these plugins and is accurate enough for informational content.

Which plugin should you pick? Polylang is the best free starting point: you translate each post and page by hand, which keeps quality high on a smaller site. WPML is the paid standard for large or WooCommerce sites, with built-in translation management and string handling for plugins and themes. TranslatePress lets you edit translations visually on a live preview of the page, which suits anyone who wants to see context while they work. Weglot is a hosted service that translates the whole site automatically for a monthly fee, useful when you need several languages live quickly and do not mind the ongoing cost. For most blogs and small business sites, start with Polylang and only move up if you outgrow it.

This guide uses Polylang, the most widely used free multilingual plugin for WordPress. The steps below take you from a standard WordPress site to one that serves content in two languages. The same general process applies to other plugins, though menu locations and terminology will differ.

First, Choose Your URL Structure

Decide how the translated pages will sit in your URLs before you add a language, because changing it later means setting up redirects. There are three options. A subdirectory like example.com/es/ is the Polylang default, the simplest to run, and keeps all your authority on one domain, which is why it suits most sites. A subdomain like es.example.com separates each language but splits some of your SEO signals. Separate country domains like example.es send the strongest local signal to Google but mean running several sites at once, so they only pay off for businesses seriously targeting multiple countries. When in doubt, use the subdirectory option.

Step 1. Use a Compatible WordPress Theme

Most well-maintained WordPress themes work with multilingual plugins, but check that your theme has been tested with Polylang or WPML before you start. Themes built around shortcodes or custom post types sometimes have compatibility issues. Themes with active installations and recent updates in the WordPress.org repository are generally safe.

Step 2. Install and Configure Polylang

Go to Plugins > Add New, search for Polylang, install and activate it. After activation, Polylang adds a Languages menu to your sidebar. Open it and click the Languages tab. Use the dropdown to select your second language (for example, Spanish) and click Add Language. Polylang immediately creates a parallel URL structure for that language, typically example.com/es/ for Spanish content.

Step 3. Set Up the Language Switcher

Go to Appearance > Widgets and add the Polylang language switcher widget to a sidebar or footer area. This gives visitors a visible way to switch languages. Alternatively, under Languages > Settings in Polylang, you can enable a floating language switcher or add one to your navigation menu via Appearance > Menus.

Step 4. Translate Your Content

Open any page or post. In the editor sidebar, you’ll see a Languages meta box with a flag for each active language. Click the plus icon next to the language you added to create a translation of that content. Polylang opens a duplicate editor where you can type or paste the translated version. For machine translation assistance, connect through a service like DeepL API. Polylang’s settings page has integration options.

Step 5. Translate Your Menus and Strings

Go to Appearance > Menus and create a second menu in your new language. Under Languages > Translations in Polylang, you can also translate theme strings (like the tagline and widget titles). This ensures visitors in each language see a fully localized experience, not just translated page content with English buttons and navigation.

Troubleshooting: Translated Pages Not Appearing in Google

If your translated pages aren’t getting indexed or don’t appear in search results for the target language, these are the most common causes:

• Missing hreflang tags: Check your page source for hreflang attributes in the <head> section. Polylang generates these automatically when configured correctly. If they’re absent, re-check the plugin’s language settings and make sure each post has an associated translation, not just the language assigned without a translation page.
• Wrong URL structure selected after content was created: If you changed the URL structure after adding content, old URLs may not redirect correctly. Use Search Console’s URL Inspection tool to confirm the translated URL is crawlable.
• Machine translation flagged as thin content: Google can detect pages translated purely by machine with no human review. For pages that drive conversions or serve as primary entry points, add a human review pass before relying on them for organic traffic.
• Multilingual plugin settings affecting crawlability: Some configurations hide languages from search engines or block crawling of certain language versions. Check Settings > Reading in WordPress and confirm the site is not set to discourage search engines.

The most common mistake is translating page content but forgetting the surrounding interface. Visitors who switch to Spanish and still see an English-language navigation menu, English widget text, and English category names feel a jarring inconsistency. Translation plugins handle page and post content well, but menus, widgets, and theme strings often need to be translated separately through the plugin’s string translation panel.

A second mistake is using automatic translation without review. Machine translation through DeepL or Google Translate is useful for getting a rough version live quickly, but it makes errors with idioms, product descriptions, and technical content. For any page that affects purchasing decisions or user trust, have a native speaker review the translation before publishing.

Third: ignoring hreflang tags. These HTML attributes tell Google which version of a page is intended for which language and country, preventing duplicate content issues. Most multilingual plugins generate hreflang tags automatically when configured correctly. Check your site’s source code after setup to confirm the hreflang tags are present. They should appear in the head section of each page.

Fourth, many site owners skip translating their SEO metadata. The page title and meta description in your second language need to be written in that language for those pages to rank in foreign-language search results. Plugins like Polylang and WPML let you set separate Yoast SEO metadata for each language version of a post or page.

Fifth: building out all languages before deciding which ones actually matter for your audience. Translating into five languages at launch sounds thorough, but it creates five times the maintenance burden. A better approach is to add one language, confirm it generates traffic and engagement after 60 to 90 days, and only then expand. Google Analytics segments by user language so you can see which languages your existing visitors already use. Start there before adding any new ones.

Sixth: neglecting page speed on translated versions. Some multilingual plugins generate additional database queries for each language check, which can slow page loads if your hosting environment is already under strain. After enabling multilingual support, run your translated pages through a speed test to confirm load times haven’t increased significantly. If they have, adding a page caching plugin usually resolves it.