Test a translated page as a visitor

The administration table proves that text was saved. A visitor test proves that WordPress resolves the localized URL, selects the intended locale, reconstructs the content, localizes supported links, and emits coherent language metadata.

Use the post completed in Translate your first post.

Remove session effects

1. Leave Browser language detection disabled.
2. Clear only the page, object, progressive JSON, and CDN entries that can contain this post.
3. Open a private browser window with no WordPress login or language-selection cookie.
4. Keep the source and target URLs available for side-by-side comparison.

Testing while signed in can include editor controls, preview state, or user-locale behavior that a public visitor never sees.

Open the source route

Request the normal source permalink.

Confirm:

• the post resolves with a successful response;
• the title, excerpt, body, formatting, and source slug are correct;
• the active language selector identifies the main language;
• no target-language prefix appears unless the main-language subdirectory setting is enabled.

This establishes that the canonical WordPress object still works before testing localization.

Open the target route

Use the language selector or request the localized permalink directly. An additional English locale, for example, uses a route beginning with /en/.

Check the page itself:

1. the translated title is visible;
2. translated body values appear in the correct order;
3. bold, emphasis, links, classes, and supported attributes remain attached to the intended text;
4. the value left empty in the first-post exercise displays its source text;
5. the internal link points to the active language when a localized destination is available;
6. no protected marker such as %1% or %/1% is visible.

If the page is a 404, save Settings → Permalinks, recheck the language code and localized slug, then retest without the CDN. Do not solve the symptom by adding an unrelated redirect.

Inspect language and SEO output

View the rendered page source or use the browser inspector to verify:

• the document lang value matches the target locale;
• the canonical URL points to the localized route;
• alternate-language links include the configured language variants;
• selector links do not add a second copy of the language prefix.

Rank Math or Yoast may own the original SEO output. POM Translate localizes the supported canonical and sitemap values; it does not create a second SEO plugin.

Prove that the page is read-only

Reload the target route twice and confirm:

• no new WordPress post was created;
• the translation percentage in the editor did not change merely because a visitor opened the page;
• the deliberately missing string remains pending;
• no POM AI credit was required for rendering.

Public rendering reads stored target values and uses source fallback. Translation generation belongs to source-save, Translation Manager, or explicit machine-translation workflows.

Test the language round trip

From the target page:

1. switch back to the main language;
2. confirm the selector returns to the matching canonical object;
3. switch again to the target;
4. confirm the target URL, selected language, and content are stable;
5. repeat at a narrow mobile width if the site exposes a responsive or floating selector.

The first visitor test passes when both URLs resolve, the locale changes only as intended, formatting survives, the fallback is visible only where expected, and language metadata agrees with the route.