How to Build a Multilingual WordPress Site With WPML: Step-by-Step Setup and SEO

Short answer: WPML is the multilingual plugin for WordPress that lets you translate posts, pages, menus, WooCommerce products, and theme or plugin strings, gives every language its own URL, and adds hreflang tags for search engines automatically. Setup comes down to five stages: add languages, choose a URL format, translate content, translate strings, and place a language switcher. A correctly configured WPML site is indexed separately in each language with no duplicate-content problem.

This guide walks through a WPML installation from scratch, compares the URL structure options and their SEO impact in a table, explains the translation methods (manual, translation editor, automatic translation credits) based on the official documentation, and gives an honest comparison of WPML against Polylang and TranslatePress. It is written for business site owners expanding into a second language, WooCommerce stores selling abroad, and agencies that build multilingual sites for clients.

Key Takeaways

• WPML manages content, menu, product, and string translation from one dashboard and generates a separate URL plus hreflang for each language.
• A subdirectory URL format (site.com/en/) is the most balanced choice for most sites; subdomains and parameters exist for specific reasons.
• You can translate manually, in the translation editor, or with automatic translation credits; automatic translation works well when paired with a review step.
• Polylang and TranslatePress can be enough for simpler projects; WPML pulls ahead when WooCommerce and complex theme compatibility are involved.

What Is WPML and What Does It Do?

WPML (WordPress Multilingual Plugin) is a commercial plugin built to publish an existing WordPress site in more than one language. It keeps a separate copy of every post, page, and product per language; these copies are linked, so when a visitor switches language they land on the matching version of the same content. According to the official WPML getting started guide, the Translation Dashboard lets you translate posts, pages, custom post types, taxonomies, widgets, sidebars, and strings from a single interface.

What sets WPML apart from a "translation plugin" is the management layer. Tools like Google Translate render a page on the fly but never present a separate page to search engines. WPML creates a distinct URL, title, and meta description per language, so your German page is indexed in Germany and your English page in the United States, each with its own identity. The WPML license sold by Karınca Lisans is, as stated on the product page, a genuine license valid for one year and one domain, with automatic updates and all PRO features enabled; if you add your admin details in the order notes, installation is done for you at no charge.

Choosing a URL Structure: Directory, Subdomain, or Parameter?

The URL format is the hardest WPML decision to reverse, because changing it later means redirecting every language. WPML's language URL options page offers three formats. The table summarizes each one's requirements and SEO effect:

Format	Example	Requirement	SEO effect
Directory	site.com/en/	Pretty permalinks + rewrite module	Authority accumulates on one domain; the usual recommendation
Domain / subdomain	site.de or de.site.com	DNS and server configuration	Strong country targeting, but authority is split
Parameter	site.com/?lang=en	No server changes	Works technically; the least preferred

The WPML documentation stresses that you do not need to create real folders for the directory format; the directories are virtual and managed by the plugin. Unless you have a separate brand positioning per country, starting with directories keeps authority on one domain and adds no work on the hosting side.

Step-by-Step WPML Setup

A WPML installation runs in eight steps, from license registration to the language switcher, and the official wizard guides you through most of them:

1. Back up the site: A multilingual setup adds new database tables and links for every piece of content; take a full backup before you begin.
2. Install and register the plugin: Load the WPML core through the OTGS Installer and enter your site key. Registration unlocks updates and add-on components.
3. Set the default and additional languages: The wizard makes the language of your existing content the default; add the others from the list.
4. Pick the URL format: Apply the structure you chose from the table above; for directories, confirm that pretty permalinks are enabled.
5. Choose a translation method: Select "translate yourself," "automatic translation," or "work with translators"; you can change this later.
6. Translate content: Bulk-select pages in the Translation Dashboard and send them to the editor, or translate individual posts via the plus icon next to each one.
7. Translate strings: Use the String Translation component for phrases coming from the theme and plugins, such as "Add to cart" or footer text.
8. Place the language switcher: Add it to the menu, footer, or a widget area, and check the menu translations.

