What POM Translate does

POM Translate turns a WordPress site into a multilingual site while keeping each post, page, term, menu item, product, and order as one canonical WordPress object. Editors maintain the source object in its normal WordPress screen and maintain other languages through POM Translate.

The plugin separates three responsibilities that are often confused: the source content remains in WordPress, translated values are managed per locale, and the active request decides which stored values and URLs visitors receive.

Content it can translate

POM Translate can discover and render supported values from:

• post and page titles, body content, and excerpts;
• enabled custom post types and their selected fields;
• categories, tags, and enabled custom taxonomies;
• menu labels and the URLs behind menu items;
• supported custom fields registered as translatable;
• localized post and term slugs;
• registered standalone strings and defaults;
• plugin, theme, and WordPress software strings through the software-translation workflow;
• supported WooCommerce products, cart and checkout output, account routes, and transactional emails;
• eligible frontend AJAX and REST response values.

Installing the plugin does not translate all of these automatically. A content type must be enabled where applicable, the source object must be saved so its values can be discovered, and every target locale still needs stored translations or an intentional source fallback.

One source object, several public languages

When an eligible source post is saved, POM Translate identifies the values that can be translated and preserves the structure needed to rebuild the body. Editors then add target-language text under Translations.

On a localized request, POM Translate uses the current locale to render those values. If one target value is empty, the corresponding source value remains visible. The plugin does not create a second post merely to hold that missing or completed translation.

This model preserves the source post’s identity, author, publication state, taxonomy relationships, featured media, and other WordPress relationships across languages.

Localized routes and language choice

Additional languages use a URL subdirectory derived from their language code, such as /en/ or /fr/. The main language can keep the unprefixed WordPress URL or use its own subdirectory when Use a subdirectory for the default language is enabled.

POM Translate can provide:

• localized post and term slugs;
• language-aware internal links and navigation;
• menu, shortcode, and floating language selectors;
• the document language attribute;
• localized canonical URLs;
• alternate-language links for available locales.

The site owner remains responsible for choosing final slugs, preventing conflicting routes, and testing redirects and cached copies before publishing a changed URL.

Manual and assisted translation

Manual translation is built into Translations → Translate contents. Saved manual text receives the human translation status and can later be marked reviewed.

POM AI support is optional. It can create machine-translated drafts only when machine translation is configured and a separate valid POM AI license and sufficient credits are available. A POM Translate license does not include POM AI authorization or credits.

Frontend visitors never need POM AI to read a page. Public rendering uses stored translations and source fallbacks.

What remains outside the plugin

POM Translate does not write the source article, review linguistic accuracy, choose legal terminology, or decide whether a partially translated page is suitable for publication. It also does not replace the site’s normal backup, deployment, SEO, cache, or consent processes.

Use How POM Translate differs from duplicate-post translation to decide whether the one-object editorial model fits the site.