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 Translation Not Working: Causes and How to Fix It

WPML Translation Not Working: Causes and How to Fix It

Short answer

Check that the translation is complete and published, and that the post type is set as translatable in WPML settings. Translate theme and plugin text in String Translation, confirm automatic translation credits remain, then clear every cache and resave permalinks.

Key takeaways

  • Check each language status icon: in progress or needs update means visitors see no translation.
  • Post types set as not translatable always show in the default language.
  • Theme, widget and plugin text is translated in String Translation.
  • Do not mix WPML's translation editor with direct edits on the same page.
  • Automatic translation stops when credits run out.
  • Clear caches and resave permalinks after translating.

Why is WPML translation not working?

WPML translations usually fail because the translation is unfinished or outdated, the content type is set as not translatable, strings are not registered, automatic translation has run out of credits, or a cache is serving the original page.

Not working can mean several different things with WPML.

A translated page may show the original language. Some text, such as a button or footer, may stay untranslated. Or automatic translation may never finish.

Pin down which of these you see before you change settings. The sections below match each symptom to its likely cause.

New to the plugin? Our guide on how to use WPML covers the normal setup, which helps you spot what is missing.

Is the translation complete and published?

Open WPML > Translation Management or the language columns in the post list, and check that the translation exists, is complete and is published rather than in progress or needing an update.

WPML shows a status icon for each language next to every post and page. The icons tell you whether a translation is missing, in progress, complete or out of date.

Common status problems:

  • In progress translations are not visible to visitors yet.
  • Needs update means the original changed after it was translated.
  • Draft translations exist but are not published.

If you edit the original page, WPML flags its translations as needing an update. Open the translation, review the changed text and complete it again.

Is the content type set as translatable?

Go to WPML > Settings and check the post types and taxonomies sections; anything set to not translatable will always show in the default language.

Custom post types from themes and plugins sometimes default to not translatable. Examples include portfolio items, team members, events and some WooCommerce data.

For each type, WPML offers options such as:

OptionWhat happens
Not translatableContent only exists in the default language
Translatable, only show translated itemsUntranslated items are hidden in other languages
Translatable, use translation if available or fallbackUntranslated items show in the default language

Pick the option that fits your site, save, then translate the content. Custom fields have their own translation preferences on the same settings screen.

Why is some text still in the original language?

Text from your theme, plugins, widgets or page builder often lives outside the post content, so it must be translated through String Translation rather than the post editor.

This is the most common WPML complaint. The page body is translated, but the header, footer, buttons or form labels stay in English.

Where that text usually comes from:

  • Theme and plugin strings such as Read more or Add to cart.
  • Widgets and menu labels.
  • Page builder global elements and templates.
  • Customizer text, such as a footer copyright line.

Open WPML > String Translation, search for the text and translate it there. If the text is not listed, use WPML's theme and plugin localization screen to scan for strings.

Themes and plugins must also be built for translation. The WordPress internationalization guide explains how developers prepare text. Our guide on translating a WordPress plugin shows the same process from the site owner's side.

Is the translation editor set up correctly?

If edits in the translation editor do not appear on the page, check which editor WPML uses and avoid editing translations in the normal WordPress editor when WPML's editor manages them.

WPML can use its Advanced Translation Editor or let you edit translations directly in WordPress. Mixing the two causes problems.

If you edit a translation in the normal editor, WPML may overwrite your changes the next time someone updates it through the translation editor. Pick one method per page and stick with it.

Page builders add another layer. Elementor and others store layouts in special formats, so WPML needs its compatibility support for that builder. Our guide on using WPML with Elementor covers the details.

Has automatic translation stopped?

Automatic translation stops when your translation credits run out, when the job is paused, or when content is waiting in a queue for review.

WPML's automatic translation uses credits. When they are used up, new or updated content waits in a queue instead of translating.

Check these:

  • Your remaining credit balance in WPML's translation settings.
  • Whether automatic translation is switched on for the languages you need.
  • Whether translations are set to need review before publishing.
  • The translation queue for jobs that are stuck.

