Translate a page

Pages are always available to POM Translate’s parser. You can still decide whether their title, content, excerpt, and registered metadata should be translated.

This workflow suits ordinary WordPress pages and pages whose content remains in the canonical page object.

Prepare the page

Open Settings → POM Translate → Content types and find Pages (page). Confirm the required parts are enabled:

• Title for the page heading and title APIs;
• Content for the body;
• Excerpt only when the site actually uses a page excerpt;
• Meta for registered translatable keys.

POM Translate creates translation storage for published and private pages by default. Saving a normal draft does not prepare its strings.

Generate the source rows

1. Finish the page’s main-language structure.
2. Publish it, or use private visibility for controlled review.
3. Save the page.
4. Check the POM Translate summaries in the editor status area.
5. If the summary says No translatable strings found yet, confirm the page status and field settings, then save again.

The summary includes the page’s post strings and configured metadata. It does not include the translated URL slug, menu labels, or taxonomy terms.

Open only this page

Select Manage translations for the required locale. POM Translate opens Translations → Translate contents with the page’s object ID and post context applied.

Translate in a deliberate order:

1. Post title;
2. short headings and calls to action;
3. body paragraphs;
4. list items and captions;
5. supported shortcode or builder text;
6. configured metadata.

Save in manageable batches. If the table spans several pages, save before changing pagination.

Preserve the layout contract

The translation table can show protected placeholders inside body rows. They represent inline markup or nested structures that POM Translate needs to rebuild the page.

Translate:

Discover our %1%seasonal menu%/1%.

as prose appropriate for the target language while retaining %1% and %/1% once each. Do not add layout HTML merely because the textarea accepts formatted content; the existing structure comes from the page skeleton.

Translate the route separately

The title does not determine the localized slug. After the content is ready:

1. open Translations → Translate URLs;
2. select the content URL editor;
3. choose the page and target locale;
4. save the localized slug;
5. test the resulting language-prefixed route.

This separation lets an editorial title and a stable URL follow different conventions.

Check parent and navigation context

POM Translate localizes the selected page object, but a complete visitor journey may also require:

• translated parent-page slugs;
• translated menu-item labels;
• localized custom links;
• breadcrumbs generated by the theme or SEO plugin;
• related reusable content or registered strings.

Test the page from the homepage navigation rather than only pasting its URL.

Verify the page

Open the target route in a private window and check:

• browser title and visible page title;
• every content section in visual order;
• links, buttons, images, forms, and responsive layout;
• any remaining source-language fallback;
• canonical and alternate-language URLs;
• parent and child routes;
• the editor’s translated percentage after reloading.

There is no separate translation publish button. Once Save translations succeeds, non-empty values can render immediately wherever the source page is accessible.

Read Preview a translation for a safe inspection workflow.