Paid - Slide 6

If you’re responsible for enabling website translation at your company, you’ve probably run into this:

As the business expands into new markets, content needs to be updated into new languages. And that means that engineering gets pulled into string extraction, CMS workarounds, and deployment coordination.

This guide outlines a technical approach that removes website localization from your engineering backlog entirely.

You can deliver fully localized websites in real time without modifying your application code or maintaining separate language builds using Smartling’s Global Delivery Network (GDN), a translation proxy.

In this technical guide, you’ll see how to:

  • Route localized traffic through a translation proxy before it reaches your origin server
  • Automatically capture and translate HTML, JavaScript, JSON, and dynamic content
  • Control what gets translated using rules, tags, and scope management
  • Deploy new languages without rebuilds or redeploys
  • Handle untranslated content gracefully while preserving SEO and performance

The guide walks through the full lifecycle of capture, translate, and deploy with practical implementation details for engineering and product teams.