Logic of the structure of a multilingual website

Hello everyone. Our web studio has launched a multilingual website with three languages (Ukrainian, Russian, and English). The default main language is Ukrainian. Our programmer created a separate subdirectory for each language: domain/ua/, domain/ru/, domain/en/. The main domain is redirected with a 301 redirect to the language subdirectory, so the language subdirectory serves as the homepage. We argued that for the default main language, there's no need to create language subdirectories, and instead use an alias structure without the redundant language category. Language subdirectories are fine for additional languages, but not necessary for the main language. However, the programmer responded that they always do it this way and all clients are satisfied... Is this a new trend or is the programmer inexperienced? Can you advise if this website structure is acceptable?
The website is: b-granum.com.

 

I'd have the source language without a subdir and keep the other two subdirs. I wouldn't do that for SEO purposes though, I don't think the SEs care about that. It'll just look neat.

 

Both approaches - using language subdirectories or an alias structure - can be acceptable for creating a multilingual website. However, there are some factors to consider when deciding on the best approach for your particular website.

Using language subdirectories for all languages, including the default main language, is a common approach and has some benefits, such as:

• Consistency: This approach maintains the same structure for all languages, which can make it easier to manage and update the website.
  
  
• Scalability: If you plan to add more languages in the future, using language subdirectories from the beginning can make it easier to scale the website.
  
  
• SEO: Using language subdirectories can help with search engine optimization (SEO), as it allows search engines to easily identify the language of the content on the website.
  

However, using an alias structure for the default main language can also be a valid approach, and has some benefits as well, such as:

• Simplicity: Using an alias structure can simplify the website structure and make it easier to navigate for users.
  
  
• Branding: Using an alias structure can help to reinforce the website's branding, as it avoids adding the language subdirectory to the URL.
  

Ultimately, the decision on which approach to use depends on the specific needs of your website and the preferences of your team. If you are happy with the current approach and it meets your needs, then it may not be necessary to make any changes. However, if you would like to explore other options, you can discuss it further with your team and programmer, and evaluate the pros and cons of each approach before making a decision.