How to keep a multilingual small-business website accurate

Create one source-of-truth sheet for facts that must agree in every language. Think of it as the label on a filing cabinet: each language page can explain the offer naturally, but everyone checks the same drawer before changing a price, telephone number, address, service area, opening time, booking rule, or delivery condition.

Do not make one language page the hidden master if nobody knows that it has this role. Give each fact an owner, a last-checked date, and the URLs where it appears. Store approved terms for service names and calls to action too. This small terminology list keeps a translator from turning the same service into two apparently different products.

Not every edit needs the same response time. Mark a change red when outdated information could stop a purchase or send a customer to the wrong place: a closed date, wrong price, dead booking link, unavailable service, or changed safety instruction. Update every affected language before announcing the change.

Amber changes affect understanding but can be scheduled, such as a revised service description, a new photograph, or a better answer to a common question. Green changes are stylistic improvements with no change to the underlying offer. This queue lets a small team protect customers first instead of trying to perfect six pages at once.

Equivalent pages should support the same customer decision, but they do not need matching sentences. A UK reader may ask for a quote, a Swedish customer an offert, and a German customer an Angebot. Currency display, address order, date format, tone, and examples should feel familiar to the intended audience while prices, availability, and service limits stay aligned.

Give the local reviewer a short brief: what changed, what must remain exact, what can be adapted, and which page action matters. Then ask the reviewer to check the finished page in context. A string can be linguistically correct and still fail because a button is too long, the linked form is in another language, or the example makes no sense locally.

Each language should have its own stable URL. Google recommends that every equivalent page list itself and all other language versions with reciprocal hreflang links; an x-default entry can provide a fallback. Google also recommends a self-referential canonical for the preferred URL. Do not point all translated pages to the English page as canonical, because each genuinely translated page is useful in its own right.

The visible content must actually be in the declared language. Google says it determines language from page content rather than the lang attribute or hreflang alone. The W3C still recommends declaring the default language on the html element because browsers and assistive technology use that information. These signals have different jobs and should agree.

Imagine a bicycle tour company changes its summer meeting point and requires online booking 24 hours ahead. The owner first changes the two facts in the central record and marks them red. The six page owners receive the same brief, update the visible tour details and booking button, and adapt the wording naturally. They also check the confirmation page and contact link, not just the main service page.

Before release, one person opens all six URLs side by side. They confirm the same meeting point, deadline, price basis, and next step; check that each page stays in its language; and test the booking journey on a phone. The update is recorded with its date. A later monthly review can now distinguish a checked fact from an assumption.

Start with the facts most likely to change, then inspect the technical connections. You do not need to rewrite the whole site. A compact monthly check catches small differences before they become customer complaints or confusing search pages.