Complete a partly untranslated page

Partial output usually means POM Translate is working but one surface was not extracted, translated, or supported by the same contract as the rest of the page.

Identify ownership

Classify every source-language fragment:

  • post title, excerpt, body, or mapped metadata;
  • taxonomy term;
  • menu label;
  • registered interface string;
  • shortcode or builder attribute;
  • JavaScript, REST, or AJAX response;
  • theme/plugin gettext string;
  • external widget.

Each category has a different translation workflow. Translating the body does not automatically translate a menu, software catalog, or browser-rendered widget.

Resolve missing extraction

Confirm the content type and field are enabled, then save the base-language object. For custom fields or shortcode attributes, load the maintained registration before saving. Avoid enabling entire serialized payloads simply to reach one visible label.

If the string appears in the Translation Manager, add and save the target value. If it does not, determine whether it belongs to the software-string catalog or requires a third-party integration.

Check fallback intentionally

POM Translate falls back to source text for empty target fields. This prevents broken layouts but can make an incomplete page look partly translated.

After correcting the surface, clear the affected caches and review the page while logged out. Include mobile components, popups, forms, notices, and dynamic fragments. Do not publish or index the route until the visible and SEO-critical fields meet the site's completion policy.

Remove REST and oEmbed discovery
Previous
Resolve POM AI credit or authorization errors
Next