JavaScript-based translation could be a good fit for cases when the ongoing costs of the translation proxy or the fact that a 3rd party proxy provider is involved in foreign traffic raises issues for the website owner.
How does JavaScript-based translation work? In case of JavaScript-based translation, the website owner injects a JavaScript snippet into the website. When a foreign visitor comes to the site, this JavaScript downloads the corresponding TM and replaces all segments on the actual page in the visitor’s browser real-time.
Easyling’s Javascript-based translation features
* Word Count
* Automatic Change Detection
* Onsite Search
* Seamless TMS / CAT Tool Integration
Pros Since the translation happens in the visitor’s browser, no 3rd parties or ongoing translation proxy costs are involved.
Cons For the very same reason, as the foreign version is created in the visitor’s browser on-the-fly, it is not visible for most search engines, so it’s not optimal for SEO. However, if SEO is not a priority (for example, in case of web applications), JavaScript-based translation is a good fit.
The differences between Proxy- and JavaScript-based translation | ||
Proxy-based | **JavaScript-based** | |
Where the translation takes place | at the Proxy provider | in the visitor's browser |
3rd party is involved in foreign traffic | Yes | No |
Ongoing cost applied for foreign traffic | Yes | No |
SEO-friendly | Yes | No |