Inspect the page-head limitation before replacing a multilingual site
A site can publish useful language versions while giving search systems confusing instructions about them. Before treating that as a reason to rebuild, determine whether the existing publishing system can express the required page-specific metadata. A wrong template default and a genuine platform limitation call for different decisions.
In this fictional assessment, four language pages describe the same industrial support service. Each body is accurate for its language, and the visible switches reach the right subject. The concern appears in the page head: every version declares the English homepage as its canonical URL.
Record what is wrong and what already works
The team checks the rendered HTML, not only the administration screen. The French service page contains French copy at its intended URL but points its canonical element at the English homepage. The Dutch and German pages do the same. Their titles and visible breadcrumbs are already page-specific.
The existing generator has a documented page-level canonical field and a template fallback for pages where that field is absent. In the inspected project, the editor supplies the correct per-page URL, but the head template always reads the site-wide fallback first. The publishing system is capable of expressing the intended value; this implementation does not use it correctly.
That distinction matters. A new platform would still need a correct template and a maintained page relationship. Moving the same mistaken default into a different system would not resolve the underlying choice.
Compare the practical alternatives
A bounded repair would change the head template's selection logic, verify the published values and document the required field. A wider template overhaul could also improve unrelated metadata consistency but carries more pages into review. A complete replacement would include content migration, route preservation, editorial training and the same final head checks.
For this fixture, the owner selects the bounded repair because the inspected generator supports the needed values and the rest of the publishing task is maintainable. The decision is conditional on a preview proving that the correction is genuinely page-specific. It is not a general recommendation to keep every old system.
The team records what would change that conclusion: an unsupported publishing dependency, inability to maintain the field safely, or another demonstrated limitation that blocks required journeys. None is inferred merely from the canonical error.
Verify the repaired output and its controls
The preview now gives each approved language page its own intended canonical URL. Alternate-language annotations name genuine equivalents and include the relevant self and reciprocal relationships. The canonical and alternate roles are checked separately; listing another language does not mean that every translation should canonicalize to the English page.
The reviewer checks an unrelated English service page and the homepage. Their existing destinations remain correct. A preserved old URL still redirects to its agreed successor rather than acquiring a new, competing page. The repair does not alter page bodies or replace the accurate language switches.
Google's localized-page guidance explains the relationship annotations, while its canonical guidance explains canonicalization. These instructions help describe the intended pages; they do not guarantee indexing or a ranking outcome.
Leave a decision record a maintainer can use
The record includes the observed global fallback, the inspected per-page capability, the chosen repair and the final rendered-head examples. The maintainer knows where the canonical value is set and how to inspect the output after a future template change.
A proposal can now state a small, testable result instead of pricing an unexplained rebuild. If later evidence reveals a broader limitation, that evidence can support a separate decision. Website redesign begins with this kind of inventory: what is wrong, what is still useful and what the next release must prove.