Running on top of Google’s App Engine, the same infrastructure that powers Gmail and other Google services, the proxy route provides benefits unheard of elsewhere, such as automated change detection, CSS/JS-injection capabilities, and a worldwide CDN accelerating page serving.
Because this way, the proxy handles all aspects of the translated site, and the content owners only need to focus on creating the source content, it is ideal for clients looking for a hands-off approach and just want to see translations appear on their website - if they “just want to go to Disneyland” (Neal Stephenson), the proxy route can provide that.
In order to be able to translate the content, first it needs to be extracted. This is achieved by using Easyling’s specialized crawler to map out the site and grab its contents for translation. The crawler can be configured to visit only specific areas of the site while ignoring others, or even restricted to a list of pages provided by the client to establish a canonical scope for translation.
Once the translations are complete, they need to be made available to the world at large. Easyling offers two main ways of achieving this, with the choice left to the content owners.
Arguably the easier of the two, with domain publishing, Easyling provides you/the client a number of DNS records that, once inserted, allow Easyling to hook into the communication between the visitor and your server. Requests for the translated content are directed to the proxy instead of the original and are served via Easyling itself.
Of course, this is not restricted to subdomains, Easyling can, just as easily, work with new top-level domains if the content owner would prefer that route.
This method allows the fastest operation and quickest time-to-market. DNS changes are visible across the globe quickly and allow you to leverage Easyling’s world-class CDN with global points-of-presence.
Sometimes, however, subdomains just won’t cut it. For these situations, Easyling also has the ability to publish translations on path prefixes. Thus, the original site
https://www.divesites.net/en/ will become available at
https://www.divesites.net/ja/ in Japanese.
This method is slightly more involved, since it requires the content owner to have or deploy a reverse proxy or an appropriate CDN in front of their website, which may not be to everyone’s liking. It may also increase time-to-market, especially if the CDN needs to be deployed from scratch.
However, it seems to have better support as far as SEO is concerned, and marketing departments seems to prefer this option.
Once launched, via either method, the proxied translated site is available as long as your site is. Any new content the owner releases can be picked up for translation immediately upon viewing (in fact, this is the default mode of operation), and translation can be made (almost) fully automatic in a process we call Continuous Translation Delivery.
Even without this continuous translation capacity, Easyling’s proxy can alert the translation vendor to new content, so that the linguists can get to work and translations can be kept up to date with minimal turnaround.