Repair a language switch that opens a different service
A language change should preserve the subject the reader chose. A website can contain accurate Dutch, French, German and English pages yet connect them incorrectly. Translating the paragraphs again will not fix a relationship that points to another service.
This fictional investigation concerns an equipment service business with two offers: workshop repair, reference SV-42, and on-site inspection, reference SV-41. The team maintains four language versions. A French reader on workshop repair switches to Dutch and arrives at on-site inspection.
Establish what makes the pages equivalents
The source owner confirms the two service identities and their scope. Workshop repair requires an initial description before equipment is sent to the business. On-site inspection starts with a request concerning equipment at the customer's premises. Neither action is an automatic appointment confirmation.
The titles are reviewed as language-specific descriptions of those separate offers.
| Service reference | English | Dutch | French | German |
|---|---|---|---|---|
| SV-42 | Workshop repair | Herstelling in het atelier | Réparation en atelier | Reparatur in der Werkstatt |
| SV-41 | On-site inspection | Inspectie ter plaatse | Inspection sur site | Prüfung vor Ort |
These are fictional approved fixture labels. The important relationship is the service reference and reviewed meaning, not whether one title looks like a literal translation of another. A real project uses the organization's actual source and language reviewers.
Locate the first change of subject
The French repair page correctly identifies SV-42. Its Dutch selector opens the first page in a Dutch services array. That array is sorted by its localized title and begins with SV-41. The French array happens to place SV-42 first. An index position has been treated as if it were a service identity.
The Dutch destination is internally consistent: its heading, description and enquiry all concern inspection. This makes the mistake easy to miss when someone reviews pages individually. The defect becomes visible only by following the actual switch from inside the French repair page.
The reviewer records the starting route, selected language, target route and service reference at both ends. The first disagreement is the counterpart lookup, before the customer enters an enquiry. Rewriting the destination's inspection copy as repair would corrupt an otherwise valid service.
Replace positional matching with the approved family
The corrected fixture connects each language version to its service family. Switching languages from SV-42 resolves another maintained SV-42 page. SV-41 retains its own family and routes. The implementation uses supported content relationships rather than assuming translated URLs have the same spelling or position.
The reviewer opens French repair, selects Dutch and confirms the repair description and receiving action. They then move to German and English and return to French. Each step preserves SV-42. A separate round begins from SV-41 and keeps inspection intact.
A changed navigation order is included in the rehearsal. The language relationship must survive an editor rearranging a menu; presentation order is no longer responsible for identity.
Follow the corrected page into a request
The reader starts an enquiry from Dutch repair using fictional equipment details. The receiving record R-42 identifies SV-42 and the requested reply language. The visible service name helps staff read it, while the stable reference determines the relationship. The form does not infer the service by translating its heading again.
A separate enquiry R-41 starts from inspection and retains SV-41. The reviewer checks the ordinary receiving view and the customer receipt. Neither record is described as a confirmed appointment simply because its submission succeeded.
This step demonstrates why the problem was more than navigation. A wrong counterpart could send a carefully written request into a different operating process. The corrected result preserves both the selected service and the meaning of the action it offers.
Inspect a version that is not ready
The test fixture temporarily withholds the German repair version from publication. The approved behavior explains that this repair information is unavailable in German and offers an explicitly labeled maintained version. It does not send the reader to German inspection or claim that the repair service itself has disappeared.
The content owner approves the wording and alternative. A missing version is not permission for the developer to publish a draft translation. After the reviewed German page is restored, its counterpart route works again without changing SV-41.
Reconcile machine-readable relationships
The visible selector and the page's language relationships should agree. Google's localized-version guidance describes self and reciprocal references between equivalent language pages. Canonical and alternate signals need to describe the actual reviewed pages, not copy the same positional error into the document head.
Inspect the generated head of every maintained SV-42 page and the separate SV-41 family. Keep each canonical destination accurate. An annotation is supporting evidence about the page relationship; it does not approve the wording or guarantee a search result.
Close with a repeatable acceptance record
The final record includes the approved family table, old positional lookup, corrected counterpart routes, successful four-language journey, R-42 and R-41 receiving checks, and the explicit unavailable-version result. It also identifies the source editor and the reviewers who approved the displayed labels.
A new maintainer can now add a language version without guessing which page it replaces. Multilingual website development establishes that structure. Content publishing workflows handle the separate question of whether the next source revision has been approved in each language.