Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is concerned about the URL encoding for Russian language links on their website, which appear with encoded characters instead of Cyrillic characters. They are worried this might negatively impact their SEO.
Solution:
We explained that the behavior observed is not an issue and is not related to WPML. URL encoding is a standard way for browsers to handle links containing non-ASCII characters, ensuring that search engines can read the URLs correctly. When hovering over the link with the mouse pointer, the browser will display the correct URL at the bottom. Therefore, there is no need for concern as this is the correct and expected behavior for URLs.

If this solution doesn't look relevant, please open a new support ticket.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 1 reply, has 2 voices.

Last updated by Carlos Rojas 1 year, 3 months ago.

Assisted by: Carlos Rojas.

Author Posts
November 22, 2023 at 2:46 pm #14899405

CaGlarA

This is my website link for the issue i am having: hidden link

When i am copying a link for the russian language its copy with some codes for example:

hidden link

However the original link is: hidden link

I dont have this problem for the othre languages only for russian I have problem like this.
This will be very bad for my seo, I need to fix this. How can i fix it?

Thanks

November 23, 2023 at 9:48 am #14905703

Carlos Rojas
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/Madrid (GMT+01:00)

Hello,
Thank you for contacting us

This is not an issue and it is not related to WPML. This is the way the links are encoded, so the search engines can read the link correctly. If you hover the link with the pointer of the mouse you will see the correct URL at the bottom of the browser 🙂

So, there is nothing to be worried about, this is the correct and expected behavior.

Regards,
Carlos