instead of a human-readable format, this is due to URL encoding, commonly known as percent-encoding. Solution: We recommend using the "Copy from original language if translation language uses encoded URLs" option. This will copy the original slug instead of using encoded URLs for the translated pages. You can find detailed steps on how to do this in our documentation:
Well, it is gibberish for humans and that is what matters.
And it is not good for SEO either, so it matters for machines too.
And I think it is not true - that you can't do anything about it.
WPML should have an option for users to specify a naming convention for translated page URLs.
Right now, we have to manually switch to the Chinese version of the page and edit the URL by hand, for example, we changed the Chinese version of this page to /thank-you-zh/.
When you have hundreds of pages on your site, this is a tedious process.
Again, I strongly urge WPML to provide a URL naming convention option during the translation process.
Thanks, your answer makes much more sense than your colleague's.
Just to clarify, if we use the "Copy from original language if translation language uses encoded URLs" option, will WPML add a suffix to the URL to distinguish the translated page from its original?
copy means it will always copy the original value 1:1 and show it with a language suffix. If Chinese is your default language, it will be copied in Chinese and shown with /en together with the Chinese letters.
For example, we created a thank you page in English... Then we translated the page into Chinese, but we notice that the URL to the Chinese page is like this:
Chinese is your default language. You created the page in Chinese and translated it into English. Technically, the solution is correct, but if you want the Latin characters as your "main" slug, it might be worth considering changing your default language to use English and keeping Chinese as a translation. This way, a slug such as "about-us" will be turned into /zh-hans/about-us.
This is a Chinese language website targeting the Chinese market, so web pages must show up in Chinese by default. We have to set Chinese as the default language to achieve this.
On the backend, we always create pages in English first and then translate it into Chinese. It works for the website and it works for us so far, with the exception of the page URLs.
With our workflow, how will WPML create the Chinese page URLs with the "Copy from original language if translation language uses encoded URLs" option turned on? Remember, the original language is English.
On the backend, we always create pages in English first and then translate it into Chinese. It works for the website and it works for us so far, with the exception of the page URLs.
It was technically possible in translation management, as there is a language switcher, but it is possible to get issues with the page sync. Therefore, we did not recommend this workflow.
The 4.5.9 release published today allows the creation of jobs from a secondary language, but the permalink has no changes. If you select "copy", it will copy from your default language, Chinese.
Best Regards
Marcel
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
