Kentico - LionBridge Integration and Automation

Common Integration Use Cases Between Kentico and Lionbridge

1. Automated Website Content Translation Workflow

Data flow: Kentico ? Lionbridge ? Kentico

When marketing teams publish or update web pages in Kentico, the content is automatically sent to Lionbridge for translation and localization. Once approved, translated versions are returned to Kentico and published to the appropriate language sites. This reduces manual copy-paste work, shortens launch cycles for multilingual campaigns, and helps global teams maintain consistent messaging across regions.

2. Multilingual Campaign Landing Page Localization

Data flow: Kentico ? Lionbridge ? Kentico

Campaign landing pages built in Kentico can be routed to Lionbridge for translation before regional launch. This is especially useful for product launches, promotions, and event registrations that need to go live in multiple markets at the same time. The integration supports faster campaign rollout, better localization quality, and fewer delays caused by manual translation coordination.

3. Translation of Digital Asset Metadata and Descriptions

Data flow: Kentico ? Lionbridge ? Kentico

Marketing teams often manage image captions, document titles, alt text, and other content metadata in Kentico. These fields can be sent to Lionbridge for translation so that assets are usable across multilingual websites and campaigns. This improves searchability, accessibility, and consistency of content presentation in each market.

4. Localization of Product and eCommerce Content

Data flow: Kentico ? Lionbridge ? Kentico

For organizations using Kentico for eCommerce, product descriptions, category pages, promotional banners, and checkout messaging can be translated through Lionbridge. This enables localized shopping experiences without requiring teams to manually manage each language version. The result is improved customer experience, stronger conversion rates in international markets, and more efficient product content operations.

5. Translation Request Routing Based on Content Status

Data flow: Kentico ? Lionbridge

Kentico can trigger translation jobs automatically when content reaches a defined workflow stage, such as editorial approval or pre-launch readiness. Lionbridge receives the content package with language requirements and returns status updates during the translation process. This creates a controlled workflow for content teams, reduces missed translation requests, and improves governance over multilingual publishing.

6. Regional Content Updates and Re-translation Management

Data flow: Kentico ? Lionbridge ? Kentico

When source content changes in Kentico, only the modified sections can be sent back to Lionbridge for re-translation. This is valuable for regulated industries, product documentation, and frequently updated marketing content. It minimizes translation costs, keeps regional sites aligned with the source version, and reduces the risk of publishing outdated information.

7. Global Content Governance and Review Collaboration

Data flow: Bi-directional

Content teams can manage source content in Kentico while localization teams use Lionbridge to review, translate, and validate language quality. Status updates, approval outcomes, and completion signals can flow back into Kentico to support publishing decisions. This improves cross-team visibility, strengthens governance, and helps ensure that only approved localized content is released.

8. Multilingual Knowledge Base and Support Content Publishing

Data flow: Kentico ? Lionbridge ? Kentico

Organizations using Kentico for customer support content, FAQs, or knowledge base articles can automate translation through Lionbridge to serve global audiences. As articles are updated in the source language, translated versions can be refreshed and republished across regional sites. This reduces support overhead, improves self-service adoption, and helps maintain consistent customer information worldwide.