URL Design for Multilingual Web Services

To put it bluntly, the best method depends on the website's requirements.I will explain the advantages and disadvantages of each method, so please make a decision based on the requirements of your website.

The first is routing, but the benefits are well organized and multi-lingualized in a single application for high maintenance.The disadvantage is that if you don't plan to become multilingual and design the URL in advance, it will be troublesome to change it later.

Next, the URL parameter has the advantage of being able to support multilingualization without changing the URL/path of an existing website.The disadvantages can be avoided depending on the framework you are using, but logically, you will have to make sure that each page is multilingual.

While these two are often implementationally commutative, the interpretation of the URL also suggests that the former guarantees that the page is localized for the existing URL, while the latter cannot be guaranteed by the URL.

Finally, the advantage of the (sub) domain is that each language can operate and manage independently.The disadvantage is that as more languages are supported, management becomes more difficult.

For example, domain can easily accommodate large numbers of users or slow networks, but routing can be a high technical hurdle.In addition, the URL parameter will be extremely difficult.

The advantages of one method may be disadvantages of another, so consider it against your needs.