Languages
Source and target languages, the URL prefix each one is served from, and translated archive URL segments. Languages & URLs →
Translate a site
LocaleReady’s job is automatic multilingual WordPress: visitors read the site in their language, and you keep writing in yours. There is no second page tree, no export step, and no translation desk to run — the plugin reads the page WordPress already rendered and translates it.
Before you translate
Section titled “Before you translate”- The plugin is installed and the license is active.
- A DeepL or Google API key is saved under Settings → Connectors.
- At least one target language is enabled under LocaleReady → Settings → Languages.
What happens on the first request
Section titled “What happens on the first request”The first visitor to read a page in a language it has not been read in yet costs one round trip to your translation service. LocaleReady segments the rendered HTML, looks up every piece of text in its own translation memory, and sends only what is missing to DeepL or Google Cloud Translation — whichever you connected. The result is stored. Every visitor after that is served from your database, in full, with no provider call at all.
You can change that default: translate new content in the background as soon as a post is saved, so the first visitor never waits, or run a one-time scan that pretranslates the whole site from the Tools screen.
Where the settings actually live
Section titled “Where the settings actually live”Six tabs under LocaleReady → Settings cover the whole product:
Translation
Which service translates, protected terms, and a way to test a service before you trust it. Translation service →
Content
When translation runs, what happens beyond the page (AJAX, REST, email), and rules for parts of the site that stay untranslated. Content & exclusions →
Visitors
The language switcher’s defaults, and whether a first-time visitor is sent to their browser’s language automatically. Language switcher →
Usage & limits
A monthly ceiling on translation spend, and whether a non-production copy of the site may call a provider at all. Usage & spend →
General
The license key, diagnostics logging, and what happens to your translations if you ever delete the plugin.
Beyond the settings screen
Section titled “Beyond the settings screen”Two more places give you control over one page or one post at a time:
- The block editor sidebar. Set any language for the post you are editing to automatic, a hand-written version, a link to a different page, or off entirely — and ask an AI provider to polish one language’s translation. See per-page control.
- The Translations screen. Every stored translation, searchable and editable, with export to JSONL, CSV, or XLIFF for a human translator, and import back in.
If a page does not look translated
Section titled “If a page does not look translated”Confirm the language is enabled and a translation service is connected on the Translation tab, and that the page is not matched by an exclusion rule. If your monthly character limit has been reached, new strings are served in the source language until the month resets — the Usage & spend tab says so. And make sure you are looking at a front-end URL rather than a cached copy from a host’s page cache.
For the license itself — activation, updates, and where the zip comes from — see account and billing.