Creating multilingual content in HubSpot goes beyond translating your pages. To keep the entire journey in the same language, you need to connect six key elements correctly: the blog post, CTA, landing page, form, thank-you page, follow-up email, and downloadable asset.
A visitor from Germany finds your German blog post, likes it, and clicks the CTA. The landing page loads in English. She fills in the form anyway, gets a thank-you page in English, then an email in English with an English PDF attached.
Every single asset in that journey may have been translated. The experience still breaks because the assets were never connected to each other in the same language.
That gap is one of the most common problems in multilingual HubSpot portals, and it has nothing to do with translation quality.
Table of content:
HubSpot lets you create and manage language variations for core content such as website pages, landing pages, blog posts, and knowledge base articles. See here which languages are available.
This makes the core content relatively easy to manage. Different language versions can be associated with the same primary content, helping you keep your multilingual website organized.
But creating the translated pages is only one part of the setup.
A complete multilingual journey also depends on two other layers:
This second layer is where multilingual HubSpot setups often break.
A multilingual HubSpot journey requires six key handoffs: blog post to CTA, CTA to landing page, landing page to form, form to thank-you page, thank-you page or form submission to follow-up email, and follow-up email to the final asset.
Your translated blog post needs to display the CTA created for that language.
Translating a blog post doesn't necessarily replace the supporting CTA with its translated equivalent. Check each language version and make sure visitors are being shown the correct CTA.
Each translated CTA should direct visitors to the landing page in the same language.
A German CTA that sends visitors to an English landing page immediately breaks the multilingual experience, unless HubSpot catches it for you. If a visitor is already on a translated (German, for example) page and clicks a link pointing to another page's English version, HubSpot's language-specific redirects can send them straight to the German version instead (if there is one), without you ever having to update the CTA's link.
Language-specific redirects
Where to find it: Settings → Content → Domains & URLs → Language Settings.
Your translated landing page should contain a form that matches the language of the page.
Don't only check the visible form title. Review field labels, consent text, dropdowns, radio buttons, and other options that visitors interact with.
After submitting a form, visitors should continue to a thank-you page in the same language.
The language journey shouldn't end at the form submission. Check the redirect or thank-you experience for every language.
The form submission should trigger the correct follow-up email for that visitor's language.
If someone downloads a German resource through a German landing page, the follow-up communication should also be in German.
Every link inside the follow-up email should point to the correct language version of the downloadable asset.
This includes PDFs, eBooks, whitepapers, checklists, case studies, and any other resources included in the campaign.
Six handoffs, each relatively simple to configure. But miss one and the visitor notices immediately because the language changes halfway through the journey.
Want the full step-by-step setup? Download the guide and get the 1-page multilingual launch checklist
The most common multilingual HubSpot mistakes happen outside the main page translation, including incorrect blog settings, untranslated form options, incorrect metadata, and unreviewed AI translations.
Here are some of the issues worth checking:
The correct language needs to be configured for your HubSpot blog before you can properly manage content for that language.
Before planning translated blog content, check your blog settings and make sure the required languages are available and correctly configured.
Otherwise, you can finish translating your content only to discover that the publishing setup isn't ready for it.
Translating form labels isn't enough if dropdown values, property options, consent text, or other selectable fields remain in the original language.
Go through the form as if you were the visitor. Every element they can read or select should make sense in that language.
Authors, tags, categories, and other blog information should also be reviewed for each language version.
The main content may be German while smaller elements around it remain in English, creating an inconsistent experience.
AI translation can speed up multilingual content creation, but the final version should still be reviewed before publication.
Product names, technical terminology, CTAs, tone of voice, and marketing expressions don't always translate naturally.
A translation can be technically correct and still not sound like something your company would actually say.
Using separate workflows for each language can make multilingual campaigns easier to organize, test, and troubleshoot.
Instead of putting every language into one large workflow, you can keep the relevant language-specific elements together.
For example, a German workflow could contain the German form submission criteria, follow-up email, language-specific actions, and links to the relevant assets.
The Portuguese version follows the same structure with the Portuguese assets.
This makes it much easier to understand what should happen after a visitor converts and to identify where something has gone wrong.
A clear naming convention also helps. For example:
DE | eBook | Follow-up
EN | eBook | Follow-up
PT | eBook | Follow-up
As you add more languages, this structure becomes increasingly important.
The best way to test multilingual content is to complete the entire conversion journey yourself in each language, from the first page to the final downloadable asset.
Don't only preview the translated pages individually.
Open the translated blog post and follow the exact same path as a visitor:
Blog post → CTA → landing page → form → thank-you page → follow-up email → asset
Click the CTA. Submit the form. Read the thank-you page. Wait for the email. Click the links. Download the resource.
Then repeat the process for every language you're launching.
The language should remain consistent from beginning to end. Language-specific redirects reduce this risk, but they only work where a translated destination already exists — so this end-to-end test is still the only way to confirm nothing falls back to the original language.
Many broken multilingual journeys can be caught with this simple end-to-end test before visitors ever see them.
Follow the steps in our quick checklist included in the eBook: