Open
Overview of the issue
Since the release of WPML SEO 2.2.0 we can translate term meta from WPML’s Translation Dashboard as “String Packages” allowing you to have them automatically translated together with the rest of the site:
Until now, these had to be translated by editing the translated terms.
Our intention was to keep displaying manually translated terms until a string translation was made, which would override our manual translation. But this is not working correctly and we are always displaying the translation from the string package instead.
Workaround
- You can roll back to WPML SEO 2.1.1 to keep using manual translations.
- Or you can visit WPML’s Translation Dashboard and translate the “Yoast SEO Term Meta” string package.
Next steps to resolve this issue
Next WPML SEO release will resolve this issue.
Hello, when will this issue be solved? We are on WPML SEO 2.2.5 and the issue is still there…
Hi Javier, it will be fixed in the next release.
Hello Nicolas, got it, thanks, is there a date scheduled for this new release? Will we be able to disable completely the use of strings for these Yoast term metas so as to avoid having to maintain duplicate information?
Hi Javier,
This issue has been tagged for WPML SEO 2.3.0. However, I can’t share an ETA at the moment.
This issue was introduced in 2.2.0 which was released on June 18th 2025. Since then you released 5 new versions. Not a single one of them fixed this issue.
Please Nicolas, tell me. How is this even possible? What is such a priority that a known bug that hurts SEO for many customers who use Yoast is so low on the list that it can be ignored for more than a year?
Hi Tom,
I’ve asked directly to the developers, and a fix is ready and will be released together with WPML 5.0. Unfortunately, I can’t provide an exact ETA yet.