In-depth practical guides

Prepare a multilingual website migration

Map destinations by language, preserve journeys and test routes: prepare URL changes without losing useful content.

Updated :

Multilingual editorial work with proofs and compared page layouts.

AI-generated illustration

Does every old journey reach the right content in the right language?

A multilingual migration involves more than menu pages. Parameter-based profiles, categories, search, forms, downloads and media may use different addresses. Inventory content, language and dependencies. This guide prepares a migration and its checks; it does not assume the website being viewed needs an address change.

  1. Inventory URLs and usage

    Compare internal crawling, sitemap, publishing-system content and known journeys. Include parameters identifying profiles. Record language, type, status, known incoming links and planned destination; distinguish identity parameters from filter states.

  2. Map equivalents by language

    Map retained content to its genuine equivalent in the same language. For merges, confirm the destination retains useful information. If no relevant replacement exists, document retirement instead of automatically redirecting everything to a homepage.

  3. Prepare publication signals

    Update internal links, canonicals, language alternates and sitemap to final destinations. Verify declared equivalents exist and correspond. Also check files, images and downloads outside HTML pages.

  4. Test journeys in the prepared environment

    Open categories, profiles, search and forms in every language. Switch language from a specific profile and check identity retention. Test keyboard use, mobile viewports and Arabic layout; inspect HTTP responses and destinations, not only menus.

  5. Define redirects and retirements

    Test old URLs against the planned configuration and record destinations. Prefer a direct path to final content. Check loops, unnecessary chains and language mixing. Removed content without an equivalent should return a state consistent with removal.

  6. Plan monitoring and recovery

    Keep validated mappings and the last working state. Define blocking criteria, responsibility and rollback steps before changing anything. After authorised publication, monitor errors, journeys and indexing signals without promising a universal stabilisation time.

  7. Test deep links and files

    Include links to specific tables, appendices and downloads in the mapping. Check the destination opened by the browser, including its fragment. For translated files, compare title, language and edition. An equivalent HTML page does not automatically replace a PDF cited in a dossier.

Reading workshop

Four mappings to decide before moving

One matrix links old URL, destination, language, canonical and cited passage. An accessible endpoint alone does not preserve a reference.

Fictional data and records for learning: none of these results comes from a live service query.

Fictional plan DEMO-M04

old.example.invalid and new.example.invalid are demonstration addresses. Statuses are simulated plan outcomes, with no network request or executed migration.

  1. old.example.invalid/fr/notice/R-204#resultats → new.example.invalid/fr/notice/R-204#resultats

    Language and simulated response
    FR → FR; 301 then 200
    Canonical and fragment
    Canonical: new FR record; #resultats exists
    Citation and decision
    The compared passage is retained here; the coherent mapping still needs testing in the intended environment.
  2. old.example.invalid/en/record/R-204 → new.example.invalid/en/record/R-204

    Language and simulated response
    EN → EN; 301 then 200
    Canonical and fragment
    Wrong canonical points to FR record
    Citation and decision
    The English text is present, but the signal names another language; fix before acceptance.
  3. old.example.invalid/es/ficha/R-204 → new.example.invalid/fr/notice/R-204

    Language and simulated response
    ES → FR; 301 then 200
    Canonical and fragment
    FR canonical matches the received page, not the expected ES equivalent
    Citation and decision
    The Spanish citation loses its version; find the true equivalent or document its absence.
  4. old.example.invalid/ar/record/R-204#resultats → new.example.invalid/ar/record/R-204#resultats

    Language and simulated response
    AR → AR; 301 then 200
    Canonical and fragment
    Canonical: new AR record; #resultats absent
    Citation and decision
    The scenario page exists, but the full link no longer reaches the passage; restore a useful fragment.

Every arrival returns 200 in the plan. Can it be declared ready?

Open each proposition to compare its diagnosis. More checks may still be needed.

Yes, all four destinations respond.

No. That hides a wrong canonical, language change and lost fragment. Useful content also requires checking.

Yes, by replacing the remaining targets with the homepage.

No. The homepage preserves neither cited passages nor language equivalence.

No; keep the coherent FR case and fix the other three mappings.

Appropriate for this fictional plan. Then execute the prepared checks, including full links and text, without treating simulation as real results.

Fictional mapping log extract

Plan: DEMO-M04; no migration executed
Old base: https://old.example.invalid
New base: https://new.example.invalid
FR: language, canonical and fragment coherent in scenario
EN: FR canonical to fix
ES: language equivalent to find
AR: #resultats fragment to restore
Closure: no; checks still need executing

