Translate URLs and route visitors

POM Translate gives one canonical WordPress object a language-specific public address. It does this without duplicating the post or term:

1. detect the locale from the request prefix;
2. resolve localized path segments back to the base WordPress object;
3. rebuild links with the target locale's prefix and stored slugs;
4. redirect a resolvable non-canonical path to its current localized form.

Readable content and URL slugs use separate editors. Translating a title does not create its slug, and changing a slug does not translate the title.

Run one complete route test

1. Choose a published page with a simple base-language permalink.
2. Open Translations → Translate URLs → Content URLs.
3. Select Post, search for the page, and choose Load slugs.
4. Enter a distinct Slug for locale and select Save slugs.
5. Follow a link generated by WordPress or the POM Translate language selector.
6. Confirm the language prefix, localized slug, HTTP status, rendered object, canonical URL, and alternate-language links.
7. Repeat with a query string and a fragment if that route normally uses them.

If No base slug is stored for this object yet appears, save the source object in WordPress and load it again.

Understand the URL layers

• Language settings decide whether a locale uses a leading subdirectory.
• Locale codes are converted into unique URL prefixes.
• Content URLs stores post and term slugs per additional locale.
• WordPress rewrite definitions supply post-type and taxonomy route bases.
• Custom links maps external, file, iframe, download, or manually registered destinations.
• SEO output derives canonical and hreflang addresses from the same localized route builder.

Choose a focused guide