Multilingual Drupal website — how it works
A multilingual website is not simply translated content. It is a separate content strategy, a separate URL structure, separate SEO logic and a separate editorial workflow. Drupal supports all of these at once.
Many organisations start with a single-language site and add languages later. Drupal is well designed for this — multilingual support is built in, not added as an afterthought. But the fact that the platform supports multilingualism does not mean it is simple — it means it can be done properly.
Four layers of multilingualism in Drupal
Drupal distinguishes four layers that can be translated:
1. Content translation Each content item — a page, news article, product — can have different text in different languages. Different language versions of the same item are linked: when one changes, the administrator is notified that the translation is out of date.
2. Interface translation Buttons, error messages, system notifications — everything Drupal itself displays can be translated. The Drupal.org community maintains translations for many languages.
3. Configuration translation View titles, form field labels, menus, site settings — these are separate translation objects. They are often overlooked in briefs but matter for user experience.
4. URL structure Each language version has its own URL — for example /et/services and /en/services. URLs can be configured to derive language-specific slugs automatically from content.
What this means for SEO
A multilingual site requires correct hreflang tags: each page must reference its counterpart in the other language. Without hreflang, search engines do not know which language version is which and may treat language variants as duplicate content.
Drupal generates hreflang tags automatically when multilingual support is correctly configured. But this requires that translation links are created — content that has not been translated cannot receive references.
Editorial workflow
A multilingual site is more complex to manage than a single-language one. Some practical questions to resolve before starting a project:
- Who is responsible for translation — the editor or a separate translator?
- Is all content translated into every language?
- When content in the source language changes, is the translated version marked as out of date?
- Does any language have different content rather than a translation (separate version for a different market)?
These questions affect content models and configuration — they are much easier to resolve in the planning phase than to fix later.
When Drupal is the strongest choice
Drupal is the strongest platform for multilingualism when:
- there are more than two languages;
- content is not simply translated but language-specific (different content for different markets);
- separate editorial workflows exist for different languages;
- there are strong SEO requirements for multilingual search.
If the site has only two languages and the content is a complete translation with no variations, simpler solutions may work. But as requirements grow, Drupal is architecturally the most prepared platform.
Get in touch if you are planning a multilingual Drupal project — describe the situation and we can outline what decisions need to be made upfront.
Kaido Toomingas
WebPro Company OÜ
Need Drupal help?
If the article describes your situation, you do not have to read everything first. A real person will help you choose the next step.