Your Cart
WPML translated URL slugs

How to Translate WordPress URL Slugs with WPML Without Losing Multilingual URL Control

Multilingual WordPress URLs involve more than translating a page title. WPML separates several decisions that are easy to confuse: the slug of an individual page or post, the base slug of a custom post type, the base slug of a taxonomy, the slugs of individual taxonomy terms, and the broader format used for language URLs. Treating these as one setting can make configuration and troubleshooting unnecessarily difficult.

This guide explains the documented WPML workflows for translating URL slugs and choosing between translated and copied slugs. It also covers custom post types, taxonomy terms, non-Latin characters and the checks worth completing before changing established URLs. Before applying changes to a live site, create a backup or test on staging, because published slug changes can affect existing links, bookmarks, internal links, redirects and search-engine URLs.

What WPML URL Slug Translation Controls

A URL slug is the readable part associated with an individual content item, such as a page or post. In a multilingual site, that individual slug is only one layer of the URL. WPML also distinguishes the base used by a custom post type from the slug of one specific item in that post type. Taxonomies add another layer: the taxonomy base and the slug of an individual term are configured separately.

This distinction matters for ordinary WordPress content as well as for categories, tags, brands, product categories and other custom taxonomies. A translated term slug does not automatically mean that the taxonomy base has been translated, and changing a base does not replace the need to review individual terms.

Three URL decisions to keep separate

Use the following framework when reviewing the settings:

  • Individual content slug: the slug assigned to a page, post or comparable content item.
  • Custom post type or taxonomy base slug: the shared URL layer used by that content type or taxonomy.
  • Overall language URL format: whether languages use directories, separate domains or subdomains, or language parameters.

The overall language URL format is not the same as translating a content slug. URL and SEO results can also depend on the site’s permalink structure, redirects, sitemap setup, caching, SEO configuration and server configuration.

How to Translate Page and Post Slugs

For ordinary pages and posts, begin in WPML at Settings → URLs and SEO and review the Page URL setting. WPML documents an automatic option that can generate a slug from the translated title. This approach reduces manual editing, but the resulting URL still needs to be checked in the context of the site’s language settings and permalink configuration.

The other documented choice is Translate. This makes the URL slug available for translation in the Advanced Translation Editor. The translator or editor can then provide a language-specific slug for the translated page or post. This is useful when the visible URL should reflect terminology used by the target audience, but it introduces an additional editorial decision that should be applied consistently.

Automatic generation versus manual translation

Automatic generation and manual translation are not universally better or worse choices. Generation from the translated title can be suitable when the site wants a predictable workflow based on translated content. The Translate option provides more direct editorial control over the slug itself.

After selecting the preferred approach, review representative translated pages and posts rather than assuming every URL is correct. Pay attention to the language version, the visible slug and the surrounding URL structure. If the page or post already has published links, record the current URLs before making changes. Afterward, check internal links, bookmarks and redirects, and configure redirects where needed. Do not treat a successful setting change as proof of a particular SEO result.

Translating Custom Post Type Base Slugs

Custom post type base slugs require a separate configuration step from ordinary page and post slugs. WPML supports translating these URL bases, but the relevant post type must be made translatable. The documented workflow includes enabling translation of custom post type and taxonomy base slugs in the applicable WPML settings, configuring the post type in Post Types Translation, and then setting different base slugs for different languages.

This process concerns the shared base, not automatically the slug of every individual entry. A site can therefore need to review both the post type’s archive-level URL and the URL of an individual item. The exact result should be tested on the actual site, because the available documentation does not independently verify every theme, permalink structure or third-party plugin combination.

Base slug versus individual item slug

Consider a custom post type base as one configuration layer and each item’s slug as another. When the base is translated, verify an archive or listing URL where applicable, then open representative individual entries in each language. This helps identify whether the intended change affected the shared base, the item slug, or both.

Before changing an established custom post type URL on a live site, use a backup or staging environment. After testing, check for broken links and review redirects. A configuration that works for one post type or one language should not be treated as proof that every integration on the site behaves identically.

Translating Taxonomy Terms and Taxonomy URL Bases

WPML handles taxonomy translation separately from ordinary post translation. Individual terms can have translated names, descriptions and slugs. This applies to categories, tags and other custom taxonomies, including taxonomies used for products or supplied by a theme or plugin. The taxonomy’s own base slug is configured separately from the terms within it.

