GlobalLink Web introduces GL Web Studio for in-context editing, a rebuilt batch workflow, and new search tools. See what's new for your multilingual site.
Imran Sadiq
Updated on March 17, 2026
Managing a multilingual website involves constant review, approvals, and coordination across pages, languages, and stakeholders. The latest GlobalLink Web update focuses on making those day-to-day workflows easier to run, with improvements spanning in-context editing, sitewide search and review, and translation approvals.
This release introduces GL Web Studio, a new in-context editing suite with live preview and “what you see is what you get” (WYSIWYG) tools, alongside a fully rebuilt batch workflow designed to be more interactive and easier to use. Your existing configurations and translation memory remain intact, so nothing is disrupted.
Read below to learn the latest developments.
GlobalLink Web is a website localization solution that enables fast, secure, and scalable multilingual site deployment. It’s platform-agnostic and can be deployed via JavaScript injection or proxy-based technology, so teams can publish multilingual sites without integrating with a CMS, PIM, or e-commerce platform. It supports AI, human, and hybrid workflows, plus multilingual SEO capabilities.
GL Web Studio is the biggest addition in this release: a full in-context editing suite lets you view and edit translations directly on a live preview of your site. Instead of working in a spreadsheet-style editor and guessing how your copy will look, you now see exactly how each translation renders, complete with smart CSS adjustments that account for text expansion and layout shifts.
The studio includes WYSIWYG linguistic editing, so translators and reviewers can click into any segment on the page, make changes, and see the result in real time. It’s designed to speed up review cycles and reduce the back-and-forth that comes from working outside the visual context of the site. For a detailed walkthrough, visit the GL Web Studio overview on GL Knowledge.
When you make a linguistic edit in-context, you now choose what happens to the text segment’s status. Three options are available: push the edit Live immediately, revert the segment to Pending so it goes through your approval workflow, or Retain the segment’s current status. This matters most for teams that separate editing from approval. A translator can make fixes without accidentally publishing them, and a reviewer can push approved changes live in one step.
Page Edit introduces a contextual translation memory (TM) approach: you can now make linguistic edits that apply only to the page you’re working on, without overwriting the same segment everywhere else in your translation memory. This is particularly useful for SEO optimization, where you might want a keyword variation on a specific landing page but don’t want it propagated sitewide. Think of it as a scoped override. Your global TM stays clean, and the page-specific edit lives exactly where you need it.
Across the in-context editing experience, you’ll notice a series of UI and UX improvements, including cleaner layouts, better visual hierarchy, and a reorganized workspace. These changes aren’t just cosmetic. The updated design makes room for more features that are coming later this year.
If your workflow relies on machine translation (MT) with post-editing, you’ll appreciate the new Approve MT action. Previously, machine-translated segments sat in an intermediate state unless manually moved. Now, once a post-editor is satisfied with the output, they can mark it as approved, which saves the translation permanently to your TM. The result: a cleaner pipeline for MT-heavy projects, with a clear audit trail of what’s been reviewed and what hasn’t.
The batch workflow has been overhauled with a focus on interactivity and clarity. Whether you’re in Translate mode, Testing mode, or Review mode, the interface now gives you a much more intuitive path through each step.
Here’s what changed:
Review mode now supports a more structured approval process, helping demonstrate translation value to stakeholders.
Two new search pages give you direct access to your content. The Source Segments Search lets you look up any source segment across your entire project. The Translation Search lets you find source/translation pairs for a specific language. Both pages support inline linguistic editing and other critical actions directly from the search results, with no need to open a separate editor. If you’ve ever needed to find and fix a specific term across your site, this is where you’ll do it.
If you’re an existing GlobalLink Web user:
New to GlobalLink Web? Learn how it can help you launch and manage multilingual websites with no back-end integration. Visit the GlobalLink Web product page to see the full list of capabilities and deployment options.
Want to learn more about the GlobalLink platform?
Do I need to migrate my content to use GL Web Studio?
GL Web Studio is available within your existing GlobalLink Web (JS) environment. Your translation memory, glossaries, and configurations carry over. Ask your implementation manager and they’ll help you get started.
Will Page Edit override my global TM entries?
No. Page Edit creates a scoped, page-level override. Your global TM remains unchanged. If you later remove the page-level edit, the global TM entry takes over again.
Can I use the new search pages to make edits, or are they read-only?
You can edit directly from the search results. Both the Source Segments Search and Translation Search support inline linguistic editing and other key actions without requiring you to open a separate tool.
Does Approve MT change how machine translation works in my project? No—it adds a step, not a change. Your MT workflow runs the same way. Approve MT simply lets post-editors confirm that a machine-translated segment is ready, saving it permanently to your TM so it’s reused going forward.
Imran Sadiq
Vice President of Technology Solutions, TransPerfect
