Configure Weglot’s Content Delivery Network for a fully translated website in minutes. Edit your DNS settings to create specific subdomains for each new language and point them to the Weglot servers – our reverse proxy servers will automatically retrieve your website pages, detect the original content and swap it for the translations.
Any request for a translated version of your website will deliver blazing fast results to your customer in their native language. Plus, a layer of cache on top of the Weglot translation API means if the exact same translation request is sent twice, it will remember the answer and send it back to you instantly. Weglot’s reverse proxy solution provides you with a fully SEO-friendly version of your website that’s easily indexed by global search engines.
A website translation solution with zero developer effort
The Weglot proxy server is hosted on servers distributed in locations around the world. Your website visitors will have a fast, secure, and seamless experience when it comes to viewing your site in their language as they’ll be closer to the source of data. Weglot has a 99% uptime SLA.
Your translations are stored on the Weglot database. The Weglot database is fully backed up daily.
Weglot stores all the HTML fragments it translates as well as their translations. It also stores data associated with your project settings, such as glossary rules. You can exclude translations by URL or more finely by CSS selector in order to avoid sending confidential data, such as personally identifiable information (PII), to Weglot.
By default after a project is removed at the termination of the contract, any stored data is removed after 180 days of inactivity – this can be deleted sooner upon request.
Yes, no user data is stored by Weglot. Our translation database is located in AWS Frankfurt.
Weglot’s service is 24/7 with a 99% service level guarantee.
Yes. Weglot reverse proxy servers will automatically retrieve your website pages, detect the original content and swap it for translations.
Yes – You can translate any content by directly calling our API. Read our API documentation for more information.
It depends on what you want URLs to look like for your users.
If you want to use subdomains and have your Spanish-translated products page available on es.example.com/product, you’ll need to create 1 CNAME record per translated language and associated subdomain and point them to websites.weglot.com.
If you want to use subdirectories (currently in beta), and have your translated products page available on example.com/es/product, you’ll need to create a single A record for your entire domain pointing to a Weglot IP address you’ll get during onboarding.