Translate a post

Posts are enabled for translation by default. A complete article normally combines a title, optional manual excerpt, segmented body content, taxonomy terms, author and date presentation, media text, and a localized slug.

Only some of those belong to Translate contents.

Confirm the post fields

Open Settings → POM Translate → Content types → Posts (post). Keep the post type enabled and review:

  • Title;
  • Content;
  • Excerpt;
  • Meta.

Disabling a part removes that field family from subsequent source processing. It does not turn the field into independently translated WordPress data.

Save a stable source article

POM Translate processes published and private posts by default. Publish the canonical article or use private visibility, then save it after:

  • finalizing headings and paragraph order;
  • choosing the manual excerpt;
  • inserting media and captions;
  • completing shortcodes or reusable markup;
  • assigning categories and tags.

Taxonomy names and descriptions are translated separately; saving a post does not create their target text.

Translate the article rows

From the post editor, select Manage translations for the target locale. In the filtered Translate contents table:

  1. translate Post title;
  2. translate the Post excerpt row when present;
  3. work through body rows in reading order;
  4. retain protected inline and shortcode tokens;
  5. translate registered meta rows only when their context is clear;
  6. select Save translations.

The context column links back to Edit this element, which is useful when several similar excerpts or headings appear across the site.

After the article text:

  • translate the post slug under Translations → Translate URLs;
  • translate assigned category and tag terms;
  • check media alternative text when it is registered for translation;
  • translate any menu label that points to the article;
  • inspect SEO title and description rows if Meta is enabled.

The publication date is not an ordinary content string. Its format follows the locale-specific date behavior configured under Translations → Other translations → Defaults.

Handle ongoing editorial updates

Source edits are processed the next time the post is saved. An unchanged extracted row keeps its translation. If the stored source text, placeholders, token position, or structural identity changes, POM Translate replaces that source record and removes its old target translations before attempting exact-match reuse.

Review the translation summary after every material source revision. A previously complete article can return to a lower percentage.

Verify archive and single views

Inspect more than the single post:

  • the localized blog archive;
  • category and tag archives;
  • search results;
  • cards or related-post modules;
  • feed output where relevant;
  • the single-post route;
  • previous/next navigation;
  • social and SEO metadata.

The manual excerpt may appear on archives while the body appears only on the single view. Both need independent review.

Avoid false completion

A 100% figure means every extracted post and configured meta row has non-empty target text. It does not prove:

  • categories and tags are translated;
  • the slug is localized;
  • links point to the correct locale;
  • machine text was reviewed;
  • embedded software strings are translated.

Use Review translated content before publication before promoting the article.

Translate a page
Previous
Prevent misleading fallback pages from being indexed
Next