Your translated site keeps working
Everything LocalePro translates is saved on your site. If you cancel, the site keeps those translations and can keep making new ones. What you lose is plugin updates.
Alternatives
LocalePro vs Weglot
Same goal, different question: does the translating happen on your site, or somewhere else?
The short version: Weglot translates your site somewhere else and sends the result back. LocalePro translates it right on your own WordPress site and keeps it there.
| What matters | LocalePro | Weglot |
|---|---|---|
| How a page gets translated | Your page loads as normal, and LocalePro translates it right there on your own site. | A snippet sends your page off to Weglot, which sends back a translated version from its own servers. |
| Where your translations live | In your own WordPress site, where you can search them, edit them, or export them any time. | On Weglot's servers, managed from Weglot's own dashboard rather than wp-admin. |
| What you pay for translating | Your own DeepL or Google account, billed to you directly at their normal price. | A Weglot plan, usually priced by how many words you translate and how much traffic you get. |
| If you ever cancel | Your site keeps the translations, and can keep making new ones. Updates from us stop. | Translated pages stop working, since they were never saved on your own site. |
| Fixing a translation by hand | Right there in wp-admin, on the same screen you already use. | In Weglot's own dashboard, separate from your WordPress admin. |
| Shops and forms | Cart, checkout, and order emails, plus form confirmations, all translated properly, out of the box. | Translates what's on the page. Things that load in afterward, like a live cart update, depend on what the tool can catch. |
| Translated addresses | A page can live at /es/precios, not /es/pricing. The address is saved on your site. | Translated URLs are part of Weglot's hosted setup. They aren't pages in your WordPress database. |
| Site search | A visitor can search for the words on the translated page, like envío gratis on /es/, and find it. | WordPress search looks at the original text, because the translations were never saved there. |
| A ceiling on spend | Set a monthly limit. We warn you as you get close, then pause new translating. A staging copy doesn't spend unless you say so. | The plan caps words and how often pages are requested. Go over it and translation stops until you upgrade. |
| What has to be on the page | Nothing extra in the browser. The page arrives already translated. | A snippet sends the page to Weglot and brings a translation back. |
Why choose LocalePro
One flat price, no matter your traffic
The yearly price doesn't change with how many words you translate or how many people visit. A busy month and a quiet one cost the same from us.
Questions
Does LocalePro work the same way as Weglot?+
Not quite. Your page loads and LocalePro translates it right there, on your own site. Nothing about the page has to travel through another company's servers to reach your visitor.
Can I switch from Weglot to LocalePro?+
Yes. Export your translations from Weglot as CSV or XLIFF, then import that file under Tools in LocalePro. Hand edits come across. The steps are on the migration page. Turn Weglot off only after the import is in.
Is LocalePro cheaper than Weglot?+
Weglot's Business plan is published at about $320 a year, and larger word counts cost more, every year. LocalePro is $249 a year for one site. A 50-page site into one language is about 120,000 characters, which usually sits inside Google's free monthly amount, and you pay that once. Check Weglot's pricing page for the plan that matches your word count. Their dollar prices are estimates of plans billed in euros.
Give LocalePro a try
Connect your own DeepL or Google account and have your first translated page up in minutes.