Drupal translation is the process of making your Drupal site work well in more than one language. In modern Drupal, that means translating content, interface text, and site configuration, and choosing how the site detects each visitor’s language. Drupal ships with strong multilingual features in core, and Drupal.org says more than 100 languages are immediately available.
If you want a multilingual Drupal site that feels local to every user, you need more than a language switcher. You need the right modules, a clear workflow, and multilingual SEO.
This guide is written for Drupal 10 and 11 and shows the simplest way to get there.
What Drupal translation actually includes
In Drupal, translation is not one single task. It usually breaks into three main jobs:
- Content translation for pages, articles, blocks, taxonomy terms, and other content entities
- Interface translation for buttons, forms, menus, labels, and system text
- Configuration translation for Views, menus, blocks, vocabularies, the site name, and other settings
Drupal handles this with four core multilingual modules: Language, Content translation, interface translation, and configuration translation
Why Drupal is a strong choice for multilingual websites
Drupal is still one of the best CMS options for multilingual sites because its language features are built into core, not bolted on later. It supports field-level translation, lets you choose which parts of a content type should be translated, and can detect language by URL, domain, session, browser, user preference, or a default site language.
Drupal.org also notes that you do not need a splash page just to ask users which language they want. That matters for both users and editors. Visitors get the right language faster. Editors get a cleaner system to manage.
1. Language
The language module lets you add languages, set a default language, and decide how Drupal should choose a language for each page. It is the base layer for everything else.
2. Content translation
The content translation module lets you translate content entities such as pages, comments, custom blocks, taxonomy terms, users, and more. It also lets you choose which fields are translatable and which fields stay shared across all language versions.
3. Interface translation
The interface translation module translates the built-in Drupal interface and other interface text from modules and themes. In older Drupal versions this was called Locale, which is one reason older tutorials can be confusing.
4. Configuration translation
The configuration translation module translates settings stored in Drupal’s configuration system. That includes Views, menus, blocks, vocabularies, contact categories, and even your site name
How to set up Drupal translation step by step
1. Add the languages you need
Go to Configuration > Regional and language > Languages and add the languages your site needs. Current Drupal multilingual guidance starts with the four core modules and then adding at least two languages.
A practical tip: start with your main language and one secondary language first. Get the workflow right before you add more markets.
2. Enable the four core multilingual modules
Turn on:
- Language
- Content Translation
- Interface Translation
- Configuration Translation
These are the foundation of modern Drupal multilingual builds.
3. Choose what is translatable
Next, decide which content types and fields should be translated. Usually that means titles, body copy, summaries, meta fields, alt text, and CTA copy. Drupal lets you make that choice field by field.
4. Set your language detection rules
Drupal can choose a language in several ways, including URL, domain, session, user preference, browser language, and the default site language.
For most SEO-focused sites, URL-based language handling is the safest place to start because it gives each language a clear, crawlable address
5. Translate content
Once a content type is marked as translatable, editors can create a language version of each page. Drupal’s content translation flow keeps translations connected, instead of creating totally separate pages with no relationship.
6. Translate interface text and configuration
Do not stop at page copy. Translate your menus, form labels, Views text, blocks, system messages, and site settings too. This is where many multilingual sites feel unfinished.
Drupal’s Interface Translation and Configuration Translation modules exist to cover those gaps.
7. Add a language switcher and test the whole journey
Make it easy for users to switch languages. Then test the full journey: menu, page, form, search, breadcrumb, and confirmation messages. A multilingual site only feels complete when the small details are translated too.
Competitor content often explains setup, but fewer pages go deep enough on testing and consistency.
When Drupal core is enough and when you need extra tools
For many small and mid-sized sites, Drupal core is enough. But when you have a large content library, outside translators, or tighter approval flows, add a translation management layer.
Use core only if:- You have a small site.
- Your editors manage translations in-house.
- You only support a few languages.
Add TMGMT if:
- You need translation jobs and status tracking.
- You work with human translators or external services.
- You want a formal workflow.
The Translation Management Tool (TMGMT) module is built for that. Drupal.org describes it as a tool set for translating content from different sources, with support for people, translation services, and automated workflow scenarios.
Add Lingotek or another connector if:- You want a direct translation service integration.
- You need enterprise localization workflows.
- You want content sent out and returned inside Drupal.
The Lingotek module offers direct integration between Drupal and Lingotek’s translation management system.
Add AI-assisted translation carefully if:
- You need speed on large volumes
- You still have a human review before publishing
There are newer options too.
For example, AI TMGMT is a translator plugin for TMGMT that works with AI providers such as OpenAI and Ollama. That is useful for drafts and scale, but important pages still deserve review before they go live.
Drupal translation SEO best practices
SEO, even in the AI era, is an area often overlooked. But if you want to rank, a multilingual setup and multilingual SEO need to work together.
Give each language its own URL
Google recommends using different URLs for different language versions instead of changing the language with cookies or browser settings alone. That makes each version easier to crawl and easier to rank. Good examples include:
- /en/
- /fr/
- /de/
Or language-specific domains or subdomains when that fits the business.
Use hreflang
If you use different URLs for different languages or regions, add hreflang so Google can send users to the right version. Google supports three methods:
- HTML tags
- HTTP headers
- Or XML sitemaps.
The methods are equivalent, and Google says there is no benefit to implementing all three at once. Pick one and manage it well.
Translate the parts users and Google see first
Your translated page needs more than translated body text. Also translate:
- Title tag
- H1
- Meta description
- Menu label
- Image alt text
- CTA buttons
- Internal anchor text
Google says title links are important for clicks and recommends descriptive, concise title text. Google also says it may use a meta description when that better describes the page, and unique descriptions work better than copying the same text across many pages.
Do keyword research in each language
Do not translate keywords word-for-word. Search behavior changes by market. A term that sounds right in English may not be the term people actually search for in French, German, or Spanish.
Translate the main content, not just the template
Google says localized pages are only treated as duplicates when the main content stays untranslated. If you only translate the navigation and footer, you are not really giving search engines a new language page to rank.
Avoid relying on locale-adaptive pages alone
If your site changes language automatically based on the user’s browser or location, Google may not crawl every variation. Google notes that Googlebot usually crawls from the US and typically does not send an Accept-Language header.
Common Drupal translation mistakes
1. Using old Drupal 7 advice on a modern Drupal site
This is a big one. The internationalization (i18n) project page is centered on Drupal 7-era upgrades and add-ons, and Drupal 7 reached end of life on January 5, 2025.
Drupal.org says Drupal 7 is no longer community-supported. For Drupal 10 and 11, start with core multilingual modules first, not legacy i18n tutorials.
2. Translating pages but not the system around them
A half-translated site feels broken. If the article is in Spanish but the form errors, menu items, or filter labels are still in English, trust drops fast. Drupal separates content, interface, and configuration for a reason. You need all three.
3. Publishing machine translation with no review
Machine translation can speed up first drafts. It should not be the final step for important pages. A simple review workflow catches tone issues, bad product names, and broken legal or brand language. That workflow piece is one of the strongest angles in the better competing content.
4. Forgetting multilingual SEO
Many Drupal translation posts explain modules but barely cover crawlability, URLs, hreflang, or metadata.
That leaves rankings on the table. Google’s multilingual guidance is clear here: use different URLs, add hreflang, and make each language version easy to discover.
Do you still need the i18n module?
Usually, no.
If you are running a modern Drupal 10 or 11 site, the starting point is Drupal core’s multilingual system.
The old i18n project matters mostly for legacy Drupal 7 setups, and Drupal 7 is end-of-life. Only keep i18n in the conversation if you are dealing with a legacy site that has not yet migrated.
The best Drupal translation setup for most teams
Use this simple rule of thumb:
- Small site, few languages: Drupal core
- Growing site with editor review: Drupal core + TMGMT
- Enterprise localization workflow: Drupal core + TMGMT or Lingotek
- Large-volume first drafts: AI-assisted translation + human QA
That keeps the stack simple while giving you room to scale.
Key takeaways
Drupal translation works best when you treat it as a system, not a switch.
- Start with the core multilingual modules.
- Give each language a clear URL.
- Add a translation workflow that your team can keep up with.
- Then make sure the translated pages are fully localized for users and for search.
That is how you build a Drupal site that is easier to manage, easier to scale, and far more likely to compete.
Drupal translation FAQ
Yes. Drupal has multilingual features in core, supports more than 100 languages, and gives you separate tools for content, interface, and configuration translation.
For most modern sites, the best starting point is not one module but the four core multilingual modules. If you need workflow or vendor integration, add TMGMT or Lingotek on top.
Yes, with connectors and add-ons. TMGMT supports different translation services, Lingotek adds a direct TMS integration, and AI TMGMT adds AI-driven translation options. Auto-translation can save time, but review is still wise for important pages.
It can, if each language has its own URL, hreflang is set correctly, and the translated page has real localized content, titles, and metadata. Translation alone is not enough; the SEO setup has to be right too.