If jobs stay stuck for a long time, WPML's support or troubleshooting screen has options to resend or clean up translation jobs. Take a backup before using cleanup tools.

Is caching showing the wrong language?

A page cache, CDN or optimization plugin can serve the original page to visitors on translated URLs, especially if it caches by URL without knowing about languages.

Signs of a caching problem:

  • The translation looks right when logged in but wrong in a private window.
  • Switching language shows the old version until you clear the cache.
  • Visitors see mixed languages on one page.

Clear every cache layer after translating. Our guide on clearing the cache in WordPress covers plugin, server and CDN caches.

If you use a language-by-cookie or browser-redirect setup, check that your cache supports it. URL-based language formats, such as a language folder, are easier to cache safely.

If translated pages return 404 errors, resave your permalinks and check the language URL format in WPML's language settings.

Go to Settings > Permalinks and click Save Changes without changing anything. That rebuilds WordPress rewrite rules, which often fixes 404s on translated URLs.

If you use a different domain per language, each domain must point to the same WordPress install. DNS or SSL problems on a language domain can look like translation problems.

For search engines, WPML adds language tags to link versions of the page. Google's guide on localized versions of pages explains how those tags work.

Are menus or the language switcher missing?

Each language needs its own menu, so translate or sync menus with WPML's menu sync tool and check that the language switcher is enabled in a menu, widget or footer location.

If the menu shows default language links on translated pages, the translated menu is missing or not assigned to the theme location.

To fix it:

  1. Open WPML's menu sync screen.
  2. Sync your menus so each language gets a copy.
  3. Translate any menu labels that did not translate automatically.
  4. Check WPML > Languages for language switcher settings.

Could a conflict be breaking WPML?

Yes; another plugin or the theme can override language detection or the query WPML uses, so test with other plugins turned off on a staging copy.

Use the free Health Check & Troubleshooting plugin to test safely. Keep WPML, its add-ons and the plugins related to the problem active, then turn the rest off.

If the translation works with plugins off, turn them on one by one. Our guide to fixing a plugin conflict covers the full process.

What should you send to WPML support?

If none of the fixes work, send WPML support a debug report, the URL of an affected page and the exact symptom, such as which text stays untranslated.

WPML includes a support screen with debug information about your setup. Copy it into your ticket.

The WPML getting started guide is also worth rereading. Many issues come from a step skipped during setup, such as String Translation not being installed.

Make sure WPML and all its add-ons are updated to matching versions. Mismatched add-on versions are a common cause of odd behavior after updates.

Frequently asked questions

Why does my translated page still show English text?

The page body may be translated, but headers, footers, buttons and widgets often come from the theme or plugins. Translate that text in WPML's String Translation. If the text is missing there, scan the theme or plugin for strings first.

Why did my WPML translation disappear after I edited the page?

Editing the original marks its translations as needing an update, and some changes may not carry over until you complete the translation again. Open the translation in WPML's editor, review the changed segments and save to publish the updated version.

Why is automatic translation in WPML stuck?

Usually the translation credits ran out, the job is waiting for review, or a queue job failed. Check your credit balance and the translation queue. WPML's troubleshooting tools can resend stuck jobs, but take a backup before running cleanup options.

Why do translated pages show a 404 error?

Rewrite rules may be out of date or the language URL format may not match your server setup. Resave permalinks under Settings, then check WPML's language URL settings. For separate domains, confirm each one points to the same site.

Can a caching plugin break WPML?

Yes. A cache that does not separate languages can serve the default language on translated URLs. Clear all caches after translating, and prefer language folders or subdomains over cookie-based language detection when caching is in use.

Sources

  1. Getting Started With WPML WPML
  2. Internationalization WordPress Developer Resources
  3. Tell Google about localized versions of your page Google Search Central
  4. Health Check & Troubleshooting WordPress.org

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.