Translate custom URLs

Custom URL translations replace complete destinations that do not belong to the normal post-and-term slug workflow. Typical entries are external links, downloadable files, iframe sources, video sources, POM Theme logo images, explicit download links, and URLs added manually.

Save a mapping

1. Open Translations → Translate URLs → Custom links.
2. Choose the target locale.
3. Locate the row by Original URL, Type, and Used in.
4. Enter URL for locale.
5. Select Save custom URLs.
6. Test every occurrence shown for that source.

If discovery did not collect the URL, use Add custom URL, enter the exact original and translated destinations, and select Add URL.

Translate POM Theme logo images

Keep the original images in Settings → POM Theme → Design system → Brand. POM Translate detects the saved Logo, Mobile version logo, Mobile navigation logo, and Side navigation logo URLs when you open Translations → Translate URLs → Custom links. It also detects Header logo and Header mobile logo in every additional Header colors preset under Layout → Header colors. Detection also works when a logo is rendered as inline SVG.

1. Upload the translated logo to the site's Media Library and copy its file URL.
2. Open Translations → Translate URLs → Custom links and choose the target locale, such as Basque (eu).
3. Find the original image URL. Used in identifies its POM Theme logo fields and links to Brand settings. For Header colors variants, it includes the preset's Config name and links to Header colors.
4. Paste the translated image URL into URL for locale and select Save custom URLs.
5. Visit the site in that language and check the header, footer, mobile menu, and side navigation where used. Then switch to the main language and confirm it still uses the original image.

A blank translation uses the original image, including the original image of a selected Header colors preset. Each distinct source URL has its own mapping; logo fields that share a source URL share its translation. Clearing the translated field restores the original for that locale. After changing a source logo in Brand or Header colors settings, reopen Custom links to detect its new URL. A deleted source row is detected again while its image remains configured.

The Logo module uses these mappings for Brand images and for an explicitly selected Logo version, including inside fullscreen navigation content. A selected header preset or Logo version keeps precedence over the default Brand image; POM Translate then translates that selected source URL. Dimensions and SVG rendering settings remain shared: use compatible proportions and trusted local SVG files when inline rendering is enabled. The Site Icon is not included in logo detection.

Translate POM videos and video backgrounds

Video URLs are collected from these sources, including nested rows and columns:

• POM's vc_row, vc_row_inner, vc_column, and vc_column_inner background settings;
• the web_video, vc_video, and WordPress video shortcodes, including shortcodes inside a Gutenberg Shortcode block;
• the POM Section, Row, and Column Gutenberg blocks;
• HTML video sources, including the WordPress Video block.

YouTube and Vimeo URLs and self-hosted MP4, WebM, and OGV files appear in Custom links. Each source file has its own mapping. Video thumbnails, playback controls, and other presentation settings are not video URL entries.

1. Save the page containing the video to refresh its detected URLs. For existing content across the site, Translations → Generate pending translations → Process all also refreshes discovery; Translate pending only does not. Process all also translates pending text when automatic translation is enabled.
2. Open Translations → Translate URLs → Custom links and choose the target locale.
3. Enter the localized video URL for each source used by the player. Keep the same provider or file format as the original field.
4. Select Save custom URLs and open the page in that language.
5. Play the video or activate its background and confirm the localized recording loads. Check each file format when the background has multiple sources.

The main-language video and any source without a mapping remain unchanged. Detection reads stored content without playing videos or requesting provider metadata.

Understand the replacement contract

POM Translate normalizes the original URL before lookup. A stored target replaces that source for the selected locale in supported menu and rendered-content paths. The source fragment is restored after replacement, allowing a link such as document.pdf#chapter-two to keep its fragment.

The target is a complete URL. Source query parameters are not automatically merged into an unrelated replacement, so include every parameter the destination requires.

When no mapping exists:

• external destinations remain unchanged;
• a recognized file or iframe source remains unchanged;
• an eligible same-site menu link can continue through normal route localization.

Keep the dictionary focused

Do not copy native post, page, archive, or term permalinks into Custom links merely to translate their slugs. Those objects belong under Content URLs, where POM Translate can resolve them back to canonical WordPress IDs.

Custom destinations are never submitted to machine translation. Review them manually for protocol, host, path, query, fragment, access requirements, and regional availability.

Deleting a custom URL row removes the source and all of its locale mappings. Clearing one locale's translated field retains the shared source entry.