Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

WPML Taxonomy Translation Not Working: Causes and How to Fix It

WPML Taxonomy Translation Not Working: Causes and How to Fix It

Short answer

WPML taxonomy translation usually fails because the taxonomy is set to not translatable, translated terms are not assigned to translated posts, or caches show old pages. Check WPML settings first, then translate terms on the Taxonomy Translation screen, sync the hierarchy and clear every cache.

Key takeaways

  • Set each taxonomy to a translatable mode in WPML settings.
  • Translate terms before translating the posts that use them.
  • Check that translated posts carry the translated terms.
  • Sync the hierarchy when child terms lose their parents.
  • Refresh permalinks if translated archives return 404 errors.
  • Clear WPML, plugin and CDN caches before deeper debugging.

Why is WPML taxonomy translation not working?

It usually fails because the taxonomy is set to not translatable, the translated term is not assigned to the translated post, or caching and an outdated WPML setup show old results.

Taxonomies are the groups you use to sort content. In WordPress that means categories, tags and any custom taxonomy a theme or plugin adds, such as product categories or portfolio types.

WPML handles each taxonomy separately. A category can be translated while a custom taxonomy from another plugin is ignored. That is why one taxonomy can work fine while another seems broken.

The symptoms usually look like one of these:

  • The translated page still shows category names in the default language.
  • Category archive pages in the second language are empty or show a 404.
  • A custom taxonomy does not appear on the Taxonomy Translation screen at all.
  • Translated terms save but disappear or revert later.
  • The language switcher on a category page sends visitors to the home page.

If your whole site has translation trouble, not just terms, start with our broader guide on WPML translation not working. This guide focuses on categories, tags and custom taxonomies.

How do you check the taxonomy translation mode?

Go to WPML > Settings, scroll to Taxonomies Translation, and make sure the taxonomy is set to translatable rather than not translatable.

This is the most common cause. WPML only creates language versions for taxonomies set as translatable.

In the Taxonomies Translation section you will see each registered taxonomy with three choices:

ModeWhat visitors see on translated pages
Not translatableThe same terms in every language, never translated
Translatable, only show translated itemsOnly terms that have a translation in that language
Translatable, use translation if available or fallback to default languageThe translation if it exists, otherwise the original term

If a taxonomy is set to Not translatable, the Taxonomy Translation screen will not let you translate its terms. Change it to one of the translatable options and save.

The fallback mode is the safest choice while you are still translating. Visitors see the original term rather than nothing. The WPML guide on translating taxonomies explains each mode.

Is the custom taxonomy missing from WPML?

If a custom taxonomy is not listed in WPML settings, it is often registered late, set as private, or controlled by a wpml-config file from the plugin that adds it.

WPML reads the taxonomies WordPress knows about when the settings screen loads. A taxonomy registered too late, or only on certain pages, may not appear.

Check these points:

  1. Is the taxonomy public? Taxonomies registered with public set to false may be hidden. The register_taxonomy reference lists the arguments that affect visibility.
  2. Is it registered on the init hook? Custom code that registers taxonomies on a later hook can confuse WPML.
  3. Is the setting locked? Some plugins ship a wpml-config.xml file that fixes the translation mode. In that case the option is greyed out, and you need the plugin's own instructions.
  4. Is the plugin compatible? Check whether the plugin that creates the taxonomy is listed as WPML compatible.

If you added the taxonomy yourself with a plugin such as a custom post type builder, re-save its settings and then reload WPML > Settings.

Are the translated terms assigned to translated posts?

Translating a term is only half the job, because the translated post must also be assigned the translated term or the archive in that language will stay empty.

This catches many people. You translate News to Noticias, but the Spanish post still carries no category, or carries the English one.

How assignment usually works:

  • When you translate a post with WPML's translation editor, it brings the post's terms along and assigns the translated versions.
  • When you translate a post manually in the WordPress editor, you must tick the translated terms yourself in the sidebar.
  • When you duplicate content, terms are copied, but they may be the original language terms if no translation existed at the time.

To check, open a translated post in the editor and look at its Categories or custom taxonomy panel. If the wrong terms are ticked, fix them and update the post.

For bulk fixes, translate the terms first and then resend the posts for translation or update them again. Translating terms before posts avoids most of this.

How do you translate terms on the Taxonomy Translation screen?

Open WPML > Taxonomy Translation, choose the taxonomy from the dropdown, and click the plus or pencil icon under each language to add or edit the term name, slug and description.

This screen is where all taxonomy work happens. If it looks empty, pick a different taxonomy from the dropdown, because it shows one at a time.

For each term you can set:

  • Name, the label visitors see.
  • Slug, used in archive URLs.
  • Description, shown on some themes' archive pages.

After you save, the icon changes to show the translation exists.

If you edit term names in Posts > Categories while viewing the second language, that also works. Use the language switcher in the admin bar to change which language you are editing.

You may also want to translate the taxonomy's own label, like the word Category in breadcrumbs. That label is a string, handled by String Translation. See our guide on WPML String Translation not working if those labels stay in the default language.

Is the term hierarchy out of sync?

