A new language starts already written
Turn a language on, and your existing pages are readable right away — no writing a page for everything you've already published first.
Alternatives
LocaleReady vs Polylang
A lighter take on the WPML idea — still one page per language underneath.
The short version: Polylang connects a separate WordPress page for each language, similar to WPML. LocaleReady translates one page automatically, so a new language starts off already written rather than blank.
| What matters | LocaleReady | Polylang |
|---|---|---|
| How your content is organized | One page, translated automatically into every language you turn on. | Each language gets its own WordPress page, connected together — the same basic idea as WPML, in a lighter package. |
| Automatic translation | Built in and switched on by default, using your own DeepL or Google account. | Historically more about translating by hand, string by string, than translating automatically. |
| Adding a new language | Turn it on. Your existing pages translate themselves the next time someone reads them. | Turn it on, then write (or import) a page for that language for everything you've already published. |
| How much upkeep it takes | Light — a new language is ready the moment you turn it on. | A real, separate page per language — full control, and full responsibility for keeping each one current. |
| Pricing | One yearly license, based on how many sites you use it on. | Free to start, with Polylang Pro sold separately for extra features. |
Why choose LocaleReady
Automatic from the very start
Translation is built in from day one, not something you bolt on once the manual approach gets to be too much work.
Questions
Is Polylang free while LocaleReady is not?+
Polylang's core plugin is free, with Polylang Pro sold on top. LocaleReady is a paid yearly license with no free version — in exchange, automatic translation and saved translations come built in, rather than something you piece together.
Does LocaleReady make a separate page per language, like Polylang?+
No. There's one page, and LocaleReady translates it for you. You can still write your own version of one page in one language if you want to, without that becoming a second page to maintain everywhere else.
Which one is better if I'm translating everything by hand anyway?+
If every language is genuinely getting its own careful, human pass, Polylang's separate-page approach gives that work a clear home. LocaleReady is built for the more common case: most pages should say the same thing as the original, automatically.