# How to Translate HubSpot CMS Pages, Emails and Forms | Vitra.ai > HubSpot's multi-language groups handle pages well. Emails, forms and smart content are separate systems, and that is where the gaps open as well. **Canonical URL**: https://www.vitra.ai/general/translate-hubspot-cms-pages **Source**: This is the Markdown rendering of https://www.vitra.ai/general/translate-hubspot-cms-pages, generated at build time from that page. --- 4 min read # How to Translate HubSpot CMS Pages, Emails and Forms HubSpot's multi-language groups handle pages well. Emails, forms and smart content are separate systems, and that is where the gaps open as well. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager , Vitra.ai Updated Aug 17, 2026 ![How to Translate HubSpot CMS Pages, Emails and Forms](https://www.vitra.ai/static/images/blog/translate-hubspot-cms-pages.jpg) Table of contents [Language groups do the page half well](#language-groups-do-the-page-half-well) [Everything that sits outside a language group](#everything-that-sits-outside-a-language-group) [Modules and theme fields](#modules-and-theme-fields) [The CRM side has language too](#the-crm-side-has-language-too) [Sequencing that works](#sequencing-that-works) [Measuring it](#measuring-it) [Workflows branch on language](#workflows-branch-on-language) [Reporting per language](#reporting-per-language) [Where to start](#where-to-start) [FAQ](#faq) Contributors [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Senior Product Manager Subscribe to our newsletter Subscribe > **Quick answer —** HubSpot has real multi-language support for pages through language groups, with a master and variants. What it does not automatically extend to is emails, forms, CTAs and smart content, each of which needs its own language handling. ## Language groups do the page half well HubSpot lets you attach language variants to a master page. The group shares analytics context, the language switcher is built in, and [hreflang](https://www.vitra.ai/general/multilingual-sitemaps) is emitted for you. For pages, that is a genuinely good system and better than most CMS equivalents. The trouble is that a HubSpot site is not only pages. ## Everything that sits outside a language group **Forms.** Field labels, help text, validation messages and the thank-you state. A translated landing page with an English form converts worse than an English page, because the mismatch reads as broken. **Emails.** Workflow emails, nurture sequences, transactional confirmations. These never touch the page, they are where the customer relationship actually happens, and they are almost always left in English. **CTAs.** Button text lives on the CTA object rather than the page. **Smart content.** Rules that swap a block by country or device. Each variant needs its own translation, and it is easy to translate the default and miss the rest. **Blog.** A separate content type with its own language handling. ## Modules and theme fields Custom modules define their own fields, and a field's default value is content that appears on the page. Theme-level settings — a footer tagline, a global banner — sit outside any single page and get missed by page-by-page work. ## The CRM side has language too Contact properties with picklist values, lifecycle stage labels, and anything surfaced back to a customer in a portal. This is not marketing content, so nobody in marketing owns it, which is exactly why it stays English. ## Sequencing that works Pages first because they are easiest, then forms because they sit on the pages you just translated, then emails because that is where the volume of customer contact really is. [translation memory](https://www.vitra.ai/features/translation-memory) makes the email step cheap, since nurture sequences reuse most of their language across steps. [quality control](https://www.vitra.ai/features/quality-control) matters on forms specifically, where a mistranslated validation message blocks a submission and nobody reports it. ## Measuring it HubSpot reports per page, so a language group gives you variant-level analytics without extra work. Compare form submission rates rather than page views — the page attracts, the form converts, and the form is the part that was probably still in English. Setup and supported object types are on the [HubSpot CMS integration](https://www.vitra.ai/integration/hubspot-cms) page. ## Workflows branch on language Once contacts exist in several languages, the workflows that email them need to branch. A single nurture sequence sending English to everybody undoes the translated landing page that acquired them. Set a language property on the contact at form submission and branch on it. That one property is what turns a translated page into a translated funnel, and it is usually the missing piece rather than the content itself. ## Reporting per language HubSpot will report per page, but attribution across a language group needs the property to be set consistently. Retrofitting it onto existing contacts is possible and messy, so do it before the first campaign rather than after. ## Where to start List every form on your translated pages and check them first. It is the shortest path from a translated site to a translated funnel. ## FAQ **Does HubSpot support multilingual pages?** Yes, through language groups that attach variants to a master page, with a built-in language switcher and hreflang emitted automatically. Pages are the part HubSpot handles well. **Are HubSpot forms translated with the page?** No. Forms are separate objects with their own labels, help text and validation messages. A translated landing page with an English form converts worse than an English page, because the mismatch reads as broken. **What about HubSpot emails?** They sit entirely outside language groups. Workflow emails, nurture sequences and transactional confirmations never touch the page, and they are where most customer contact actually happens. **What is smart content and why does it complicate translation?** Rules that swap a content block by country, device or list membership. Each variant needs translating separately, so it is easy to translate the default block and leave every alternative in English. Our blog ## Lastest blog posts Tool and strategies modern teams need to help their companies grow. Automotive [Automotive Brochure Localization by Market](https://www.vitra.ai/automotive/automotive-brochure-localization) A car brochure is a spec grid, a legal footer and a photo library, all market-specific. What actually has to change, and why the layout decides the schedule. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Automotive Campaign Localization Across Markets](https://www.vitra.ai/automotive/automotive-campaign-localization) Campaigns run through national companies and dealer networks, so one master becomes hundreds of files. Where the offer text and the disclaimers actually break. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 Automotive [Car Service Manual Translation for Technicians](https://www.vitra.ai/automotive/automotive-service-manual-translation) A workshop manual is read mid-repair by someone with the car on a lift. What that demands of procedures, torque figures and fault codes, in every language. [Samhitha J Bhatt](https://www.vitra.ai/author/samhitha) Aug 18, 2026 [View all posts](https://www.vitra.ai/blog/page/1) --- ## Structured data ```json { "@context": "https://schema.org", "@type": "Article", "mainEntityOfPage": { "@type": "WebPage", "@id": "https://www.vitra.ai/general/translate-hubspot-cms-pages" }, "headline": "How to Translate HubSpot CMS Pages, Emails and Forms", "image": [ { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/blog/translate-hubspot-cms-pages.jpg" } ], "datePublished": "2026-08-17T00:00:00.000Z", "dateModified": "2026-08-17T00:00:00.000Z", "author": [ { "@type": "Person", "name": "Samhitha J Bhatt" } ], "publisher": { "@type": "Organization", "name": "Vitra.ai", "logo": { "@type": "ImageObject", "url": "https://www.vitra.ai/static/images/vitra-v-logo.png" } }, "description": "HubSpot's multi-language groups handle pages well. Emails, forms and smart content are separate systems, and that is where the gaps open as well." } ``` ```json { "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://www.vitra.ai" }, { "@type": "ListItem", "position": 2, "name": "General", "item": "https://www.vitra.ai/general" }, { "@type": "ListItem", "position": 3, "name": "How to Translate HubSpot CMS Pages, Emails and Forms", "item": "https://www.vitra.ai/general/translate-hubspot-cms-pages" } ] } ``` ```json { "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ { "@type": "Question", "name": "Does HubSpot support multilingual pages?", "acceptedAnswer": { "@type": "Answer", "text": "Yes, through language groups that attach variants to a master page, with a built-in language switcher and hreflang emitted automatically. Pages are the part HubSpot handles well." } }, { "@type": "Question", "name": "Are HubSpot forms translated with the page?", "acceptedAnswer": { "@type": "Answer", "text": "No. Forms are separate objects with their own labels, help text and validation messages. A translated landing page with an English form converts worse than an English page, because the mismatch reads as broken." } }, { "@type": "Question", "name": "What about HubSpot emails?", "acceptedAnswer": { "@type": "Answer", "text": "They sit entirely outside language groups. Workflow emails, nurture sequences and transactional confirmations never touch the page, and they are where most customer contact actually happens." } }, { "@type": "Question", "name": "What is smart content and why does it complicate translation?", "acceptedAnswer": { "@type": "Answer", "text": "Rules that swap a content block by country, device or list membership. Each variant needs translating separately, so it is easy to translate the default block and leave every alternative in English." } } ] } ```