Community Information
-
•
Approach to urls / slugs when localising a web page
I am doing a huge rehaul of our webpage, lots of new pages and urls. We're also adding a new language. Which poses a question of urls. I think it makes sense that the url language matches the content of the page, right? so /riskmanagement and /riskijuhtimine (Estonian) However now that I started localising the urls, my urls are like this: /riskmanagement /et/riskijuhtimine. So basically the difference is that the Estonian one has the language code extra. Should I a) force language code for the English language as well b) try to avoid the language slug in both (I am not sure if I even can do this with translatepress c) doesn't really matter as long as the content is good an the final word matches with the content3
© 2025 Indiareply.com. All rights reserved.