Proxy & JavaScript comparison 

1. Integration, Setup & Onboarding


Easy to complex, depending on client architecture and requirements


Easy, only requires settings in the site template (single line of JavaScript inserted)

2. SEO Support


Excellent, Content extracted by default, Search engines crawl translated content. URL translation is supported,

JavaScript Content extracted by default.

Advanced: DNS setting or CDN is used to serve translated content

Simple: Search engines run JavaScript to obtain translated content for indexing.

SEO domain might be different.

3. Site Search

Proxy & JavaScript

Available; dedicated search layout effort needed.

4. Latency, Performance


Highly scalable, lowest latency.

Great use of global Content/Translation Delivery Network (CDN).


Rely on the viewer's device (mobile/ tablet/desktop). Start after the page+dictionary loaded. Tiny overhead, flickering possible upon the first load.

5. Deployment options, URL, header, titles


DNS and/or CDN configuration.

Subdomain ( or subdirectory ( For better latency, existing CDN caching can be leveraged CDN is needed for subdirectory.


Single line of JavaScript insert.

Can be blended with existing JavaScript one-liner. Subdomains/Subdirectories supported via CDN

6. Security


Equal to the original.

Proxy does not modify existing site security


Not applicable .

Client-side translation does not impact site security.