A CMS migration for a multilingual website means moving every language version of a site into a new content management system. Plan for URL mapping, translation handling, language settings, and testing so visitors and editors get the same complete experience in each language. A content management system controls page creation, media storage, user roles, and publishing rules. Migration touches all of these, so a missing language setting can hide whole sections from readers.
Official resource:
- Tell Google about localized versions of your page — Verify hreflang, URL structure, and canonical requirements to preserve multilingual SEO during migration.
Table of Contents
- How will URLs and language structure carry over?
- What happens to translated content and workflows?
- How do menus, forms, and media stay consistent?
- What should you test before launch?
- How do you protect traffic and campaigns after go-live?
- Frequently Asked Questions
How will URLs and language structure carry over?
Decide whether each language will use a subfolder, subdomain, or separate domain. A subfolder setup looks like example.com/fr/ for French, while a subdomain looks like fr.example.com. Keep the same pattern after migration unless there is a strong reason to change it. Map every old address to its matching new address, language by language.
English pages should not point to French replacements, and vice versa. A spreadsheet of old and new pairs helps catch gaps before launch. Check language markers on each page, such as links that tell browsers which language version is which. Set a clear default language for visitors who arrive without a language preference. Confirm that switching languages keeps the reader on the same topic.
What happens to translated content and workflows?
Export source text and translations together, with status labels such as draft, in review, and published. Many teams lose work because draft translations are left behind or marked as published by accident. Confirm what each status means in the new system before import.
Plan for content that does not translate one-to-one. – Keep shared items, such as product codes and legal names, identical across languages Assign editors and translators to the right language areas in the new system. Test permissions with a sample article in each language. Fix access problems before bulk import begins.
- Keep layout differences, because German or Spanish text may need more space than English
- Keep approval steps separate, so each language team can review its own pages
How do menus, forms, and media stay consistent?
Rebuild navigation separately for each language rather than copying one menu everywhere. Labels, link order, and featured pages often differ by market. Broken menu links are a common sign that a language was only partly migrated. Check forms, search boxes, error messages, and checkout steps in every language.
A contact form may submit correctly in English but fail in another language if its fields or alerts were not moved. Submit a test entry for each version. Review images, videos, PDFs, and captions for language-specific files. A diagram with English text inside the image needs a separate localized file, not just a translated caption. Confirm file names and alt descriptions match the page language.
What should you test before launch?
Run a focused check on a staging copy that mirrors the live setup. Include editors, translators, and market managers who know each language well. Ask them to complete normal tasks, not just read pages.
Freeze content changes for a short window around launch when practical. Record which pages were translated last so newer edits can be reapplied after import. Keep backups of both databases and uploaded files until the new site runs steadily.
- Open top pages in each language on phone and desktop
- Switch languages from several entry pages and confirm the topic stays matched
- Submit forms, use site search, and follow checkout or signup paths
- Publish, edit, and unpublish a test page in each language
- Check dates, numbers, currencies, and address formats for local correctness
How do you protect traffic and campaigns after go-live?
Update paid campaigns, newsletters, and social profiles that link to old addresses. A migrated page can work correctly yet still lose visitors if ads point to retired URLs. Review destination links for each language market separately. Watch search referrals, direct visits, and conversion actions by language for several weeks.
A sharp drop in one language often points to a missing redirect map or a hidden section. Fix language-specific problems first, then recheck shared templates. Keep the old system readable to staff for a limited period. Use it to compare page counts, media files, and translation status when something looks incomplete. Remove access only after counts match and editors approve the result.
Frequently Asked Questions
Should untranslated pages show in the new system?
Hide them or show the source language with a clear notice, based on what each audience expects. Avoid mixing half-translated menus with finished pages.
How do we handle region-specific pages, such as offers for one country?
Migrate them only into the relevant language versions and keep their targeting rules. Do not copy regional offers into every language by default.
Who should approve each language before launch?
Ask a reader fluent in that language to approve pages, forms, and alerts. A central team can check layout, but only local reviewers catch wrong tone or terms.
