Background of the issue:
I’m trying to understand why, when I attempt to create an automatic translation of a product using WPML, the slug automatically includes a -2 at the end. The original product’s slug is /product-name/. When I create three automatic translations in three different languages, the result for all languages is /product-name-2/.
Symptoms:
Questions:
How can I keep the original slug in the automatic translations?
Welcome to the WPML support forum. Before passing this thread to my colleague, I would like to share some suggestions and possible solutions for the issues you mentioned.
Sorry for the late response because of the holidays and the high support load. It is not normal here. Thank you for your kind understanding.
Translating a post or page using the same slug as the original will automatically add a language code suffix to the translated version. This happens because the WordPress API does not allow duplicate slugs for posts or pages within the same site.
So this is an expected result. Please refer to the following links for more details and let us know your feedback.
I’m already familiar with the suggested workaround, and I’ve actually applied it. But you can surely understand that if I have to automatically translate an entire website and then go back to review 600 pages, this becomes a real issue.
If there’s a known workaround, it means that WPML could potentially anticipate this situation and handle it automatically. Don’t you think?
I’m asking you to provide a solution that prevents me from having to manually recheck a huge number of pages before they get indexed by Google. As you know, once they’re indexed, I won’t be able to change the URLs without additional work – and that’s definitely something we’d prefer to avoid.
Regarding WPML handling slugs like in the workaround. That's a feature that's on our backlog for WPML 4.8, but is not currently available. It may be implemented for that version, but I can't promise it will be.
Hi Otto, first of all—thank you. I’m glad to hear that you’re considering integrating this properly into the plugin. Honestly, I have to laugh a bit at how you heavily advertise the idea of translating a whole site with one click… only to discover countless small issues afterwards.
I’m sure you’ve noticed I’ve opened several tickets in recent days. They all relate to real-life challenges that an E-Commerce Manager faces due to things WPML doesn’t currently handle. There’s still a long way to go—really. We’re not quite at the “one-click translation” stage yet.
That said, thank you again.
I look forward to updates. We need to translate our site in the coming weeks and, as mentioned, we simply can’t go through and double-check the slugs of hundreds of products in multiple languages.
As far as I can see, all the other tickets are already being handled. I hope we can help you with all those issues.
Best Regards,
Otto
Manage Cookie Consent
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
