Localize internal links in content

Links embedded in post content are part of the rendered structure, not ordinary prose. POM Translate preserves their markup while translating readable text and can rebuild same-site URLs for the active locale.

Prefer canonical WordPress destinations

When linking to a page, post, archive, or term:

  1. Insert the link through the editor using the canonical object.
  2. Complete the destination object's localized slug under Translations → Translate URLs → Content URLs.
  3. Translate the surrounding anchor text under Translate contents.
  4. Open the source and target versions from the public frontend.
  5. Confirm the target locale, resolved object, query string, fragment, and trailing slash.

The URL localizer accepts absolute same-site URLs and relative paths. It resolves an existing language-prefixed path back to the base route before rebuilding it, which prevents a second language prefix from being added.

Automatic custom-URL discovery is deliberately focused. It registers:

  • external anchor destinations;
  • recognized downloadable file URLs;
  • iframe sources;
  • links explicitly marked as downloads.

Native WordPress object permalinks continue through the slug localization pipeline instead of filling the custom-link editor. A same-site URL that needs a special non-object replacement can still be registered manually under Custom links.

Preserve non-path components

Internal localization retains the original query string and fragment. Custom URL replacement also restores the source fragment after substituting the mapped destination. Check links such as:

/services/?plan=team#pricing

as a complete unit. Translate only the readable anchor copy; do not paste an entire <a> element into a text translation field unless that field already represents protected structured content.

Test rendered output

Inspect links after shortcodes and page-builder content have rendered. A link generated dynamically by unsupported JavaScript may never pass through the server-side content or menu filters, so it may require the integration that creates it to use POM Translate's supported URL helper.