If a custom taxonomy is not available for translation, it may be marked as not translatable by default. In that situation, review Taxonomy Translation and enable the taxonomy before attempting to translate its terms. The required setting depends on how the taxonomy was registered, so do not assume that every taxonomy supplied by a theme or plugin is immediately ready for translation.

A practical taxonomy troubleshooting path

Use a simple diagnostic sequence when taxonomy URLs are not behaving as expected:

  1. Check whether the taxonomy is enabled for translation in the Taxonomy Translation settings.
  2. Separate the term-level task from the taxonomy base task. A translated term slug does not replace configuration of the base slug.
  3. Test translated term archives and confirm that the term name, description and slug appear as intended.
  4. Review internal links after saving changes, especially where existing term URLs were already published.

Check both the taxonomy base and several translated term archives. Avoid promising uniform behavior across third-party taxonomies without testing the actual site setup.

Translate or Copy the Original Slug?

WPML provides an alternative to translating every slug: copy the original-language slug into secondary languages. This can be appropriate when the team prefers one consistent source-language slug across translations or when translated URLs would create characters that are difficult for the intended audience to read or share.

A translated slug may be preferable when target-language terminology matters in the visible URL and editors need direct control over that terminology. A copied slug may simplify maintenance where the source-language structure is already established. Neither approach should be presented as a universal SEO rule. The decision should reflect readability, editorial requirements, existing links and the team’s ability to maintain consistent URLs.

A maintenance-focused decision checklist

Before selecting an approach, ask:

  • Is target-language terminology important in the visible URL?
  • Would encoded characters be difficult for the intended audience to read or share?
  • Would changing an established slug create additional link and redirect work?
  • Can the editorial team apply the same URL policy consistently across languages?

If existing URLs are already in use, prioritize controlled testing and link review over a simple preference for translated or copied slugs. Back up the site or use staging before changing them, then check internal references, bookmarks and redirects. The choice is a design and maintenance decision, not a guarantee of cleaner indexing, higher rankings or an absence of redirects.

Non-Latin Languages and URL Encoding

Non-Latin languages require a closer look at how the slug will appear. WPML documentation describes transliteration when Translate is selected for a language using a non-Latin script. In that workflow, the translated slug is represented with Latin characters rather than retaining the original script in the visible URL.

WPML also documents an option to use encoded URLs for a language and copy the original-language slug when the translation language uses encoded URLs. This avoids creating a translated encoded slug by retaining the original-language value. Original-script, percent-encoded and transliterated representations are different choices; none should be described as inherently unsafe or invalid without testing the site’s environment.

Transliteration and copying are different choices

Transliteration changes how a translated slug is represented by converting it into Latin characters. Copying retains the original-language slug instead of creating a translated encoded slug. Test both the URL appearance and the sharing workflow for representative pages, language switchers and content links. Browser, server and sharing behavior can depend on the site configuration, so do not assume that one option is superior in every case.

Verification Checklist Before Publishing Changes

URL changes should be verified as a complete multilingual workflow, not only as a saved WPML setting. Test translated and untranslated versions of representative content and record which slug approach was selected for future editors.

Final pre-publish checks

  • Open representative page and post URLs in each language.
  • Check custom post type archives and individual entries separately.
  • Check taxonomy bases and translated term archives separately.
  • Review internal links, redirects and existing bookmarks after changes.
  • Review sitemap, canonical and hreflang output through the site’s existing SEO setup without assuming a particular result.
  • Back up or stage established URL changes before publishing them.

WPML slug translation is easiest to manage when each URL layer is treated separately: ordinary content slugs, custom post type bases, taxonomy terms, taxonomy bases and the overall language URL format. Translated slugs and copied original slugs are both documented options, and the right choice depends on language terminology, readability, editorial control and the existing link structure. Test before publishing, check broken links and redirects, and review the site’s current permalink and SEO configuration. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.

Free Worldwide shipping

You can download the products right away at wpbetterplugins.com

Immediate delivery

After the payment is credited, the product is ready for download

International Warranty

Offered in the country of usage

100% Secure Checkout

Stripe / Apple Pay / Google Pay / MasterCard / Visa

Zadzwoń