A brief becomes a real page.Translate a page with TranslatePress
Translate the text visitors see and review shared strings across the site.
Video coming soon
Your next step is ready.
Follow the complete written guide below.
The video will join it here when it’s ready.
Before you start
- EMCP Pro 3.19.0+, TranslatePress active, and a user allowed to translate.
- A practice page and one configured translation language; the free edition permits one.
Let’s do this, step by step.
Step 01
Check the language and tools
Open Setup → Tools → Plugins → TranslatePress. Enable the required read/write tools, Save changes and reconnect. Read the language setup.
Check the translation language before starting. TranslatePress changes the text shown on the page rather than creating a second page copy.
Step 02
Read the page strings
Use get-page-strings with the actual post ID and target locale, such as fr_FR. Inspect the page-ordered strings and whole-sentence context.
Read the page’s text, including menus and footer. A sentence may arrive in pieces around a link or bold word. Use the complete sentence to translate those pieces naturally.
Step 03
Review and save translations
Prepare translate-strings from the returned versions, up to 200 entries per call. Review the text before writing. If a conflict occurs, read again and reconcile instead of overwriting.
Review the translated wording before saving. The same text can be shared across the website, so a menu or footer change can appear on several pages. If somebody edited a string meanwhile, read the new version first.
Read the chosen page’s TranslatePress strings in French. Propose translations using each whole-sentence context. Preserve reviewed translations, identify shared strings, and wait for review before writing.
Step 04
Check the visual editor
Open the page in its translation language and inspect it in TranslatePress. New translations are marked machine translated. After a human review use review-strings for the verified strings.
Check the page layout and complete sentences in the visual editor. Mark only the translations you have reviewed. Reading a page through this workflow does not start automatic translation.
Step 05
Check shared text and limits
Review another page sharing header/footer strings, then get-progress and History. Use the native product’s appropriate features for unsupported SEO fields, slugs and image alt text.
Check shared text on another page too. The free-edition workflow does not translate every field, including search metadata and slugs. History can restore a batch unless those strings were changed again.
You’re done when…
The translated page and shared text read correctly, and reviewed strings are marked deliberately.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.