Skip Navigation

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

Problem:
The client is unable to prevent page slugs from being translated following the documentation on translating page slugs.
Solution:
1. Navigate to WPML → Settings and scroll to Translated documents options.
2. Under Page URL, choose one of the following options:
- Autogenerate from the title: The slug will be created from the translated page title.
- Translate: Allows translating the default language slug.
- Copy: This will copy the slug from the default language, but it only works if the language uses encoded URLs, which can be set in WPML > Languages > Edit language settings (applicable for languages like Chinese or Russian).
After changing these settings, re-translate the pages for the changes to take effect.

If the 'Translate' option is selected, make a small change to the default language page, save it, and resend it for translation to create a new translation job.
For more information, refer to a related ticket.

Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, 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 3 replies, has 2 voices.

Last updated by Dražen Duvnjak 9 months, 1 week ago.

Assisted by: Dražen Duvnjak.

Author Posts
February 22, 2024 at 11:34 am #15333194

christopherA-19

I'm following the documentation here: https://wpml.org/documentation/getting-started-guide/translating-page-slugs/

None of the options, however, seem to prevent page slugs from being translated.

February 22, 2024 at 1:31 pm #15333803

Dražen Duvnjak
Supporter

Languages: English (English )

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

Hello,

thanks for contacting us.

Post and Page slugs are automatically created from the title.

1. Go to WPML → Settings. Scroll to Translated documents options.

2. Under Page URL, you can choose:

- Autogenerate from the title - it will be created from the translated page title
- Translate - translate default language slug
- Copy - it will work only if the language is using encoded URLS from WPML > Languages > Edit language settings, for example for Chinese or Russian letter/language

When you change these settings you will need to re-translate pages to take effect.

Also, you can always manually edit the slug and adjust it from the WordPress admin screen.

Hope this helps, let me know if you have any other questions.

Regards,
Drazen

February 22, 2024 at 2:20 pm #15334065

christopherA-19

Ok, so I chose "Translate (this will include the slug in the translation and not create it automatically from the title)", however, when I go to translate the page, I don't see the slug anywhere to translate. It seems to just take what I put for the title and use that as the slug. Here's the page in question: hidden link

How do I keep the slug untranslated while being able to translate the title?

February 22, 2024 at 3:04 pm #15334263

Dražen Duvnjak
Supporter

Languages: English (English )

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

Hello,

if you selected Translate, you need to make a small change to the default language page (for example title) save and resend it to translation, so a new translation job is created. Or create a new job by sending a page for translation from WPML > Translation Managment.

To keep the slug untranslated and copy from the default language, you can select the copy option and then from WPML > Languages > Edit languages > For correct language select > Encode URLs > Yes.

Same here you will need to make small changes and translate page.

Related ticket: https://wpml.org/forums/topic/keep-slugs-in-english/#post-13467395

Make sure, this language requires encoding of characters, as said this is applied to non standard languages with special characters like Chinese, Japanese etc.

Let me know if any further questions.

Regards,
Drazen

February 23, 2024 at 3:50 am #15335993

christopherA-19

Looks like that worked. Thank you.