There are plenty of modules <\/strong>to help you build the functionality you want, so all that’s left is for you to produce the right content.<\/p>\n\n\n\n The thing is, if you want your audience to span borders, you must ensure everyone understands what is written on your site.<\/p>\n\n\n\n This means translating the website and enabling support for multiple languages<\/strong>. With most CMS solutions, this means installing a range of third-party plugins and spending hours configuring them. However, because you use Drupal, the process can be much simpler. Today, we’ll walk you through it.<\/p>\n\n\n\n Some of you are probably wondering whether going through the effort of translating a website into multiple different languages is really worth it. And indeed, you can just about see a couple of arguments against it.<\/p>\n\n\n\n Recent studies suggest that almost a fifth of the world’s population speaks English<\/strong> now, so we’re closer than ever to having something that resembles a universal language. For users who don’t understand it, there are automated translation tools<\/strong> that are getting better and better at accurately transmitting information in pretty much any language you can think of.<\/p>\n\n\n\n Vendors now integrate these tools directly into their browsers, so users no longer need to copy-paste large blocks of text and open new windows. In light of this, introducing multiple languages to your website may seem like a bit of a pointless exercise.<\/p>\n\n\n\n Often, however, doing it is well worth it.<\/p>\n\n\n\n While many people speak and read English, you can’t merely discount the users who don’t, at least not if you want them to engage with your site. Automatic translators are indeed available, but relying on them is not a good idea for two main reasons.<\/p>\n\n\n\n First, they’re still not perfect. Although they’ve come a long way, a machine will never be able to accurately translate all the semantic nuances that a text inevitably carries. Second, although auto translators are now integrated into most popular browsers, they still require a couple of additional clicks. <\/p>\n\n\n\n So, the case for leaving your Drupal site in English only is already weaker, and when you consider the benefits of integrating multilingual functionality, you’ll see the scales tipping in the other direction. Let’s look at some of the main advantages.<\/p>\n\n\n\n Even if a person speaks English, allowing them to view your site in their native language will make it easier and more pleasant to use. This is critical if you want them to interact with your business.<\/p>\n\n\n\n Translating the website into another language means you care about the people who speak it. It shows that you’re determined to enter that particular geographical region and you’re serious about doing business with it. This is bound to be noticed by the site’s visitors.<\/p>\n\n\n\n If you introduce multilingual functionality on your website before your competitors, the improved user experience gives you a definitive advantage. You can be the first to conquer new markets and ensure users choose your products and services.<\/p>\n\n\n\n The more languages you support, the more keywords you can target and the more search engine results pages you can appear on. This could have a tremendous effect on the volumes of organic traffic you attract.<\/p>\n\n\n\n So, without further ado, let’s see how you turn a regular Drupal website into a global online portal translated into multiple languages.<\/p>\n\n\n\n Up until a few years ago, multilingual integration on a Drupal site was only possible through so-called contributed modules<\/strong> – add-ons you download and install after you’ve set up the CMS. However, with Drupal 8<\/strong>, the modules were integrated into the core.<\/p>\n\n\n\n So unlike WordPress and Joomla, where you have to find and set up third-party extensions, the functionality here is available out of the box. You just need to enable it.<\/p>\n\n\n\n To do that, log in to your Drupal site with your administrator account and go to the Extend<\/strong> section of Drupal’s backend. Scroll down to the Multilingual <\/strong>section, where you’ll find four modules: Configuration Translation<\/strong>, Content Translation<\/strong>, Interface Translation<\/strong>, and Language<\/strong>.<\/p>\n\n\n\n Select the checkboxes next to them, then scroll down to the bottom of the page and click Install<\/strong>.<\/p>\n\n\n\n Next, it’s time to add a new language. Go to the Configuration<\/strong> page in the Drupal administration panel and locate the Regional and Language <\/strong>section.<\/p>\n\n\n\n Click Languages<\/strong>. You’ll see a list of the languages currently available on your site. In your case, it should contain English only. Above it is the Add Language<\/strong> button. Click on it.<\/p>\n\n\n\n Select your preferred language from the drop-down menu and click Add language<\/strong>. Drupal automatically downloads and imports everything it needs. The drop-down menu has over 100 languages, so in all likelihood, you’ll find what you’re looking for. If you don’t, a Custom language<\/strong> option is available at the very bottom of the list.<\/p>\n\n\n\n When done, you will be taken back to the list of installed languages. You can use the crosshairs to modify the order in which languages appear in the languages switcher block. From this page, you can also change the default language of your Drupal website. However, doing that is highly unadvisable if you don’t have previous experience,<\/strong> as it is possible to cause the entire site to break.<\/p>\n\n\n\n Next, it’s time to add a language switcher block<\/strong> to the website’s front end. Go to the Structure<\/strong> section of the administration panel and click Block<\/strong> Layout<\/strong>. At the top of the page, you’ll see the Drupal themes installed on your site. Make sure the one you’re currently using is selected. <\/p>\n\n\n\n Further down, you can see all the regions where you can place the language switcher block. Your choice depends on your personal preferences and the theme. More often than not, the switcher is located either in the sidebar or in the header. Pick the location and click the Place Block<\/strong> button.<\/p>\n\n\n\n From the list, you need to find the Language Switcher <\/strong>entry and click the Place Block<\/strong> button next to it.<\/p>\n\n\n\n The popup that appears gives you a few options for deciding how the switcher block behaves. If you want the added languages to be available on all pages, you can leave the settings in their default state.<\/p>\n\n\n\n The Content Translation<\/strong> core module we enabled in the previous section lets you decide which parts of your website will be translatable. Open the Configuration<\/strong> page in Drupal’s administration panel, and under Regional and Language<\/strong>, click Content Language and Translation<\/strong>.<\/p>\n\n\n\n You’ll see a list of all the entity types. By default, only the checkbox next to URL aliases <\/strong>is selected. Using the other checkboxes, you can make other entity types translatable.<\/p>\n\n\n\n The ones you’re most likely interested in are Content<\/strong>, Content Block<\/strong>, and Custom Menu Link<\/strong>.<\/p>\n\n\n\n Every checkbox you create opens a new set of configuration options under the list of entity types. Through these options, you can choose which subtypes and fields will be translatable<\/strong>.<\/p>\n\n\n\n For example, after you select the Content<\/strong> checkbox, you’ll probably see checkboxes for translating articles and basic pages (the exact subtypes depend on your theme and modules). When you select a subtype, you can configure which fields will be translatable.<\/p>\n\n\n\n Pretty much any field can be translatable, but in all likelihood, you don’t need all checkboxes to be selected. <\/p>\n\n\n\n For example, if you’re configuring article translations, you need to make sure the title <\/strong>and the body <\/strong>are translatable. Your URL aliases<\/strong> and tags <\/strong>should also be available in the target language for SEO purposes. However, you most likely don’t need to translate the author’s name or the date the article was published, so you can leave those checkboxes empty. Make sure you select the Show Language Selector on Create and Edit Pages <\/strong>for each entity subtype you want to translate. This makes translation management easier.<\/p>\n\n\n\n When you’re done, click Save Configuration<\/strong> to apply the changes. After that, when a user with content translation privileges views the entries in the Content <\/strong>section of your Drupal dashboard, they’ll have the Translate<\/strong> option under the Operations<\/strong> drop-down menu next to existing articles and pages.<\/p>\n\n\n\n When new content is added, a Language <\/strong>drop-down menu lets the author choose the language of the latest article or page.<\/p>\n\n\n\n Translating the articles and pages won’t help much if the menus, buttons, and fields users interact with are in a language they don’t understand. That’s why, when we activated Drupal’s multilingual core modules, we also selected the checkbox next to Interface Translation<\/strong>.<\/p>\n\n\n\n With it, you can translate everything users see on the front end, as well as all the tools and features in Drupal’s administration panel. Most of the work is done automatically when you add a language through Configuration <\/strong>> Languages <\/strong>> Add language<\/strong>.<\/p>\n\n\n\n Remember the long list under the drop-down menu? <\/p>\n\n\n\n For every entry, a translation is created and maintained by the Drupal community<\/strong>. On the list of installed languages, you can see how much of your website is covered by that translation.<\/p>\n\n\n\n As you can see from the screenshot below, for example, the German translation is more complete than the Italian one.<\/p>\n\n\n\n The percentage figures you see on this page depend not only on the volume of time translators have spent working on the CMS but also on the modules you’ve installed. The more add-ons you have, the more elements you have to translate.<\/p>\n\n\n\n If you click on the percentages in the Interface Translation <\/strong>column, you can complete or modify the installed translations. <\/p>\n\n\n\n In basic terms, the translation is a large list of entries, each representing a string of text either on the front end or in Drupal’s administration panel. You can filter untranslated strings and complete them straight from the User Interface Translation <\/strong>page.<\/p>\n\n\n\n Alternatively, you can click the Export<\/strong> tab and download the translation as a .po file<\/strong>. Plenty of free editors can help you translate the unfinished strings on your computer. When ready, you can upload the completed .po file and apply the chances through the Import <\/strong>tab.<\/p>\n\n\n\n If your site works in multiple languages, you’ll likely have several people accessing Drupal’s Administration Panel to add or edit translations. To make things easier for them, it’s best to ensure everyone sees the administration pages in their native language.<\/p>\n\n\n\n To do that, go to the People<\/strong> section of the admin panel and click the Edit<\/strong> button next to the user account you want to change. Scroll down to the Language Settings<\/strong> section and pick the required language from the Administration Pages Language<\/strong> drop-down menu.<\/p>\n\n\n\n After you save the changes, the Drupal dashboard will be displayed in the language chosen by this particular account owner.<\/p>\n\n\n\n For regular site visitors, it’s best to use the language detection functionality built into the multilingual core modules. To configure the feature, go back to the Configuration<\/strong> page and click Languages<\/strong> under the Regional and Language <\/strong>section.<\/p>\n\n\n\n Open the Detection and Selection<\/strong> tab to see all available options.<\/p>\n\n\n\n Because you’ve already configured the accounts with access to the admin panel, the Account Administration Pages<\/strong> detection method is enabled. So is the URL <\/strong>method, i.e., Drupal knows what language to display thanks to the URL loaded in the user’s browser.<\/p>\n\n\n\n If you click the Configure <\/strong>button, you can see and change how Drupal forms these URL addresses. By default, the CMS adds a path prefix to the URL to define the language. For example, German content is available under domain.com\/de<\/em>, Italian translations are under domain.com\/it<\/em>, etc.<\/p>\n\n\n\n If you click the Domain <\/strong>radio button at the top, you can also configure Drupal to use subdomains for different languages (i.e., de.domain.com <\/em>for German, it.domain.com <\/em>for Italian, etc.). Still, you need to make sure the subdomains are set up and pointing correctly.<\/p>\n\n\n\n IMPORTANT:<\/strong> You shouldn’t forget that any changes you make to these particular settings could break existing URLs. If you have already uploaded some translated content, it’s best to keep URLs as they are. Even if you haven’t, be extremely careful when making changes to your live website.<\/p>\n\n\n\n The next option on the Detection and Selection<\/strong> page is labeled Session<\/strong>. If enabled, Drupal can be configured to deliver translations based on a specific parameter in the user’s request. For example, if the request is for domain.com\/language=de<\/em>, Drupal serves German translation; if it’s for domain.com\/language=it<\/em>, it delivers content in Italian, etc.<\/p>\n\n\n\n The third option on the detection methods list is labeled User<\/strong>, and it’s down to the user’s personal preference according to their account settings.<\/p>\n\n\n\n If you enable the Browser detection method<\/strong>, Drupal will determine which translation to serve based on the user’s browser UI language. The problem with this method is that browsers work differently, and their encoding isn’t always the same. For the most popular languages, you should see no problems, but if you’re not happy with the way the feature works, you can click the Configure <\/strong>button and assign specific codes to languages.<\/p>\n\n\n\n The last detection method is called Selected Language<\/strong>. It’s always enabled, and it’s the fallback option that delivers the Drupal website in a language of your choice in case all other enabled methods don’t work. This is effectively a workaround to the problems you will inevitably encounter if you try to change the default language of your live site.<\/p>\n\n\n\n By default, the Selected Language<\/strong> option reverts everything back to English, but if you wish, you can change it to another language without breaking the entire website.<\/p>\n\n\n\n Going back to the Detection and Selection<\/strong> page, you’ll see that the detection methods are arranged in a specific order, which determines their priority. Drupal will first use the topmost enabled detection method when deciding which translation to serve and will only move to the second one if the first is unsuccessful.<\/p>\n\n\n\n You can rearrange the methods using the crosshairs on the left and determine which one has the most weight.<\/p>\n\n\n\n When you’re done, click Save settings<\/strong> and perform a few tests to make sure everything works.<\/p>\n\n\n\n Unlike many other website-building applications, Drupal’s multilingual features are available out of the box, so it’s much easier to start building your international online business. However, all your efforts will be in vain if you don’t deploy your website on a <\/strong>reliable drupal hosting platform<\/strong><\/a>. This is where ScalaHosting comes in.<\/p>\n\n\n\n A multilingual Drupal site isn\u2019t just about translations \u2014 it\u2019s about delivering them instantly to audiences across continents. ScalaHosting\u2019s global data centers, integrated Cloudflare CDN, and high-availability VPS clusters ensure that visitors in Berlin, S\u00e3o Paulo, or Tokyo see your site load as quickly as those in New York. Combined with multi-domain hosting and daily offsite backups, you can manage localized sites for each region with the same speed and security.<\/p>\n\n\n\n The service is built on state-of-the-art hardware<\/strong>, giving you impeccable uptime stats. All but our cheapest plans support multiple domains hosted under the same account<\/strong>, so you can create your regional domains and further increase visibility. In the meantime, the daily offsite backups<\/a> and our unique anti-malware system give you some much-needed peace of mind.<\/p>\n\n\n\n All Drupal hosting packages include a control panel. Depending on the service type, you’ll work with either cPanel <\/strong>or SPanel <\/strong>– our proprietary server management platform. In both cases, you have easy Cloudflare integration, meaning you can easily use one of the world’s biggest Content Delivery Networks (CDN)<\/a> to ensure page load times are consistent regardless of the visitor’s location.<\/p>\n\n\n\nTurning a Website Into a Global Business Venture: Why Integrating Multilingual Functionality is Important<\/h2>\n\n\n\n
![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/Drupal-Hosting-for-International-Websites-Turning-a-Website-1140x513-1.webp\")
<\/figure>\n\n\n\n
\n
\n
\n
Enabling Multilingual Modules in Drupal and Adding a Language<\/h2>\n\n\n\n
![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/drupal-multilingual-modules.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/regional-and-language-1140x446.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/languages-1140x328.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/add-language-1140x251.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/language-list-1140x431.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/block-layout-theme.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/language-switcher-place-block.webp\")
<\/figure>\n\n\n\nTranslating Content<\/h2>\n\n\n\n
![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/content-types-1140x308.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/content-subtypes-1140x912.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/translate-article-1140x436.webp\")
<\/figure>\n\n\n\nUser Interface Translation<\/h2>\n\n\n\n
![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/german-vs-italian-1-1140x445.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/user-interface-translation-1140x559.webp\")
<\/figure>\n\n\n\nLanguage Detection and Settings for Front End and Administration Pages in Drupal<\/h2>\n\n\n\n
![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/adminisrtation-pages-language.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/detection-and-selection-1140x455.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/url-prefixes-1140x330.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/session-language-detection-1140x264.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/selected-language-1140x229.webp\")
<\/figure>\n\n\n\n![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/language-detection-order-1140x320.webp\")
<\/figure>\n\n\n\nScalaHosting and Multilingual Drupal Websites<\/h2>\n\n\n\n
![\"Drupal](\"https:\/\/www.scalahosting.com\/blog\/wp-content\/uploads\/2025\/09\/Drupal-Hosting-for-International-Websites-Scalahosting-1140x513-1.webp\")
<\/figure>\n\n\n\n