Journal ·
What automatic multilingual actually means
One WordPress site, many reading languages — without a second page tree.
“Multilingual WordPress” usually means one of three things: a second site, a second page tree, or a string catalog you export and import. All three work. All three make publishing slower.
LocaleReady is built for the case where the source of truth stays one site. You publish in the language you write. Visitors read in theirs. The plugin is the translation layer, not a new CMS.
What we will not document from this repo
The WordPress UI — which languages, how to exclude a URL, how to edit a string — lives in the plugin. These pages stay at the product level so they do not drift from screens we do not ship here. When that UI is documented in the plugin repo, it will land under /docs.
What is already true
- You buy a license and install a zip like any other plugin.
- You activate a key so the site can validate and receive updates.
- Translation is the job of the plugin after that, not a second editorial workflow we invented for marketing.
If a page is not translated, check the license still validates and that you are looking at a front-end URL, not a host cache of the last HTML. That is the boring, correct debug path.
The rest is translate a site.