Translate posts, pages, and custom content
POM Translate turns selected fields from one canonical WordPress object into editable strings for each additional language. Translators work on those strings under Translations → Translate contents; visitors still receive the same post, page, or custom object in the requested locale.
Use this chapter for manual translation and editorial review. URL slugs, taxonomy terms, menus, software strings, and WooCommerce emails have their own dedicated chapters and screens.
Prepare the source object
Translation storage is generated for eligible post types when an object is saved with a supported publication status. By default, published and private objects qualify; ordinary drafts, pending posts, autosaves, and revisions do not.
Before translating:
- configure at least one Additional language;
- open Settings → POM Translate → Content types;
- confirm the post type is enabled;
- enable the required Title, Content, Excerpt, and Meta parts;
- publish or privately publish the source object;
- save it once after the final source structure is in place.
Pages are always enabled for parsing, although their individual field parts remain configurable. Posts are enabled by default. Other public post types shown by WordPress must be enabled explicitly unless an integration makes them mandatory.
Choose the relevant workflow
| Goal | Guide |
|---|---|
| Understand the central table, columns, filters, and save behavior | Tour the translation editor |
| Complete a normal hierarchical page | Translate a page |
| Complete a dated blog post | Translate a post |
| Edit one specific core field | Translate titles, excerpts, or body content |
| Work with structured content | Translate shortcode content or builder content |
| Include metadata | Translate custom fields |
| Enable another object type | Translate custom post types |
| Start with unchanged source wording | Use the original text as a starting point |
| Decide what visitors see when rows are empty | Handle incomplete translations |
| Interpret workflow labels | Understand translation status |
| Perform linguistic and functional approval | Review translated content |
| Inspect the localized result | Preview a translation |
| Understand when saved text becomes public | Publish and update translations |
| Respond to an edited source segment | What happens when original content changes |
Recommended first translation
- Open the published source page in WordPress.
- Find the POM Translate language summary in the editor status area.
- Choose Manage translations for the target locale.
- Confirm Translate contents is filtered to that object and locale.
- Translate the title and one short body row.
- Preserve every protected token shown in the source.
- Leave unrelated rows unchanged.
- Select Save translations.
- Confirm the success notice says Translations updated.
- Open the target-language public URL in a private window.
A manually saved non-empty value receives Human status. Clearing a value and saving makes it Pending, and the frontend uses the source value for that missing row.
Understand completion
The percentage in the post editor is based on non-empty translated rows, including configured post metadata. It is not a publication switch and does not mean the text was reviewed. A page can show 100% while containing Machine or Human rows that still require approval.
Similarly, a localized route can render before reaching 100%. Missing rows fall back to source content, which keeps structure intact but may create a mixed-language page.
Keep structure and prose separate
Body content is segmented. Inline HTML and other protected structures can appear as tokens such as %1% and %/1%. Shortcode content may use its own stable markers. Translate the human-readable words while retaining all required tokens exactly; invalid placeholder changes are rejected on save.
Do not translate:
- locale prefixes in the content editor;
- post or term slugs in ordinary string rows;
- shortcode configuration values unless POM Translate extracted them;
- identifiers, IDs, CSS classes, or technical metadata.
Verify a complete object
Review the localized URL as a visitor and check:
- title, body, excerpt, and configured metadata;
- headings, lists, links, buttons, and media alternatives;
- shortcode and builder output;
- source fallbacks that remain visible;
- translated slug and canonical route;
- menus, taxonomy terms, and related content;
- responsive layout and interactive forms;
- status labels and reviewer assignment.
Start with Tour the translation editor.