TranslateSense can translate supported content from an individual WordPress page into a target language configured in Polylang. The workflow uses the page’s editor type and the active mapping rules, so review the result in the editor before saving it.
Prepare the page translation
- Open Pages → All Pages and locate the source page.
- Check the source language and configure the target language in Polylang.
- Activate or connect a translation provider in TranslateSense or WordPress AI Connectors, as appropriate.
- Use Polylang’s language controls to create or open the target-language page. Confirm that the target is linked to the correct source page.
Translate and save the page
- Open the target-language page in its editor.
- Select Translate Page in the TranslateSense control. The control location depends on whether the page uses Gutenberg, Elementor, or Classic Editor.
- Choose an active provider in Choose Translation Provider.
- Review the extracted source strings and translations in Review Translations. Correct any text that needs editing.
- Select Apply to Page to update the open editor.
- Save the target page with WordPress’s normal Save, Update, or Publish action. Check the rendered page and its Polylang language relationship.
Check page content and layout
TranslateSense does not translate every page setting automatically. Gutenberg content and Elementor widget fields are processed according to their mapping rules. Review headings, buttons, image alternative text and captions where mapped, links, and any important page-specific text. Confirm that layout and non-text settings remain correct.
If the page contains Elementor content, see Translate Elementor Content and XML Mapping and Content Rules. If TranslateSense is missing, check the editor troubleshooting guide.
Screenshot to add: [WordPress page editor with the target language selected and TranslateSense translation control]