Website localization services for continuous releases
Your website, app, and product catalog change with every release, and every language has to keep up. We localize each release, not the whole product again, with the same team, the same glossary, and the same rules each time, so your terms stay consistent across releases. We work inside your translation management system (TMS) or from your exports: agents find what changed since the last release, a native linguist works on it, and an automated quality gate checks every file before it goes back to you.
Releases, not projects
Continuous localization runs on your release cadence, so nobody on your team has to scope a new project each time. We compare each source release with the previous source version. We translate what changed and recheck existing translations affected by changes in context, approved terminology, or product behavior. Approved translations stay in your translation memory (TM), and decisions you approved stay closed. They reopen only when you ask, or when new evidence appears.
A continuous stream of high-volume updates is exactly what this service is built for.
Working inside your TMS, with files that come back intact
We work inside your platform, including Phrase, XTM, Smartling, Crowdin, and Lokalise, or from the exports you send. JSON, XML, XLIFF, PO, HTML, and CSV files all work, as do exports from your content management system (CMS). Files come back in your format, with tags and placeholders preserved.
Automatic checks on tags, placeholders, numbers, and length limits run on the AI output before the linguist sees it. The quality gate then checks the delivered file. If it fails, the file does not ship: the issue goes back into the cycle to be fixed, and the gate runs again. If a delivery is at risk, we tell you before the agreed date.
Context for UI strings
A string without context is a guess. Before we translate a release, we ask for what the linguist needs: screenshots, string keys, and length limits.
UI strings run at AI + Edit or above, so a native post-editor edits every one. Checkout and payment text never runs at AI + Check. Each linguist is a native speaker of the target language and a subject specialist, and the same team stays on your account from release to release.
Website and app localization
Website pages and app UI usually run at AI + Edit. Launch campaigns and brand pages run at AI + Edit + Review, where a second linguist reviews every segment and does a final read of the delivered file.
Your glossary and style rules apply across everything we localize for you, so a feature name reads the same on your website, in your app, and in your help center. Your style rules go into your own rulebook. We turn the rules that can be tested reliably into automatic checks. Linguists judge meaning, tone, and anything else that needs judgment.
Same-day delivery is possible for suitable volumes. We confirm timing in the quote.
E-commerce and product catalogs
Product catalog translation covers two kinds of text. Titles and descriptions sell, so they usually run at AI + Edit, where a native post-editor edits every segment. Long-tail attributes that shoppers only need to understand can run at AI + Check, if you choose it. Attributes that carry safety or compliance data never run at AI + Check.
Terms for product descriptions come from your glossary, your TM, and the listings you have already published, and every term carries its source. Numbers are checked automatically, and the catalog comes back in your format, such as CSV, XLSX, or XML. On request, we localize catalog titles for the search terms shoppers use in each market.
Queries, batched per release
Questions about a string or a term are collected and sent once per release, not one email at a time. The query window is agreed in your contract, so your team knows when questions will arrive. Your answers go into your rulebook and apply to every later release.
What each release delivers
Every delivery includes the quality-gate result and an issue log. At AI + Edit, sampled quality reports follow the schedule agreed for your program and can cover several small releases; at AI + Edit + Review, each delivery gets a full report.
- The changed content, localized and returned in your TMS or export format
- Tags and placeholders preserved
- The quality-gate result and an issue log
- Quality reports: sampled at AI + Edit, on the schedule agreed for your program, and full with every delivery at AI + Edit + Review
- Glossary changes and a query log at AI + Edit and AI + Edit + Review
- Your TM, updated, with a Translation Memory eXchange (TMX) file on request
Pooling small releases into one sampled report gives the sample enough text to be useful. Under a monthly contract, you also receive a monthly quality summary.
Every edit your reviewer makes is compared with what we delivered. Each confirmed lesson becomes a glossary entry, a rule or an automatic check before your next batch.
Questions about continuous localization
Do you work inside our TMS?
Yes. We work inside your platform, including Phrase, XTM, Smartling, Crowdin, and Lokalise, or from your exports. Files come back in your format, with tags and placeholders preserved.
How do you handle string context and length limits?
We ask for screenshots, string keys, and length limits with each release. Automatic checks catch tag, placeholder, and length problems, and a native post-editor edits every UI string.
Can you adapt product titles to local search terms?
Yes, on request. We localize catalog titles for the search terms shoppers use in each market, and the catalog comes back in your format, such as CSV, XLSX, or XML.
How fast can a release come back?
Same-day delivery is possible for suitable volumes. We confirm timing in the quote, and again for each order.
Can different parts of the product run at different levels?
Yes. You choose the service level per content type, and the quote names it. Catalog attributes, UI strings, and launch pages can each run at their own level.