How to Translate a Category Base Slug in WPML Without Breaking URLs

A translated category name can look perfect while the URL still exposes /category/ or /product-category/ in the wrong language. That small mismatch is easy to overlook—until it makes a carefully localized store or content site feel unfinished, confusing visitors and muddying the URL structure you intended for each market.

If you need to wpml translate category base slug safely, the distinction matters: this is not about translating individual category labels such as “Shoes” or “News.” It is about the taxonomy base itself—the fixed URL segment WordPress places before every category archive. With WPML already installed and configured, changing that segment can produce cleaner, more natural localized links without sacrificing the routes your site already relies on.

The catch is that rewrite rules, translations, and existing URLs have to stay aligned. One incorrect setting can leave visitors facing 404 pages or send search engines mixed signals—so the right approach starts with knowing exactly which slug WordPress is actually using.

Understand What WPML Can Translate in Taxonomy URLs

Category base slug vs. category name and term slug

One misplaced translation can change every category archive URL on a site. That is why the category base and the category term must be treated as separate parts of the permalink.

In /product-category/shoes/, product-category is the taxonomy base: the fixed segment shared by all product category archives. shoes is the term slug, identifying one specific category. The visible category name may be “Shoes,” while its slug remains shoes; neither is automatically the base.

When people search for how to wpml translate category base slug, they often edit individual category translations instead. That changes the final segment only. To localize the shared URL structure, you need WPML’s taxonomy-slug or permalink-base controls, not merely a translated term name.

Which taxonomy bases can be translated

WPML can handle bases for WordPress’s built-in taxonomies, including categories and tags, when the relevant translation and permalink settings are configured. It can also work with custom taxonomies registered by a theme or plugin, such as a portfolio type, location, brand, or recipe cuisine.

WooCommerce is where this distinction becomes especially visible. A store may use URLs such as /product-category/shoes/, where product-category is the base, alongside product tags and attribute-related archives. Translate the base deliberately for each language, while translating individual product-category terms separately. Otherwise, you can end up with localized category names inside an unchanged—or inconsistently changed—URL structure.

Requirements before changing a base slug

Changing a base affects many URLs at once, so preparation matters more than speed.

• Confirm that WPML is installed, active, and functioning as the site’s multilingual framework.
• Enable and configure the target languages before creating translated bases.
• Create a recent full backup of the database and site files.
• Make sure you can access WordPress permalink settings, since saving permalinks may be necessary to refresh rewrite rules.

Also check existing redirects and sitemap entries after the change. A translated base is useful for local SEO, but only if old archive URLs resolve cleanly and each language keeps one consistent taxonomy structure.

How to Translate the Category or Taxonomy Base Slug in WPML

Enable translated custom post type and taxonomy slugs

A translated category archive can still look unfinished if its URL keeps the original base. For example, a Spanish archive at /product-category/zapatos/ is understandable, but not fully localized. To wpml translate category base slug, open WPML > Settings and find the URL slug translation settings. Enable translation for custom post type and taxonomy bases, then ensure the relevant taxonomy is configured as translatable in WPML’s taxonomy translation settings.

Add the translated base slug for each language

WPML exposes registered bases for translation through its slug or string-translation interface, depending on the WPML version and configuration. Find the taxonomy base you want to change—such as product-category—and enter a natural, URL-safe equivalent for each secondary language.

• English: /product-category/shoes/
• Spanish: /categoria-producto/zapatos/
• French: /categorie-produit/chaussures/

Use lowercase words, hyphens instead of spaces, and avoid accents or punctuation where possible. The base should describe the archive type, not a specific category.

Save permalinks to flush rewrite rules

After saving the translated base, go to Settings > Permalinks and click Save Changes. Do this even if you change nothing on that screen. WordPress stores URL patterns as rewrite rules; saving permalinks rebuilds them so the new localized archive URLs resolve instead of returning a 404 error.

Translate taxonomy terms separately

