WPML and Yoast SEO

We are sorry to hear that you’re having trouble. Can you please share a relevant screenshot in which you highlight the issue you’re experiencing so that we can take a look at it?

We look forward to hearing from you.

Yes,
from here you can see the WPML String Translation page. As you can see, the string is translated. https://www.dropbox.com/s/01996m59d8wv6bw/WPML%20-%20String%20Translate.png?dl=0

Here, instead, you can see the Yoast Seo section of the page: https://www.dropbox.com/s/ewd3pb663oj28ip/Yoast%20SEO%20-%20not%20translated.png?dl=0

As you can see, the string appears not translated.

However, here you can see the relative page source code: https://www.dropbox.com/s/ekw1170p4vbi51y/Source%20Code.png?dl=0

As you can see, the string is translated correctly and in the meta-description it appears exactly what it should appear.

So the problem is related only to what the Yoast Seo section shows in the metadecription filed and in the google preview field.

I hope I was able to explain the problem.

Best regards
Giovanni

Hi,

Just to confirm, could you let us know if you are using the latest version of WordPress 5.6.1, Yoast SEO for WordPress 15.7, and the latest version of WPML? Do you also have the Yoast SEO Multilingual plugin (by WPML)?

You can learn more about it here — https://wpml.org/documentation/related-projects/using-wordpress-seo-with-wpml/

Hi, yes, I can confirm.
WordPress: Version 5.6.1
Yoast SEO for WordPress: Version 15.7
Yoast SEO Multilingual: Version 1.2.4
Easy Digital Downloads Multilingual: Version 1.3.4
WPML Multilingual CMS: Version 4.4.9
WPML String Translation: Version 3.1.7
WPML Translation Management: Version 2.10.5

I’ve already followed the instructions on the link you sent me. It shows how to manually translate all the pages, including seo attributes. It could works for ecommerce with few items. We don’t need this approach. We want translate in automatic way all the “content types” and “taxonomy” filed of Yoast Seo, in search appearance.

And, as I explained before, all works perfectly: in the source code of the page you can see that the fields are translated correctly.

What doesn’t work is this:
Let’s take our beats as an example. We use a modified version of EDD, so our beats, are basically EDD items, which are usually called “downloads”.

1. On Yoast Seo / Search Appearance / Content Types, I write the default Seo description and the default title.

2. On WPML string translations, in the admin_text_wpseo_titles section I’m going to enter the relevant translations.

3. At this point in the source code of the pages the translations are created correctly.

However, if I check a random beat from the backend (an EDD item),in the Yoast SEO section, the italian translations do not appear, it keeps showing the English versions.

So, to sum up, it’s a problem of Yoast SEO visualization, because in the source code of the pages the translations are correctly created.

I hope I was able to explain the problem. Anyway, it is not a big problem. Just that at the beginning, not seeing the translation in the yoast seo section of the beats, we thought that this was not happening correctly.

Then, following this support ticket,
we discovered that in the source code of the individual beats pages in Italian, meta-description and seo title were translated correctly.

We appreciate you for clarifying everything. We now understand the issue better.

Based on the information you provided, we think it’s a bug specific to the Yoast SEO snippet preview as the snippet preview fails to show translated data even though the output values on the front end part seems correct.

So, if you have a spare moment to share with us, please do feel free to submit a proper bug report directly at our GitHub development repository so our development team can look into this further.

We actively track bug reports and feature requests in our GitHub development repository rather than here. It will help you to follow the progress of the relevant bug report as well.

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.