When parent and child categories do not match across languages, translated archives and menus can break, and the Taxonomy Translation screen offers a button to sync the hierarchy.

Hierarchical taxonomies, such as categories, have parents and children. If Shoes is a child of Clothing in English, its translation should be a child of the translated Clothing.

Problems start when you translate a child before its parent. WPML then has no translated parent to attach it to, so it may end up at the top level.

To fix it:

  1. Make sure every parent term is translated.
  2. On WPML > Taxonomy Translation, look for the option to synchronize the taxonomy hierarchy, which appears when WPML detects differences.
  3. Run it and recheck the term list.

After syncing, reopen a translated archive page in a private browser window to confirm the structure.

Yes, if two languages share a conflicting slug or permalinks were not refreshed after translating terms, translated category archives can return 404 errors.

WordPress needs unique slugs within a taxonomy. WPML manages this, but conflicts can still happen when terms are imported or created by code.

Try these fixes:

  • Give each translated term a distinct, readable slug in its own language.
  • Go to Settings > Permalinks and click Save Changes without changing anything. This refreshes rewrite rules. Our guide to flushing permalinks in WordPress explains why it helps.
  • Check WPML's language URL format, whether directories, a parameter or separate domains, and make sure archive links use it.

If only one language returns 404s, compare its term slugs with the default language. A slug with odd characters or a leading number is often the culprit.

Is caching showing old term translations?

Caching plugins, server caches and WPML's own cache can serve pages built before you translated the terms, so clear all of them before assuming the translation failed.

This is a quick check that often solves the problem. Clear caches in this order:

  1. WPML's cache, under WPML > Support > Troubleshooting.
  2. Your caching plugin.
  3. Any host-level or CDN cache, such as Cloudflare.

Our guide on how to clear WPML cache walks through the WPML part in detail.

The Troubleshooting page also has tools that help with taxonomy problems, such as fixing term counts and setting missing language information for terms. Back up your database before running them, since they change stored data.

Do WooCommerce product categories need extra steps?

Yes, product categories, tags and attributes work through WooCommerce Multilingual, so that add-on must be active and set up for product taxonomies to translate properly.

WooCommerce taxonomies follow the same rules as other taxonomies but are managed through the WooCommerce Multilingual and Multicurrency plugin. It adds its own screens for categories, tags, shipping classes and attributes.

Common issues on stores:

  • Attributes not translating. Global attributes are taxonomies and need translating. Custom attributes added on a single product are text, not terms.
  • Empty shop category pages. Products in the second language are not assigned to the translated category.
  • Wrong filter labels. Layered navigation widgets may cache the old labels.

Check the WooCommerce Multilingual documentation for the right screen for each item. Also review the WooCommerce docs on managing product categories, tags and attributes.

What else should you check before contacting WPML support?

Update WPML and its add-ons, test with only WPML and a default theme active, and check the debug log, since plugin conflicts and old versions cause many term problems.

Work through this short list:

  • Update everything. WPML, String Translation, WooCommerce Multilingual and WordPress itself.
  • Look for conflicts. Deactivate other plugins one by one on a staging copy. SEO and filter plugins sometimes rewrite term queries.
  • Switch themes on staging. Some themes hard-code category names instead of using translated terms.
  • Turn on debugging. The WordPress debugging guide shows how to log PHP errors.

If you imported terms with a CSV tool, they may lack language information. Re-import using WPML-aware settings or set the language with the troubleshooting tools. Our guide to importing categories in WordPress covers the import side.

If none of this helps, open a ticket on the WPML forum. Include the taxonomy name, the plugin that registers it and a screenshot of the Taxonomies Translation setting.

Frequently asked questions

Why does my custom taxonomy not appear in WPML?

WPML only lists taxonomies that WordPress registers in the normal way. If the taxonomy is private, registered late or locked by the plugin's configuration file, it may be hidden or greyed out. Check how the plugin registers it and whether that plugin is listed as compatible with WPML.

Should I translate terms or posts first?

Translate terms first. When terms already have translations, WPML can assign the translated versions automatically as you translate posts. If you translate posts first, you may need to go back and fix the terms on each translated post by hand.

What does fallback to default language mean?

It means that when a term has no translation in the current language, WPML shows the original term instead of hiding it. This keeps archives and menus working while you are still translating, and it is a safe setting for most sites during setup.

Why are my translated category pages empty?

Usually the translated posts are not assigned to the translated category, or the term was set to only show translated items. Open a translated post, check its category box, and make sure the translated term is ticked. Then clear your caches and reload the archive.

Can caching stop term translations from showing?

Yes. Page caches and CDNs may keep serving pages built before you translated the terms. Clear the WPML cache, your caching plugin and any CDN cache, then reload the page in a private browser window to see the current version.

Sources

  1. How to Translate WordPress Taxonomies WPML
  2. WooCommerce Multilingual and Multicurrency WPML
  3. register_taxonomy() WordPress Developer Resources
  4. Debugging in WordPress WordPress Developer Resources
  5. Managing Product Categories, Tags and Attributes WooCommerce

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.