This matrix covers only FR, EN, ES and AR. RU and FI would still need inventory in a six-language project; do not extrapolate four decisions to the whole site.

Documentation of the rules, separate from fictional examples

Compare other situations and exercises

A profile keeps its slug but loses a parameter

Verify the same profile, not merely the page template. Test several IDs, encoded characters and an unknown value. One template URL cannot replace every profile.

A translated version has no equivalent

Check whether content is absent or wrongly connected. Create useful translation when justified; otherwise document the gap. Do not declare a section with another purpose equivalent.

A form changes language after an error

Check action, context fields and validation returns. Preserve language and test values needed for correction. Test the complete journey to the observed state with an authorised test destination.

The page survives but its anchor disappears

Fictional example: an old link reaches the right new page, but #results has been renamed. A final 200 status misses the problem. Preserve a compatible anchor or a meaningful section destination, then open the full link in each language and verify that the cited passage remains findable.

A download becomes a summary

Illustrative case: an appendix URL now opens a general summary. Check whether the file and its edition remain available. If the summary lacks the cited tables, document the loss and seek an exact replacement; the redirect does not establish document preservation.

Worked exercise

A migration swaps two profiles

Fictional example: the values and documents teach the method and do not describe a real organisation.

Each destination is translated into the requested language and returns 200. The two rows represent twelve variants whose content, not just status, must be checked.

If the table exceeds the screen, scroll horizontally; arrow keys work when the region is focused.

Starting information
Old record identifierLanguages affectedDestination identifier
Afr, en, es, ru, ar, fiA
Bfr, en, es, ru, ar, fiA

Your checks

  1. Build twelve old/new URL pairs.
  2. Compare destination ID and subject.
  3. Test an unknown profile and retained languages.
Read the answer

Answer and decision

A's six variants may be equivalent; B's six lose their entity. Twelve 200 responses are not twelve correct migrations. Fix B's mapping and check its specific incoming links and downloads.

If the case changes

If B genuinely merges into A, document retained information before calling the destination equivalent.

Record to retain

Keep mapping, identities, language, status and content-check result.

Documentation reference : Google Search Central — Site moves with URL changes · Consulted on

Record to retain

  • URL inventory with identity, language, type and retention decision.
  • Old-to-final URL mapping and justification for merges or retirements.
  • HTTP results, canonicals, language equivalents and tested journeys.
  • Verified configuration, monitoring criteria, responsibilities and recovery procedure.
  • Expected fragments and downloads, received editions and documented gaps.

Official references

Related protocols

Checks before reaching a conclusion

  • Does each old URL have an equivalent destination in the same language or a documented removal decision?
  • Do internal links, canonicals, language alternates and discovery files identify the same final destination?
  • Has a record with parameters or an anchor been tested end to end, beyond checking its HTTP code?
  • Does the full migrated link reach the expected passage or file?

Frequently asked questions

Should every translated slug change?

Not automatically. Choose a structure consistent with content and journeys. Additional changes increase mappings to maintain; establish their value beforehand.

Can every page redirect to the homepage?

A generic destination usually does not restore expected content. Seek a relevant same-language equivalent. Without replacement, handle retirement explicitly instead of hiding information loss.

Is the sitemap a sufficient inventory?

It is a starting point. Compare linked pages, parameter-based profiles, files and application journeys. Useful content may be absent while stale entries remain.

When should final checks run?

Before publication on the prepared configuration, then afterwards on actually served URLs. Compare both states. Late changes to routes, content or dependencies require affected checks to be repeated.

What to keep the site before switching?

A inventory of URLs, essential content, links and configurations useful for recovery. The preserved elements must allow to check the correspondences and restore the routes in case of a problem.

DEEPER READING / PRACTICE

Plan URL mappings before a website migration

A reorganisation changes URLs and language paths. Preparing a mapping before the switch helps preserve user journeys and verify destinations after publication.

Updated on .

Priority checks

Link each old page to a relevant destination in the same language. Find fusioned content, removed pages, internal links and forms or files dependence.

Interpretation pitfalls

Redirecting all the old URLs to the home deletes their intention. Technically successful migration may, however, introduce language changes or interrupted routes.

Working record to retain

The migration plan contains correspondences, reasons, checks before and after the shift and the return procedure. A sample includes important pages as well as fusion and withdrawal cases.