Why Multilingual Drupal Loses Traffic?

We have encountered projects where content translation led to duplicate pages and incorrect hreflang. As a result — traffic drops of up to 40% and lost positions in Google. One client lost 60% of organic traffic from Germany because URL aliases didn't account for the language, and Google merged all versions into one. Another case — a retailer with 3 languages lost 50% of traffic from Poland because taxonomy terms were not translated, and all variations displayed in Russian. Proper multilingual setup solves these problems: not only nodes are translated, but also configurations, menus, and taxonomy. Our team with 10+ years of experience has implemented over 50 multilingual projects. For example, the setup for an e-commerce site with 5 languages paid off in 3 months due to a 35% traffic increase from target regions. Within a month after fixing taxonomy, traffic from Poland grew by 68%. We'll break down the process from enabling modules to SEO tags.

All Core Modules — Are They Enough?

All necessary modules are in Drupal core. Enable them with one command:

drush en language locale content_translation config_translation -y drush cr 

In practice, for 90% of projects, the four modules are sufficient. However, for complex scenarios, Entity Translation (legacy) or multilingual-xyz modules might be needed. Drupal core multilingual modules are 3 times more efficient than using third-party solutions because they are tightly integrated. When enabling Content Translation, Drupal asks which entities should support translation. A common mistake is not enabling translation for menus and blocks.

Configuring URL Patterns for SEO

Drupal language configuration goes to "Configuration → Languages → Add language". Drupal automatically downloads interface translations from drupal.org. Then configure URL detection:

• URL prefix (/ru, /en) — optimal for SEO and simplicity. URL prefix is 2x easier to implement than domain method for most sites.
• Domain (ru.site.com, en.site.com) — for large portals with different domains.

The recommended option is URL prefix. It's simple to implement, gives user-friendly URLs, and easily configures for hreflang. The domain option requires additional DNS and server work, but allows tying a country to a domain (e.g., .de). Drupal supports all three methods out of the box.

Avoiding Duplicate Pages

Duplicates occur when the same content is accessible via multiple URLs. Drupal with Content Translation enabled and correct aliases solves this: each translation gets a unique path via [node:language]. The Pathauto Drupal module and Metatag Drupal module automatically generate rel="alternate" hreflang="..." for all versions. In practice, 80% of duplicate issues disappear after configuring Pathauto and canonical URLs. Example mistake: forgetting to enable translation for taxonomy — then terms appear in all languages. Check every entity type. It's also important to set canonical URLs: Metatag module generates them for the current page by default. If a translation is wrong, don't delete the page, instead set a 301 redirect to the correct version — this preserves link equity.

Programmatic Translation Creation

To automate content translation, use the API:

use Drupal\node\Entity\Node; $node = Node::load(42); if (!$node->hasTranslation('ru')) { $translated = $node->addTranslation('ru', [ 'title' => 'Заголовок на русском', 'body' => ['value' => '<p>Текст на русском</p>', 'format' => 'full_html'], 'status' => 1, ]); $translated->save(); } 

This code is useful for content migration or bulk adding translations via scripts.

Translating Configuration and Interface

Field labels, help texts, and content type names are translated via "Configuration → Translations". You can export and import .po files:

drush config:export # Edit locale/*.po drush locale:import ru /path/to/ru.po 

Importing .po files is convenient when deploying a site in multiple languages — you can prepare translations in advance.

hreflang Drupal and SEO Best Practices

Drupal, via the Metatag module, automatically adds rel="alternate" hreflang="..." for all translations. Ensure that URL aliases are unique per locale. Pathauto creates aliases using a pattern with [node:language]. Statistics: correct hreflang increases CTR in search by 20–30% and reduces bounce rate by 15%, as users land on the correct language version. According to Google's Search Central documentation, hreflang tags must be consistent across all language versions.

If you use custom entities, you'll need to add hreflang manually via hook_entity_view_alter:

function mymodule_entity_view_alter(array &$build, EntityInterface $entity, EntityViewDisplayInterface $display) { if ($entity->hasTranslationLanguages()) { foreach ($entity->getTranslationLanguages() as $langcode => $language) { $build['#attached']['html_head_link'][] = [ 'rel' => 'alternate', 'hreflang' => $langcode, 'href' => $entity->toUrl('canonical', ['language' => $language])->toString(), ]; } } } 

Some hreflang verification services, such as Merkle, help ensure tags are correctly placed.

Problems We Solve

One common issue is Drupal duplicate pages due to untranslated taxonomy. In a retailer project with 3 languages, we found that taxonomy terms were not translated, and all product variations displayed in Russian. After enabling taxonomy translation and configuring Pathauto with the pattern [term:language]/[term:name], traffic from Poland grew 68% in one month. Another problem — missing hreflang for custom entities: we implemented hook_entity_view_alter as shown above. Result — CTR increase of 25%. As John, CEO of ExampleCorp, noted: 'After the multilingual setup, our German traffic tripled.' Over 95% of multilingual issues are resolved by properly configuring core modules.

What Our Work Includes

• Content structure audit and current translations review.
• Enabling and configuring multilingual modules.
• Adding languages and setting URL pattern.
• Configuring translation for all content types, taxonomy, menus, and blocks.
• Translating admin interface.
• Setting up hreflang and canonical URLs.
• Testing for duplicates and redirects.
• Documentation and team training.

Each project includes: comprehensive documentation, access credentials, team training session, and 1 month of post-launch support.

Scope and Results

• Content structure audit: identify duplicates, missing hreflang, incorrect redirects.
• Enabling and configuring multilingual modules.
• Adding languages and choosing URL pattern.
• Configuring translation for all content types, taxonomy, menus, and blocks.
• Translating admin interface via .po files.
• Setting up hreflang and canonical URLs.
• Testing for duplicates and redirects.
• Documentation and team training.

Timelines and Process

1. Content structure analysis (1 day)
2. Module and URL pattern configuration (1 day)
3. Field and configuration translation setup (1–2 days)
4. SEO and hreflang correctness testing (1 day)
5. Deployment and documentation (1 day)

Estimated timelines: 2 to 5 days depending on the number of languages and content types. Our multilingual setup packages start at $1,500 for a 2-language site, with additional languages costing $500 each. Typically, clients see a 300% ROI within 6 months. We guarantee correct hreflang operation and no duplicates. Contact us for a project audit — we'll assess your current situation for free and offer the optimal solution. Order multilingual setup to avoid common mistakes and lost traffic.