# Don't hardcode language slug in multilanguage website **URL:** \ **Category:** HubSpot Ideas\ **Tags:** content\ **Created:** [August 31, 2020, 8:32pm UTC](https://community.hubspot.com/t/dont-hardcode-language-slug-in-multilanguage-website/24823 "2020-08-31T20:32:36Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![finn](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/finn/32/102498_2.png) [@finn](https://community.hubspot.com/u/finn)\ **Post date:** [August 31, 2020, 8:32pm UTC](https://community.hubspot.com/t/dont-hardcode-language-slug-in-multilanguage-website/24823/1 "2020-08-31T20:32:36Z")
Right now in CMS, if I set a page’s language to French, the URL gets a hard-coded language slug: [www.domain.com/fr-fr/page-name](http://www.domain.com/fr-fr/page-name) where the “fr-fr” bit is hardcoded, i.e. not changeable by the website editor / super admin. Similar for all languages (e.g. Brazilian=pt-br, Danish = da or da-dk, etc). The website URLs should be flexible, so I can decide what my URL structure should be. No hardcoding of a part of the URL. If I want the Brazilian site to be e.g. [domain.com/br/](http://domain.com/br/) then I should be able to choose that. If I want to have a page in Brazilian Portuguese directly under the main domain (e.g. [domain.com/precos](http://domain.com/precos)) next to a page in English (e.g. [domain.com/prices](http://domain.com/prices)) then it should be possibe. Don’t for a language code into the URL just because the page itself is in a different language. ---
**Author:** ![Alicia-AXXAIR](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/alicia-axxair/32/4861_2.png) [@Alicia-AXXAIR](https://community.hubspot.com/u/Alicia-AXXAIR)\ **Post date:** [September 28, 2020, 2:10pm UTC](https://community.hubspot.com/t/dont-hardcode-language-slug-in-multilanguage-website/24823/2 "2020-09-28T14:10:30Z")
I totally agree !! We want to create our website in Korean and they normally use “co.kr”… Hubspot is offering “ko-kr”. I am afraid users might not find us this way. ---
**Author:** ![BBrinkman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bbrinkman/32/51304_2.png) [@BBrinkman](https://community.hubspot.com/u/BBrinkman)\ **Post date:** [December 9, 2021, 3:16pm UTC](https://community.hubspot.com/t/dont-hardcode-language-slug-in-multilanguage-website/24823/3 "2021-12-09T15:16:25Z")
I’m trying to use Content Staging for a Multi-language site. It would work great if not for this hardcoded language slug issue. Here is the scenario I’m running into. **Working:** If we have a Spanish page called **[http://mysite.com/es/test](http://mysite.com/es/test)** ; this page will Stage and Publish perfectly. **Not Working:** If we have an English page called **[http://mysite.com/test](http://mysite.com/test)** ; this page will Stage, but will not Publish correctly. When you go to the Publish step there is a discrepancy in the URL. Staging forces the URL to change to **[http://mysite.com/en-us/test](http://mysite.com/en-us/test)** and will not publish the staged page to **[http://mysite.com/test](http://mysite.com/test)**. ---
**Author:** ![DanielRamirez](https://avatars.discourse-cdn.com/v4/letter/d/5daacb/32.png) [@DanielRamirez](https://community.hubspot.com/u/DanielRamirez)\ **Post date:** [December 10, 2021, 7:58pm UTC](https://community.hubspot.com/t/dont-hardcode-language-slug-in-multilanguage-website/24823/4 "2021-12-10T19:58:09Z")
Yeeees! We have the same problem! Would love to have a “.com/br” website for our Brazilian public, but our only options are “.com/pt” for Portuguese, or “.com/pt-br”, very clumpsy 😐! Pleeease add this feature! The option to select the way you want your language slug to display, and even not display at all? Would be great. ---
**Author:** ![finn](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/finn/32/102498_2.png) [@finn](https://community.hubspot.com/u/finn)\ **Post date:** [April 4, 2023, 12:41pm UTC](https://community.hubspot.com/t/dont-hardcode-language-slug-in-multilanguage-website/24823/5 "2023-04-04T12:41:50Z")
Three years later this is still hardcoded to these clumsy and non-friendly URL slugs. Speaking with Hubspot support today though they told me that “Our development team is constantly monitoring this forum to improve the tool as much as possible.”, which sounded like a joke. It certainly doesn’t fit very well with that so many issues on these forums are open after 3, 4, 5 years… ---
**Author:** ![finn](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/finn/32/102498_2.png) [@finn](https://community.hubspot.com/u/finn)\ **Post date:** [September 18, 2024, 8:43pm UTC](https://community.hubspot.com/t/dont-hardcode-language-slug-in-multilanguage-website/24823/6 "2024-09-18T20:43:53Z")
entering 5th year of “idea submitted”. Hubspot language for “we don’t care enough about non-US websites”? ---
**Author:** ![BBrinkman](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/bbrinkman/32/51304_2.png) [@BBrinkman](https://community.hubspot.com/u/BBrinkman)\ **Post date:** [September 19, 2024, 5:58pm UTC](https://community.hubspot.com/t/dont-hardcode-language-slug-in-multilanguage-website/24823/7 "2024-09-19T17:58:30Z")
This ‘bug’ bascially breaks the abilty to use Content Staging with multilanuage sites. Oringal English pages often don’t have /en but staged pages require /en. So long story short you get errors when trying to launch staged pages because the URLs don’t match. So your \*\*bleep\*\* if you have a large site you want to do a redesign 👎 Hubspot, please consider making a change to how this feature works.