How do I manage domains for multilingual sites on HubSpot?

Last updated: August 11, 2016

Available For:

Product: HubSpot Marketing
Subscription: Basic, Professional, & Enterprise

When creating websites in multiple languages, there are several options for how you to set up the URL structure of your site hosted on HubSpot. Below is a description of some of the methods that you can use to manage multilingual sites on HubSpot.

When choosing how you want to structure a multilingual site, you will want to take into consideration which method is most manageable for your team, as well as the SEO implications


One approach to hosting multilingual content is to create your translated pages with language code subdirectories. You can manage the URL of a page from the Settings tab of within the page editor. In the screenshot below, the subdirectory "es" has been added for the Spanish version of the page.

subdirectory-settings-tab.pngFor HubSpot blogs, you can create language specific blogs and specify a permanent subdirectory for a particular blog from Content > Content Settings > Blog, under the Blog Root URL option. In the screenshot below, the blog's url is set to have the subdomain "es", which means all posts will be created on URL paths relative to this listing domain.

blog-root-url-subdirectory.pngYou can set up as many subdirectories as you need on HubSpot, regardless of your account subscription level.


With an Enterprise HubSpot account, you can use an unlimited number of domains within each tool of HubSpot. You could connect language-specific subdomains, as shown in the example below, and use them interchangably depending on the language of each page. To host multiple language domains, you will need to purchase each domain with a registrar and point the DNS to HubSpot. Once connected, you can publish content on the domain of your choice from the Settings tab in the editor.


Smart content by language and Javascript translation

The previous two methods allow you to create distinct pages for each language and have your team write the in-language content or use an integration to translate it. You may choose to use a single page instead, while relying on smart content or Javascript to handle the translation.

Smart content can be used dynamically to swap out areas of the page for alternate versions, based on the visitor's preferred language. To learn more about smart content based on language, check out this article.

One final alternative is to host a single version of the page and use a Javascript solution, such as Localize, to translate the content on that page based on the visitor's preferred browser.

Was this article helpful?