AI-assisted translation
POM AI translates WordPress content into the other languages configured on your site. It builds on Polylang: the language setup, the language relationships and the translated records are all Polylang's, and POM AI supplies the translation.
Requirements
Polylang or Polylang Pro must be active. Without one of them, the translation tool does not register at all — no menu entry, no screen, even if the tool is ticked under AI Tools.
The languages must already be configured in Polylang, with the post types and taxonomies you want translated marked as translatable there.
The POM theme must be present. Post and product translation reads the theme's meta configuration to decide which custom fields are translatable.
The two ways to translate
| You want to translate | Use |
|---|---|
| One post or page you are editing | The Translate to … buttons on the edit screen |
| Many items at once | Languages → AI translate |
Both consume credits per element. Both create real Polylang translations linked to the source.
Guides
- Translate text with POM AI — translating a single post from the editor.
- Bulk translation with the AI translate screen — analysing the site and translating in bulk.
- Provide context and terminology — what the translator knows about your business.
- Preserve formatting, shortcodes and links — what survives translation and what does not.
- Bulk translation and credits — what a large run costs and how to control it.
- Review machine translation — the review that has to happen before publishing.
- Troubleshoot translation errors.
What gets translated
For a post or page, POM AI translates the title, the content — including translatable shortcode attributes — and the translatable custom fields defined by the theme, then creates the translated post and links it to the original in Polylang.
It also carries across the structural properties: author, dates, status, parent, menu order, comment settings and attached meta. Taxonomy terms attached to the post are translated too when they have no translation yet, each as its own request.
One deliberate exception: the excerpt is copied, not translated. If a post has an excerpt that matters, translate it by hand or with the paragraph assistant.
What it does not do
- It does not publish anything you have not already published — the translation inherits the source's status.
- It does not translate media files or the text inside images.
- It does not re-translate an item that already has a translation, unless you use the per-post button, which overwrites.
- It does not manage languages, URLs or language switchers. That is Polylang's job.
- It does not review its own output.
The one rule worth internalising
A machine translation is a first draft in a language you may not read. Publishing it unreviewed means publishing something nobody in your organisation has understood.
Translate a small representative set first, have it reviewed by someone who reads the target language, and only then run the bulk job. See Review machine translation.