Pages built with Elementor can be translated through WPML in the same workflow. Whether Elementor Pro earns its place in that workflow is the subject of our Elementor Pro review; if you need the license, terms are listed on the Elementor Pro license page.

Translation Methods: Manual, Editor, and Automatic

WPML offers three translation routes, and they can be mixed on the same site. First, manual translation: you write each language version from scratch in the WordPress editor; full control, slowest route. Second, the Advanced Translation Editor: source text on the left, translation on the right, segment by segment, with a glossary and translation memory reducing repetition. Third, automatic translation: according to the official automatic translation documentation, WPML's default engine is Private Translation Cloud; it runs on credits, can translate the whole site in "Translate Everything Automatically" mode, and lets you review translations before publishing.

The credit model comes in two forms: pay as you go or prepaid packages. A certain number of credits is included with the account; how many, and at what rate beyond that, is kept current on WPML's own site, so we do not quote figures here. Our experience: automatic translation saves real time on bulk content such as product descriptions and blog posts, while the homepage, service pages, and legal texts need human review.

WooCommerce: Multiple Languages and Currencies

Making a WooCommerce store multilingual requires WPML's WooCommerce Multilingual component. It translates products, categories, attributes, and the checkout flow, so a visitor stays in their language from product page to order confirmation. The same component also supports defining multiple currencies; configure how exchange rates are updated and whether currency follows language or location according to the official documentation.

The detail stores most often miss is that email templates and payment-gateway texts remain in string translation. If the order confirmation goes out in the wrong language, an overseas customer loses trust, so always scan the "woocommerce" domain in String Translation.

hreflang and SEO Verification

The cornerstone of multilingual SEO is that every language page points to all of its counterparts with hreflang tags. Google's localized versions documentation defines three methods: HTML link tags, HTTP headers, and the sitemap, and treats them as equivalent. The critical rule is that annotations must be bidirectional: if two pages do not both point to each other, the tags are ignored. Google also recommends an x-default value for visitors whose language matches none of your versions.

WPML generates these tags automatically; your job is verification. Open the source of any translated page and check that every language is listed, that URLs are fully qualified (with https), and that x-default is defined. To write titles and meta descriptions per language, an SEO plugin such as Rank Math Pro works alongside WPML, letting you set a separate focus keyword and schema in each language. After the translations go live, creating a separate Search Console property per language is the clearest way to see which market is growing.

WPML vs. Polylang vs. TranslatePress

All three plugins build multilingual sites; the difference lies in management style and scope. Polylang, with its free core, is enough for blogs and small business sites; WooCommerce and some theme or plugin strings require the paid version. TranslatePress uses a click-to-translate approach on the front end that suits less technical users; string management can become unwieldy on large sites. WPML stands out on business and e-commerce projects thanks to the widest theme and plugin compatibility, the Translation Dashboard, translator management, and the WooCommerce Multilingual component. If you are launching a simple two-language blog, starting with Polylang makes sense; with a store, many custom post types, or an agency workflow, WPML saves time. Other plugin licenses are in the WordPress plugins category.

Performance Tips

Because WPML runs extra queries for each language, an uncached site can feel slower. Three measures are enough: use a caching plugin that keeps page cache separate per language, remove languages you do not use, and leave String Translation's automatic scanning on only during setup. Our support team at Karınca Lisans helps dozens of customers a month with WPML installations; the most common problem we see is string translation left in "auto-register" mode, bloating the database and slowing the admin panel. Second is the directory format failing because permalinks were left on "plain"; both are fixed in minutes.

Which Option Should You Choose?

• For a simple two-language blog, start with the free version of Polylang; migrating to WPML later is possible.
• If you translate a business site with custom post types and Elementor templates, WPML's Translation Dashboard cuts the workload.
• For a WooCommerce store selling abroad, WPML plus WooCommerce Multilingual manages the product-checkout-email chain from one place.
• Agencies that build multilingual sites for clients again and again settle on WPML for translator management and the automatic translation workflow.

As of October 2026, the first step toward a multilingual site is deciding on the URL format and taking a backup; after that, activate your WPML license and complete the wizard in the order described here. If you want installation done for you, adding your admin details in the order notes is all it takes.