Per-page control

Site-wide settings decide how translation works by default. The block editor’s Language Switcher sidebar panel decides how one post behaves in one language — open any post or page, find the panel, and each enabled language is a row you can expand.

The four modes

• Automatic (the default). The page translates the same way every other page does. Most content should stay here.
• Custom. Write or paste a version of this page for one language by hand — a full alternate rendering, not a string-by-string correction. Use this when a machine translation would never be right: an idiom, a region-specific offer, a legal notice that needs its own local wording.
• Linked. Point this page, in this language, at an entirely different page on your site — for when you already maintain a separate page for that market and want the switcher and hreflang to point at it instead of a translated copy of this one.
• Disabled. This page does not exist in this language. It is left out of the switcher, out of hreflang, and out of sitemaps for that language, and answers as though it were never published there.

A mode you set here is more specific than any site-wide exclusion rule and takes precedence over it.

Translated slugs

Each enabled language can also have its own URL slug for this post — a French page can live at a French-language slug rather than a transliteration of the English one. A Suggest button offers a translated slug for the title, generated the same way any other missing string would be, so you are not typing a translation by hand just to fill in a field. It is a suggestion: nothing is committed until you save the post.

Improve with AI

Fast machine translation is what renders the page for a visitor. When you want better tone, context, or terminology on a specific post’s translation, the panel’s Improve with AI button runs one pass through an AI provider you have connected via Settings → Connectors, for the post and language you are looking at. This is never automatic and never runs in front of a visitor — it is something an editor asks for, on demand, and it replaces only the translation of that post’s own text, leaving the theme’s shared furniture untouched.

Once refined, a translation is locked, the same as a hand-written correction: if the underlying source text changes later, LocaleReady notices the original sentence is gone and does not silently overwrite your correction with a fresh machine translation of the new one.