Managing marketing across multiple regions often reveals a recurring challenge: keeping content consistent across languages without duplicating effort.
Cloned pages, copied modules, and one-off edits lead to mismatched updates and hard-to-maintain sites. Over time, this slows releases and increases the chance of errors.
HubSpot’s Design Manager solves this by letting you translate modules at the source. Instead of creating separate modules for every language, you localize content once and reuse the same structure everywhere. This keeps layouts consistent while allowing each language version to display the right text.
This guide explains how module translations work in HubSpot, how to set them up correctly, which mistakes cause issues later, and how to measure results once translations are live.
How HubSpot Handles Module-Level Translations
Creating translations for custom modules means localizing all user-facing text within a module so visitors see content in their selected language without manual duplication.
This includes headings, button labels, helper text, form placeholders, and instructional copy. Translations are managed inside the Design Manager, where developers attach language-specific JSON files to a single module.
Each JSON file contains translated values mapped to the module’s original field names. When the module loads on a translated page, HubSpot detects the page language and displays the matching text automatically. If no translation exists, HubSpot falls back to the default language.
This structure keeps design and logic centralized while allowing content to vary by language.
This approach is especially important for teams managing more than two languages. Without source-level translations, every new market increases content debt.
Changes to messaging, legal text, or CTAs must be manually repeated across duplicated modules, increasing the risk of inconsistencies and outdated copy appearing on live pages.
Translating modules at the Design Manager level removes that risk by centralizing all language variants in one controlled structure.
How Module Translations Work Internally
HubSpot uses JSON-based translation files to connect modules with supported languages.
- Module Fields: Editable fields define all text that appears on the page.
- Translation Files: JSON files replicate those fields and store translated values.
- Language Codes: Each file is mapped to a specific language, such as en, fr, or de.
- Rendering Logic: When a page loads, HubSpot selects the correct file based on the page language.
If a translation file is missing or incomplete, HubSpot displays the default language values. This prevents broken layouts while translations are still in progress.
Common Use Cases in HubSpot
Localized Landing Pages
Translated modules allow one landing page template to serve multiple regions. A single CTA module can display different headlines and button labels in different languages without duplicating templates.
Multilingual Headers and Footers
Navigation labels, footer links, and contact text appear across every page. Translating these through global modules avoids repetitive edits and maintains consistent navigation across languages.
Headers and footers often contain compliance-sensitive elements such as privacy links, cookie notices, or regional contact information.
Managing these through translated global modules ensures that legal and regulatory updates are reflected consistently across all language sites, reducing compliance risk and operational overhead.
Personalized Modules With Language Support
Modules that use personalization tokens or dynamic data still require localized labels. Translation files allow logic to remain intact while text changes based on language.
Common Setup Errors and Wrong Assumptions
Point: Missing translation files
Explanation: Pages revert to the default language, resulting in mixed-language experiences.
Point: Duplicating modules per language
Explanation: Updates require repeated edits and increase maintenance overhead.
Point: Hardcoded text in templates
Explanation: Text outside module fields cannot be translated using JSON files.
Point: Invalid JSON formatting
Explanation: Syntax errors prevent modules from loading correctly.
Another common mistake is assuming page-level language settings automatically apply to all embedded modules. In reality, modules must be explicitly translation-enabled in Design Manager.
Without this step, even correctly structured multilingual pages can surface untranslated module content, leading to fragmented user experiences.
Avoiding these issues early prevents rework later.
Step-by-Step Setup Guide
- Open Design Manager: Go to Marketing > Files and Templates > Design Tools.
- Select the module: Confirm all visible text exists as editable fields.
- Create JSON files: Add one file per language using the correct language codes.
- Add translations: Match field names exactly and insert translated values.
- Upload translations: Link each file under the module’s Translations tab.
- Publish the module: Make the module available across pages.
- Test pages: Preview each language version to confirm accuracy.
- Maintain updates: Sync translation files whenever fields change.
Optional best practice: maintain a changelog for translation updates. Each time a base module field changes, log which translation files were updated and when.
This lightweight documentation prevents missed updates in future iterations and helps new team members understand the localization workflow more quickly.
Measuring Results in HubSpot
Once translations are live, validate their impact using HubSpot reporting tools.
- Review traffic by language or domain
- Compare conversion rates across translated pages
- Check engagement metrics such as time on page and bounce rate
- Build reports segmented by language or region
Tracking these metrics confirms whether localized content supports engagement and conversions.
Short Practical Example
A SaaS company launches pricing pages for English-, Spanish-, and German-speaking audiences. Instead of rebuilding modules, the team adds es.json and de.json files to the pricing module. Each file contains translated labels for pricing fields.
When visitors access the site, the module automatically displays the correct language. Later pricing updates require edits in only one module and its translation files.
Six months later, when the pricing model changes, the team updates the calculator logic once and adjusts translated labels inside the same module files.
No rework, no duplicated QA cycles, and no missed translations. The system scales because it was designed for change from the beginning.
How INSIDEA Helps
INSIDEA supports teams building multilingual HubSpot sites that remain structured and easy to manage.
We help with:
- HubSpot onboarding and language setup
- Module translation planning and file structure
- Ongoing CMS cleanup and governance
- Reporting tied to language performance
If you want to scale globally without duplicating effort, hire our HubSpot experts.
Accurate module translations support consistent experiences across regions. When set up correctly, they reduce maintenance work and keep global sites aligned as content grows.
