Multilingual Publishing 
A truly search engine friendly multilingual site
Multilingual support is a must for your company's website if you plan to expand internationally. Not all multilingual sites are created equal.
In case you wonder what a "proper" multilingual website should consists of, look no further than the website you are currently on. The Inga website is fully engineered to support multiple languages, and more important, to enable communication with our multilingual staff.
Here are the top characteristics a multilingual site should have:
1. Per-Page Language Correlation
Many websites divide up content into sub sites for each language. You might see page links such as
www.mysite.com/en/about
and
www.mysite.com/de/about.
These websites also have a language selector at the landing page. Once a language is chosen, the audience is confined to the realm of the selected language. Although it is technically possible to provide a link from the English version the About page to its German counterpart, many websites are not set up this way. It is common to see "unbalanced" content completeness where the dominate language has all the pages, and the pages for the other languages are few and far between.
On the Inga site, you may switch language on any page. This feature alone makes the site properly multilingual.
2. Localized URLs
Some websites address the issue of Language Correlation by organizing content on a page level instead of a language grouping. You can identify these sites by looking at their link structure:
www.mysite.com/deals?lang=en
www.mysite.com/deals?lang=de
The above links not only look cumbersome. They also miss out the opportunity of being indexed in its other supported languages. If you are actively targeting the German market, "angebote" works much better than "deals?lang=de". Similarly, "predlozheniya" helps your page rank better in the Russian market.
You might be wondering, why don't many websites translate their links if URL localization is so important? The answer is scale and complexity. A complex website is often dynamically generated. The numerous items in a web storefront can be translated, but the content engine has to
Our Approach
In case you wonder what a "proper" multilingual website should consists of, look no further than the website you are currently on. The Inga website is fully engineered to support multiple languages, and more important, to enable communication with our multilingual staff.
Here are the top characteristics a multilingual site should have:
1. Per-Page Language Correlation
Many websites divide up content into sub sites for each language. You might see page links such as
www.mysite.com/en/about
and
www.mysite.com/de/about.
These websites also have a language selector at the landing page. Once a language is chosen, the audience is confined to the realm of the selected language. Although it is technically possible to provide a link from the English version the About page to its German counterpart, many websites are not set up this way. It is common to see "unbalanced" content completeness where the dominate language has all the pages, and the pages for the other languages are few and far between.
On the Inga site, you may switch language on any page. This feature alone makes the site properly multilingual.
2. Localized URLs
Some websites address the issue of Language Correlation by organizing content on a page level instead of a language grouping. You can identify these sites by looking at their link structure:
www.mysite.com/deals?lang=en
www.mysite.com/deals?lang=de
The above links not only look cumbersome. They also miss out the opportunity of being indexed in its other supported languages. If you are actively targeting the German market, "angebote" works much better than "deals?lang=de". Similarly, "predlozheniya" helps your page rank better in the Russian market.
You might be wondering, why don't many websites translate their links if URL localization is so important? The answer is scale and complexity. A complex website is often dynamically generated. The numerous items in a web storefront can be translated, but the content engine has to
Our Approach
- content block mapping
- page identity and reverse URL resolution
- text label dictionaries
- multilingual slug stems
Estimated implementation cost: €1.200,00
find this useful?