Translate a WordPress Post

Use TranslateSense to translate an individual WordPress post into a language configured in Polylang. The translation workflow runs in the editor and processes content according to the detected editor type and its active mapping rules.

Before translating a post

• Open Posts → All Posts and locate the source post.
• Confirm that the source post has the correct Polylang language and that the target language is configured.
• Confirm TranslateSense has an active translation provider.
• Use the Polylang language controls to create or open the target-language version of the post. Keep the source and target linked as translations.

Translate the post

1. Open the target-language post in the WordPress editor. TranslateSense needs to resolve its source post through the saved source ID or Polylang translation relationship.
2. Select Translate Page in the TranslateSense control.
3. In Choose Translation Provider, select an active provider that supports the target language.
4. Wait for extraction and translation to finish, then review each source string, status, and translated value in Review Translations.
5. Edit any translated text that needs correction, then select Apply to Page.
6. Use WordPress’s Save, Update, or Publish action to persist the target post. Review the post on the frontend and confirm the Polylang translation relationship.

What gets translated?

The content parser selects the builder for the source post. Gutenberg blocks and Elementor widgets use their configured XML mappings; Classic Editor content uses the Classic Editor content builder. Only supported, mapped text is processed, and email addresses, URLs, and asset paths are excluded from the editor’s string-translation list. Review titles, excerpts, links, and any additional fields separately where they are exposed in the editor.

Troubleshooting

• If the TranslateSense control is missing, check the post type’s Polylang translation support and the source-to-target relationship.
• If the provider cannot start, verify its credentials, connection status, model access, and target-language support.
• If text is skipped, inspect the relevant XML mapping and confirm the source post uses that editor or field.
• Do not assume that Apply to Page saves the WordPress post. Save the target post in WordPress after reviewing the editor.

See Set Up Polylang Translation Pairs if the source and target posts are not linked correctly.

Screenshot to add: [WordPress post editor showing the Polylang language relationship and TranslateSense control]