Preview a translation

The general Translate contents table does not provide an unsaved translation preview. Save translations writes the target values, and the localized frontend route is the authoritative assembled result.

Use a staging site or private WordPress visibility when content must be reviewed before public access.

Choose a safe review environment

For an unpublished launch:

• translate on a staging copy; or
• set the canonical object to Private, which is eligible for translation storage by default, and review it while authorized.

Ordinary drafts and pending posts do not generate or retain translation strings in the default configuration. Publishing only the target locale separately is not possible because all locales share one canonical object.

Save a controlled batch

1. Open Manage translations for the target locale.
2. edit a small set of rows;
3. preserve placeholders;
4. select Save translations;
5. confirm Translations updated.;
6. keep the source editor and target route open in separate tabs.

There is no translation-specific undo history exposed in the table. Keep a source export or controlled record when reviewing substantial rewrites.

Build the target URL

Use the language selector or the URL generated by Translations → Translate URLs. The target should include the configured locale prefix and localized slug policy.

An explicit language-prefixed route is preferable to an unprefixed URL during review because browser detection and saved preferences cannot select a different locale.

Inspect as the intended visitor

For public content, use a signed-out private browser window. For private content, use an authorized account that can view the object, while still testing the explicit localized route.

Check:

• document language and URL prefix;
• title, body, excerpt, and registered meta;
• any source fallback;
• inline formatting and placeholders;
• forms, shortcodes, and builder components;
• menu and taxonomy context;
• canonical, hreflang, and sitemap behavior where applicable;
• mobile layout and keyboard operation.

Refresh derived output

POM Translate invalidates its relevant translation caches when values change, but a full-page cache, reverse proxy, or CDN can still serve an earlier response.

After saving:

1. reload without relying on an open cached tab;
2. purge the affected page cache when necessary;
3. test the exact prefixed URL;
4. compare signed-in and signed-out output;
5. avoid sharing the review link until the intended version is visible.

Correct and recheck

Return to Translate contents, update the specific row, save again, and reload the route. Mark it Reviewed only after the corrected assembled page passes.

If the wrong source row appears, use Context and Edit this element to verify the canonical object. If a row is absent, resave the published or private source after checking field configuration.

Do not confuse specialized previews

WooCommerce email translations have their own preview and test-send tools. Those controls do not preview ordinary posts, pages, or custom post types.

Read Publish and update translations to understand when saved values become visitor-facing.