How many languages ​​do we plan to have?

[rochon.a1.119]

EN: mydomain/en/section-1

EN: mydomain.com/en/section-1

ITA: mydomain.com/it/sezione-1

But we can also have a folder structure without the first level with the initial of each language.

Continuing with the previous example it would be like this:

EN: mydomain/section-1

EN: mydomain.com/section-1

ITA: mydomain.com/section-1

Between the two options, both have their pros and cons.

The first is, without a doubt, the one that most easily allows us to understand which version of the language we are using and that has its advantages for both the user and the development team.

On the other hand, at the SEO level, it is better to have cleaner URLs, with only descriptive terms of the page, without the language folder.

As always, the choice depends a lot on the specific context:


What types of URLs?
How many?
In any case, both solutions are good as they provide a structure that is easier to build and develop as your site and business grows and changes.

Its flexibility makes it the best solution if you don't want belarus mobile database to sign up for a language yet (for example because you don't have the resources to do so) but you do trust in doing so in the medium term.

Setting up a subfolder structure allows you to use the same structure for any future ccTLDs or subdomains for country sections in the future.

Additionally, the development team will appreciate this option because it is also scalable to implement hreflang tags (especially if we have a folder with the language initials)

Parameters allow for a backup system in case tagging fails on a future site update.