The base is only one part of the URL. Translate each category or taxonomy term in WPML > Taxonomy Translation, including its name and slug. Otherwise, you may get a localized base paired with an untranslated term slug—technically valid, but inconsistent for visitors and search engines.

Test the New URLs and Prevent Common SEO Issues

Check archive pages in every language

A translated base slug can look perfect in the editor and still fail where visitors actually navigate. After you wpml translate category base slug, open each taxonomy archive directly in every language, then switch languages from the archive itself. Test paginated URLs as well: a category page that works at page one but breaks at /page/2/ is a common missed problem.

Also follow links generated by menus, widgets, breadcrumbs, product-category blocks, and WooCommerce shop pages. These links should point to the new language-specific archive path, not the former default-language base.

Clear caches and regenerate plugin-specific links

Do not trust the first result you see. Clear WordPress cache plugins, server or hosting cache, CDN cache, and your browser cache before testing again in a private window. Cached HTML can preserve old archive links long after WPML has updated its rewrite rules.

Then inspect SEO and breadcrumb plugins closely. Yoast SEO, Rank Math, caching tools, and theme breadcrumb systems may hold generated URLs until their own cache or index is rebuilt. If an old slug persists, regenerate that plugin’s links or data before assuming the WPML configuration failed.

Redirect indexed archive URLs when they change

If the old archive URL has been indexed or has earned links, add a permanent 301 redirect to the matching new archive URL. This matters most for established WooCommerce stores changing paths such as /product-category/shoes/; leaving that address to return a 404 throws away both traffic and accumulated signals.

Check Google Search Console and crawl reports after deployment. A small number of temporary 404s may be harmless, but repeated hits on old taxonomy paths are a clear case for redirects.

Avoid duplicate or mixed-language URL patterns

One archive should have one intended URL per language. Inconsistent term translations, hard-coded menu links, or incomplete WPML URL-format settings can leave both the old and translated paths accessible. That creates confusing navigation and can dilute indexing signals.

Search your site for the former base slug, test canonical tags on archive pages, and make sure each language switcher link resolves to its proper equivalent rather than a mixed-language fallback.

Use Affordable AI Translation Inside Your Existing WPML Workflow

Translate WPML content with LATW AI Translator for WPML

Fixing a category base slug is usually a one-time configuration task. Translating an entire site is where costs can quietly get out of control. Once you have used WPML to translate category archive URLs, posts, products, metadata, and SEO fields still need consistent treatment across every language.

LATW AI Translator for WPML is built for that next stage. It is an add-on, not a standalone multilingual plugin: an active WPML installation is required, and WPML continues to manage languages, URLs, translation relationships, and its wider multilingual workflow. LATW simply adds a more flexible AI translation engine within that familiar setup.

Using your own API key, the plugin sends content directly from WordPress to your selected AI or translation provider. There is no intermediary LATW server handling the text. That approach can substantially reduce the cost of high-volume work compared with credit-based translation systems, while giving you a choice among current providers and engines.

For a site owner trying to wpml translate category base slug settings correctly, the practical advantage is consistency beyond the URL itself. LATW can translate body content, excerpts, slugs, taxonomies, custom fields, metadata, and SEO fields through WPML, so a localized category archive does not lead visitors to partially translated product pages.

Its bulk translation tools are particularly useful for stores and content-heavy sites. Queue many items at once, apply a glossary to protect product names and preferred terminology, add website context for tone, and retranslate only the content that changed rather than paying to process an entire page again. WPML’s built-in automatic translation remains an option, but LATW is the sensible upgrade for teams that already rely on WPML and want more control over quality and spend.

Make the URL Change Part of Your Localization Plan

When you WPML translate a category base slug, treat it as an SEO and navigation change rather than a cosmetic edit: configure the base-slug translation, translate the individual terms, save your permalink settings, then test every affected archive in each language. If old URLs have already been indexed or shared, add appropriate redirects so visitors and search engines still reach the right destination.

A carefully localized taxonomy structure makes your site easier to browse in every market without sacrificing the visibility you have already earned. Translate deliberately, validate the routes, and let every language lead visitors somewhere clear.