A brief becomes a real page.Translate a page with Polylang
Create a linked translation draft and review its text without changing the original page.
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+, Polylang active, and a verified AI connection.
- A practice Elementor or Gutenberg page and the intended target language.
Let’s do this, step by step.
Step 01
Check languages and tool access
Open Setup → Tools → Plugins → Polylang. Check the read tool, enable the write tool, Save changes and reconnect. Ask the AI to read languages and the source page.
Check the source page and the languages already set up. Enable Polylang’s write tool only when you are ready to create the translation.
Step 02
Prepare the language relationship
If needed, use add-language and assign-language for content without a language. Inspect any existing translations before create-translation. Avoid URL-mode changes in this walkthrough.
Give the original its correct language. Check that the target language exists and that the page has not already been translated. Do not change site-wide language URLs just to translate one page.
Step 03
Create the linked draft
Use create-translation with the source post ID and target language slug. Record the returned draft ID and warnings about untranslated terms.
Create a translation copy linked to the original. It starts as a draft and keeps the page structure. Check any warning about categories that still need translating.
Create a French translation draft of the verified page using Polylang. Preserve the original. Read the draft’s text segments and propose translations. Do not publish or change site-wide language settings.
Step 04
Translate and save the text
Read get-page-text on the translated draft. Review the numbered translations, then apply-page-text. Inspect skipped HTML, dynamic or unsupported block content separately with its native builder.
Translate the returned text while keeping its numbered links to the page. Review the wording, buttons and metadata. The tool reports content it cannot safely change, so check those parts separately.
Step 05
Review both language versions
Preview the draft and original. Check text, links, menu language and missing term translations. After approval, use set-status to publish and inspect History.
Open both versions and confirm the original is unchanged. Check the translated page’s links and layout. Publish only after the language review. History can undo supported writes, but deleting a language is not reversible there.
You’re done when…
The translation is linked, readable and reviewed; the original page remains intact.
Keep the reference handy.
The docs cover tool details and requirements for this lesson.