Site features integration · Updated November 15, 2026

WPML integration

We set up WPML on WordPress sites that need English and French, including string translation, WooCommerce, hreflang and /fr/ URLs. We also build bilingual sites on the CMS's own localization (Sanity, or Polylang and multisite on WordPress), with no translation plugin subscription to renew.

Rated 5.0 out of 5,72 Google reviews

WPML at a glance

Connects
Posts, pages, menus, theme and plugin strings, WooCommerce, SEO plugins and automatic translation.
WordPress
WPML itself: a paid plugin, with String Translation and WooCommerce on the CMS plan and up.
Webflow
Not available. WPML is WordPress-only; Webflow uses its Localization add-on or Weglot.
Astro or Next.js with Sanity
Not available. Sanity's document- or field-level localization does the same job.
Custom software
Not available. Locale routing and translation tables go into the app itself.
Complexity
Medium. The work is in page builder content, strings and the URL format.
Typical setup
3 to 6 days on an existing site, not counting translation.

How we connect WPML

  • WordPress

    As of November 15, 2026, WPML lists Multilingual Blog at €39, Multilingual CMS at €99 and Multilingual Agency at €199, each with a year of updates and support. Blog leaves out String Translation, WooCommerce support and automatic translation, so most business sites need CMS, which covers three production sites and 22,500 AI translation words. Without renewal WPML keeps running but gets no updates. The purchase page doesn't list renewal prices.

  • Webflow

    WPML is a WordPress plugin, so it doesn't run on Webflow. Webflow's own option is Localization, a paid add-on: as of November 15, 2026, Webflow lists Essential at $9 a month per locale (up to 3 locales, 10,000 AI-translated words a month) and Advanced at $29 per locale, which adds localized URL slugs. Weglot is the other common route.

  • Astro or Next.js with Sanity

    WPML has no role here. We model French in Sanity instead: document-level localization, where each language is its own document published on its own schedule, for pages and articles, and field-level localization for shared items like a staff directory. Astro or Next.js routes the /fr/ pages and writes hreflang and lang attributes. There's no translation plugin to renew.

  • Custom software

    WPML isn't available outside WordPress. In a custom app we keep translations in the database or in locale files, route /fr/ paths in the app and send copy to translators as XLIFF or a spreadsheet. A marketing site can stay on WordPress with WPML while the app keeps its own French strings.

What organizations use WPML for

  • French kept by your own translators

    WPML's Translations Dashboard sends pages to in-house translators or a translation service and tracks each job. Automatic translation can write a first draft that a person edits in the Advanced Translation Editor, with a glossary and translation memory. Menus are translated by hand. We set up the workflow and train whoever owns the French.

  • WooCommerce in two languages

    WPML Multilingual & Multicurrency for WooCommerce comes with the CMS and Agency plans. It translates products, categories, cart, checkout, account pages and order emails, and can price in CAD and USD by hand or by exchange rate. We test checkout and emails in French before launch, because that's where untranslated text shows up.

  • Theme and plugin text

    Form labels, error messages, widget titles and button text sit outside posts, so String Translation handles them. Admin texts, such as a footer copyright line, need its scanner. We register these strings during the build.

What to watch out for

  • Performance cost

    WPML says it has a negligible effect on speed, but every translated page adds database work, and its docs warn that detecting strings in JavaScript files can affect performance. We switch that detection off after scanning, use page caching and measure the French pages, not only the English ones.

  • Page builders and URL format

    WPML supports Elementor and Beaver Builder, but its forum has reports of Bricks pages translating only the title. Directory URLs (/fr/) need pretty permalinks and WPML's own rewrite rules; separate domains need DNS and server setup. We choose the URL format before translating, because changing it later means redirects.

  • Automatic translation costs and data

    Past the included words, automatic translation is pay as you go: as of November 15, 2026, the first 500 words a month are free, then €3.00 down to €0.40 per 1,000 words, before VAT. Source text goes to WPML's translation service. The translated pages are stored in your WordPress database, on your own host.

Sources

Checked against WPML's docs on November 15, 2026.

  1. WPML purchase plans, included words, refunds
  2. Automatic translation pricing pay as you go and prepaid words
  3. Language URL options directories, domains, parameter
  4. Adding hreflang tags in WordPress
  5. WPML Multilingual & Multicurrency for WooCommerce
  6. String Translation admin texts, JavaScript detection
  7. Translating your contents dashboard, editor, translation services
  8. Boosting the performance of your multilingual WordPress site
  9. Localization (Sanity docs) document- and field-level
  10. Polylang free and Pro features
  11. Webflow pricing Localization add-on

Questions about WPML

Do we need WPML to have a bilingual site?

No. Polylang and WordPress multisite also run bilingual WordPress sites, and Sanity handles French with no plugin. Building on the CMS's own localization is the better choice when staff keep professional French translations, the site has many pages and it will run for years. WPML suits an existing WordPress site with WooCommerce or a supported page builder.

What does WPML cost in Canadian dollars?

WPML prices in euros. As of November 15, 2026, Multilingual CMS is €99 for a year of updates and support; your card issuer sets the CAD amount. Extra AI translation words are bought separately, from €50 for 10,000 words.

Does WPML add hreflang tags?

Yes. Every WPML plan inserts hreflang tags and updates them as you translate. You can set a regional code such as fr-CA for each language, but WPML can't warn you if a code is invalid, so we check them.

What happens if we stop paying for WPML?

The plugin keeps working and your translations stay in your database. You lose updates and support, including fixes when WordPress or WooCommerce changes. WPML offers a 30-day money-back guarantee on new purchases.

Making a WordPress site bilingual?

Tell us how many pages you have and who will keep the French up to date. We'll say whether WPML, Polylang or a rebuild on the CMS's own localization fits.

Book a call