Tour the POM Translate interface

POM Translate separates site-wide configuration from day-to-day translation work. Administrators use Settings → POM Translate to define the system; translators and editors use Translations to work on language-specific values.

Settings → POM Translate

Languages setup

Base setup controls:

  • the read-only Main language inherited from Settings → General;
  • optional selector labels for the main and additional languages;
  • the ordered Additional languages list;
  • whether the main language also uses a URL subdirectory;
  • browser-language detection and its redirect fallback.

Language switcher controls the global output used by navigation-menu items, the [pom_translate_language_switcher] shortcode, and the optional floating selector. A selector exposes configured languages; it does not create translations.

Content types

This area decides which public post types and taxonomies are parsed when their source objects are saved.

For each eligible post type, the current interface can control:

  • Title
  • Content
  • Excerpt
  • Meta

Pages and navigation menu items are always enabled by the current policy. Posts are enabled by default. Categories and tags are always enabled taxonomies. Other post types and taxonomies are explicit choices.

Advanced

LLM translation settings owns optional machine-translation behavior, translation guidance, quotas, batching, retry policy, and POM AI availability. These settings do not affect the ability to enter manual translations.

Treat generated text as a draft. A successful provider response does not mark the wording as reviewed by a person.

Tools

Translation maintenance provides operations with different risk levels:

  • Export translations downloads a JSON snapshot with statuses and protected markup.
  • Import translations accepts a POM Translate JSON export and updates only exact source matches.
  • Clean up orphaned data removes translation records whose source object or locale no longer exists.
  • Reset machine translation quota resets the current site’s local daily counters.
  • Reset translation storage permanently clears stored translations, slugs, and reconstruction data.

Export and cleanup do not have the same rollback. Back up the database before reset, and never use reset as routine troubleshooting.

License

The License section owns domain authorization and private updates. It does not enable machine translation and it does not decide which languages are public.

Translations

Translate contents

This is the main table for extracted post, term, menu, and supported meta values. Choose a target locale, filter by status or object, review Original Text, edit Translation, and select Save translations.

Protected placeholders represent formatting or inline structure. The editor validates them before saving; keep every required opening and closing marker intact.

Other translations

This area contains registered standalone strings and supported singleton defaults that do not belong to an ordinary post or term. WooCommerce email fields appear in their dedicated view when WooCommerce is active.

Translate URLs

Use this workspace for localized content slugs and mapped custom URLs. Text translation and URL translation are separate operations; saving a translated title does not invent a translated slug.

Translation exclusions

Exclusions remove selected subjects from a locale’s translation workflow and localized public route. Review the exact locale and object before applying one.

Software translations

Administrators can work with supported WordPress, theme, and plugin gettext catalogs here. Software strings follow file-based WordPress translation behavior rather than the extracted content table.

Generate pending translations

This tool scans enabled content types and taxonomies for missing translation work. It can create missing source rows and, when configured, process machine translations. Use a small scope first and do not close a review merely because the generated count reached zero.

Post editor shortcut

For an enabled post type, the classic and block editors show a per-language translation summary. It reports translated, missing, machine, human, and reviewed counts and links to Manage translations. When POM AI is available, Translate with AI can fill missing strings for that post and locale.

The summary is a progress view, not a full translation editor. Use Manage translations to inspect individual source and target values.

Enable tweaks safely on a production site
Previous
Multilingual site launch checklist
Next