Page-by-page control

Site-wide settings decide the default. The editor’s language panel decides how one post behaves in one language. Open any post or page, find the panel, and each language you offer is a row you can open.

The four choices

• Automatic. The usual one. The page translates the same way every other page does. Most content should stay here.
• Your own version. Write or paste a version of this page for one language. Use this when a machine translation would never be right: a joke, a local offer, a legal notice that needs its own wording.
• Another page. Point this language at a different page on your site. Useful when you already keep a separate page for that market, and you want the language menu and search engines to send people there.
• Off. This page doesn’t exist in this language. It’s left out of the menu, out of the language notes for search engines, and out of sitemaps. Visitors get the same answer they’d get for a page you never published.

A choice you set here beats any site-wide exclusion.

Translated addresses

Each language can have its own web address for this post. A French page can live at a French slug, not a copy of the English one. Suggest offers a translated slug from the title, the same way any other missing sentence would be translated. Nothing is saved until you save the post.

Improve with AI

Visitors get the automatic translation. When you want better tone on one post, Improve with AI runs one pass through an AI service you’ve connected under Settings → Connectors, for the post and language you’re looking at. It never runs on its own, and it never runs in front of a visitor. It only rewrites that post’s own text, not the header, footer, and other shared pieces of the theme.

Once you improve a translation, it’s treated like a correction you typed. If the original sentence changes later, LocalePro notices your version no longer matches, and it does not quietly overwrite it with a fresh machine translation.