How to Translate Page and Post Slugs in WPML Without Breaking Links

A perfectly translated page can still feel wrong when its URL remains stuck in another language. A Spanish visitor who sees /pricing or a German reader landing on /about-us may understand the content—but the mismatch can weaken trust, click-through confidence, and the relevance signals you want search engines to see.

Learning how to wpml translate url slug is straightforward, but changing a slug also creates a new URL. That is where an innocent localization task can turn into broken internal links, lost referral traffic, or avoidable SEO problems. With WPML already installed and configured, the key is to translate the right field, preserve the old path where needed, and verify the details that keep every language version reachable.

Before You Translate a URL Slug in WPML

A translated slug is small, but it sits at the centre of a page’s address, internal links, redirects, and search visibility. Change it before the multilingual setup is sound, and a tidy URL can quickly become a 404 error or an unindexed duplicate.

Confirm that WPML languages and URL format are configured

First, make sure the page or post already has a translation in the target language. WPML cannot attach a meaningful translated slug to content that does not yet exist in that language. Then check WPML’s language URL format, because it determines the final address visitors and search engines see.

• Language directories: example.com/fr/services
• Different domains: example.fr/services
• Language as a parameter: example.com/?lang=fr

For SEO-focused sites, directories or separate domains are usually clearer than parameters. Whichever format you use, test the translated URL after saving it rather than assuming the slug alone controls the full path.

Check your WordPress permalink structure

Use a readable permalink structure such as Post name. Plain permalinks, which use URLs like ?p=123, leave little practical value in translating a slug and can complicate troubleshooting. If a new URL does not resolve after you wpml translate url slug settings, visit Settings → Permalinks and click Save Changes once. This refreshes WordPress rewrite rules; it is often the fix for an unexpected 404.

Choose a localized slug, not a word-for-word rewrite

The best slug is written for the target-language searcher, not copied mechanically from English. Keep it short, use the local term people actually search for, and separate words with hyphens. For example, an English running-shoes page may need a locally preferred equivalent rather than a literal translation.

Accents are generally safe in modern URLs, but many teams remove them for consistency and easier sharing. More importantly, avoid duplicate slugs within the same language. Before publishing, search existing pages, categories, and products for conflicts—especially where WordPress may silently append -2.

How to Translate a Page or Post Slug in WPML

A translated title is not enough for a clean multilingual URL. If the English page remains /pricing in every language, visitors may still understand it—but local search intent and URL clarity suffer. To wpml translate url slug correctly, edit the permalink on the translated post itself, not on the original.

Open the translation in the target language

In the WordPress admin area, find the page or post you want to localize. Use the language controls shown in the post list, or open WPML’s Translation Management list and select the completed translation for the relevant language.

The important distinction is easy to miss: WPML creates a linked version for each language. Open the target-language version—for example, the French translation—not the English source post. Changing the source permalink changes the source URL; it does not assign a French slug to the French translation.

Edit the permalink slug in the WordPress editor

With the translated post open, look in the block editor’s right-hand settings sidebar for the URL or Permalink panel. Click the slug field, replace the automatically generated value with the localized version, then click Update or save the translation.

For instance, an English page at /en/our-services could use /fr/nos-services for French. Keep slugs short, readable, and consistent with the language’s normal spelling. Avoid changing the post title just to force a URL; the slug field gives you precise control.

Verify the translated URL on the front end

Open the target-language page in a private browser window and confirm the new URL loads without a 404 error. Then use the site’s language switcher to move between languages. Each option should lead to its matching translation, even though the final URL segment is different.

If the old translated slug has already been indexed or shared, add a redirect where appropriate. A correct new permalink is only half the job; preserving useful inbound links prevents an avoidable loss of traffic.

Translate Slugs for Custom Post Types, Taxonomies, and Archives

Translate individual custom post type entries

A product URL has two moving parts, and confusing them is how multilingual links quietly go wrong. The individual entry slug is the final segment: /products/red-shoes/. In WPML, a translated custom post type entry—whether it is a product, portfolio item, listing, or testimonial—can have its own localized slug just like a translated page or post.

Open the entry’s target-language edit screen, set the permalink slug in that language, and update it. For example, an English product called “Red Shoes” might use /products/red-shoes/, while its French translation uses /produits/chaussures-rouges/. This is the right approach when you need to wpml translate url slug for one specific item rather than an entire URL structure.

Translate category, tag, and taxonomy slugs

Taxonomy terms have their own slugs too. Edit the category, tag, or custom taxonomy term in its target language, then enter a localized term slug before saving. A “Summer Sale” product category, for instance, may become soldes-ete in French.

Afterward, visit the translated term archive and inspect links in navigation menus, breadcrumbs, product filters, and internal content. These elements often expose a missed taxonomy translation faster than the WordPress editor does.

Translate custom post type archive bases separately

The archive base is not an individual post slug. In /products/red-shoes/, products is the custom post type archive rewrite base; changing “red-shoes” will not translate it.

For archive bases and taxonomy rewrite bases, use WPML’s post type and taxonomy slug translation settings. Set the translated rewrite base for each language, save the changes, then go to Settings > Permalinks and save once more to flush WordPress rewrite rules. Finally, test every language archive directly. A correct editor setting means little if /fr/produits/ still returns a 404 or redirects to the default-language archive.

Keep Old URLs Working After a Slug Change

Add a 301 redirect from the old translated URL

A translated slug is not just a label; once Google, a customer, or a partner has seen it, it becomes part of your site’s public infrastructure. If the old URL was indexed, shared on social media, included in an email campaign, or linked from another website, create a one-to-one 301 redirect to the new translated URL immediately. This preserves referral traffic and tells search engines that the page has moved permanently rather than disappeared.

Use a trusted WordPress redirect tool or server-level configuration, and redirect the exact old-language path to its matching replacement. For example, an old French URL should point to the new French URL, not merely to the English original. After saving the redirect, test it in an incognito browser and confirm that it returns a 301 status rather than a temporary 302.

Update internal links, menus, and canonical signals

A redirect catches old visitors, but your site should stop sending new visitors to the old address. After you wpml translate url slug values, check navigation menus, in-content links, breadcrumbs, related-post modules, and footer links. A single outdated menu item can create an avoidable redirect chain across every page view.

Then validate the SEO signals WPML outputs for the translated page: the canonical URL should reference the new URL, and hreflang entries should connect the correct language versions. Review the XML sitemap as well, ensuring it contains the new address rather than the retired one. Finally, open the translation in WPML and confirm its language, translation relationship, and permalink all match the intended page.

Speed up WPML content translation with LATW AI Translator for WPML

For teams translating dozens of pages or posts, LATW AI Translator for WPML can reduce the manual workload without replacing WPML. It is an add-on, not a standalone multilingual plugin: WPML still manages languages, URLs, and translated-content relationships. LATW works within WPML’s translation workflow and sends content directly through your own AI or translation-provider API key, making bulk translation and ongoing updates far easier to manage.

Make Every Localized URL Earn Its Place

For a safe WPML translate URL slug workflow, update the target-language page or post slug first, manage archive bases and taxonomy slugs through their relevant WPML settings, then test the finished URL before publishing it widely. If an older address has already been indexed, shared, or linked elsewhere, add a redirect so visitors and search engines reach the new version without encountering a dead end.

Localized slugs are more than translated keywords: they are part of how people recognize, trust, and navigate your site in their own language. Choose wording that matches local search intent and reads naturally in the address bar—then protect that work with careful testing and redirects. A good multilingual URL should feel written for its audience, not merely converted for it.