WPML costs money. It handles complex multilingual sites with the least manual work. Polylang is free. It works well for a smaller site with two or three languages. A custom-built multilingual system only makes sense in narrow cases, when neither plugin fits your content structure. Most businesses expanding into new regional or export markets can start with WPML or Polylang. Very few genuinely need a custom build. This guide breaks down what each option costs, what it takes to maintain, and how to decide without guessing.
Why a Multilingual Website Matters for Growing Businesses
A business that sells only in one language limits itself to one audience. An export-focused manufacturer loses buyers who can’t read the product pages. A tourism business courting international visitors loses bookings the same way. A multilingual website removes that barrier. It also signals seriousness. A buyer in France trusts a site with a proper French version more than one running through a browser’s auto-translate tool.
Many businesses treat “multilingual” as a checkbox. They add a translate widget and call it done. Real multilingual setup means something different. It means separate, properly translated content for each language. It means correct URL structure. It means search engines that can find and rank each language version on its own.
WPML: The Full-Featured Paid Option
WPML is the most widely used premium multilingual plugin for WordPress. It costs roughly $39 to $199 a year, depending on the plan. Renewal fees keep the plugin updated and supported.
What WPML Handles Well
WPML translates posts and pages. It also translates menus, widgets, and WooCommerce products. It covers most theme and plugin strings too. It integrates with major page builders, including Elementor. It supports professional translation services directly inside the plugin. You can send content out for human translation without leaving WordPress. For a business with 10 or more pages and an active blog, this integration saves real time.
Where WPML Costs Add Up
The license fee is only part of the cost. WPML adds real overhead to page load time. It also adds overhead to database size, especially with many languages active. Some premium themes and plugins need a separate compatibility check before they work correctly with WPML. Budget a few extra hours for setup and testing beyond the plugin price itself.
Polylang: The Free Alternative With Real Limits
Polylang’s free version covers the basics. It translates posts, pages, and categories. It gives you a clean admin interface for switching between languages while editing.
What Polylang Does Well
For a site with straightforward content and two or three target languages, Polylang does the job. It carries no recurring plugin cost. It’s also lighter on server resources than WPML, which matters on budget hosting.
Where Polylang Falls Short
The free version skips translation management workflow entirely. You translate everything manually, one field at a time. WooCommerce and advanced e-commerce translation require the paid Polylang Pro add-on. That add-on narrows the price gap with WPML considerably. Complex sites with heavy custom fields sometimes hit compatibility gaps too. WPML tends to handle those gaps more gracefully.
SEO Handling: hreflang Tags and Duplicate Content
Search engines need a clear signal about which language version to show which visitor. That signal is the hreflang tag. It sits embedded in each page’s HTML head. Both WPML and Polylang generate these tags automatically, once configured correctly. Skip this step, and search engines may treat your English and French pages as duplicate content. They might also show the wrong version to the wrong audience.
A properly configured multilingual site needs distinct URLs per language too. Most sites use subdirectories, like site.com/fr/. Some use separate subdomains instead. Both plugins support subdirectory structure out of the box. Subdomains and separate domains per language need more manual DNS and server configuration. Most small and mid-sized businesses don’t need that added complexity.
When a Custom Multilingual Build Actually Makes Sense
A custom solution earns its cost in a narrow set of cases. A headless architecture querying WordPress purely as a content API is one. A site with an unusual content model that no plugin cleanly supports is another. A business already running custom post types deep enough that plugin compatibility becomes a constant fight fits too. Outside these cases, a custom build usually costs more than either plugin’s lifetime license fees combined. It ends up doing the same basic job at a higher price.
We worked with a Kolkata-based home décor exporter who needed English and French storefronts on the same WooCommerce catalog. Their first instinct was a fully custom multilingual build. That quote came in at nearly three times what WPML plus setup time actually cost. WPML’s WooCommerce integration handled their product catalog, including variable products, without any custom code. The lesson holds beyond this one case: check whether an existing tool already solves your specific problem before assuming you need something built from scratch.
Cost Over Three Years: A Realistic Comparison
Polylang’s free tier costs nothing over three years, assuming you don’t need WooCommerce translation. WPML’s mid-tier plan runs roughly $99 a year, or about $300 over three years, plus setup time. Polylang Pro, needed for serious eCommerce translation, costs less than WPML but still carries an annual fee. A custom build, even a modest one, commonly starts at ten times WPML’s three-year cost, before counting ongoing maintenance as your site grows. Run these numbers before assuming “custom” means “better.”
A Practical Decision Framework
Choose Polylang if you run a smaller site, sell nothing that needs translation, and want to avoid a recurring plugin cost. Choose WPML if you run WooCommerce, need professional translation workflow tools, or plan to add more languages over time. Consider a custom build only after testing both plugins on a staging site first. Move to custom only if you find a genuine, specific gap neither plugin closes.
Test any option on a staging copy of your site before committing. Translation setup that looks simple on paper sometimes reveals plugin conflicts once real content goes in. It’s far cheaper to catch that on staging than on your live site.
Machine Translation vs Human Translation
Both plugins now offer machine translation shortcuts, often powered by DeepL or Google Translate. Machine translation is fast and nearly free. It works fine for internal notes or a quick draft to review. It rarely works as your final published content. Product descriptions, service pages, and anything customer-facing deserve a human pass, even if machine translation creates the first draft.
A hybrid workflow works best for most businesses. Use machine translation to generate a starting draft. Send that draft to a native speaker for editing rather than translation from scratch. This cuts human translation time significantly, while avoiding the awkward phrasing that pure machine output leaves behind on a public-facing page.
Common Setup Mistakes to Avoid
Businesses new to multilingual WordPress make a few predictable mistakes. They translate the homepage and a few key pages, then leave older blog posts in the original language only, creating an inconsistent experience for visitors browsing in their chosen language. They forget to translate SEO fields like meta titles and descriptions, so search results show the wrong language snippet even when the page itself is translated. They also skip testing the language switcher on mobile, where a poorly styled dropdown can make switching languages nearly impossible for a visitor on a phone.
Catch these early. Audit every page type, not just top-level pages, before considering a multilingual rollout finished. A partially translated site often looks worse to visitors than a single-language site handled well.
Budgeting for Ongoing Content, Not Just the Initial Setup
The initial translation is only the starting cost. Every new blog post, product, or landing page you publish afterward needs translation too, and that ongoing work often exceeds the original setup cost within the first year. Build translation into your regular content workflow from day one. Assign it to a specific person or vendor, and set a clear turnaround expectation, rather than letting translated content quietly fall behind the English version as your site grows.
A site with a French version that’s six months out of date looks worse to a French visitor than a site with no French version at all. Partial, stale translation undermines the trust a multilingual site is supposed to build in the first place.
Frequently Asked Questions
Can I switch from Polylang to WPML later without starting over?
Yes, but expect manual work. Neither plugin offers a clean one-click migration path to the other. Budget time to re-link translated content and re-check hreflang output after switching.
Does a multilingual site slow down my WordPress site?
Any translation plugin adds some overhead. It stores and queries extra content per language. Good hosting and caching keep the impact small. WPML tends to add more overhead than Polylang on larger sites.
Do I need separate hosting for each language?
No. Both plugins run every language from the same WordPress installation and database. They use either subdirectories or subdomains for the URL structure.
How long does it take to add a second language to an existing site?
For a 10 to 15 page business site, expect one to two weeks. That’s once translated content is ready, including plugin setup, hreflang configuration, and testing.
If you’re planning a multilingual expansion and want a setup that matches your actual content and budget, see what our CMS development services cover, or get in touch to talk through your specific requirements.
