Start with a page inventory
Publishing a translated page is not the end of the job. Contact details change, services are renamed, and instructions become clearer. If the original page changes while its translations do not, visitors may receive different answers depending on the language they use. For a small website, the goal is not to translate every edit immediately. It is to know which pages exist in each language and make deliberate decisions about updates.
Create a simple inventory with one row per page and language. Record the page title, URL or content-management-system entry, the person responsible, the date of its last content review, and its status. Useful statuses might be current, needs review, in translation, ready to publish, and temporarily unavailable. Link each translated page to the page it corresponds to so nobody has to guess which versions belong together.
The inventory also makes gaps visible. A language may have a translated homepage but no translated contact page, or an old page may still be reachable from search even though it has disappeared from navigation. You can address those gaps one at a time rather than treating the whole site as a single translation project.
Decide what triggers an update
Not every source-page change needs the same response. A correction to a street address, opening hours, eligibility rule, form instruction, or price can affect what a visitor does next; flag it for prompt review in every available language. A minor change in tone may be able to wait for the next scheduled review. Write down these priorities so the decision does not depend on who happens to make the edit.
Give editors an easy way to flag translation work at the moment they change a page. This could be a field in the content system, a task in a shared board, or a note in a spreadsheet. Include a short description of what changed and where it appears. “Contact phone number changed in the final section” is more useful to a translator than “page updated.” If several people can edit the site, agree on who checks the queue and who can mark an item complete.
Give translators the context they need
A translator needs to know more than which words changed. Share the purpose of the page, its intended audience, and any terms that should remain consistent across the site. Keep a short glossary for recurring names, service descriptions, navigation labels, and button text. It does not need to be elaborate; a shared document that people actually use is better than a detailed guide nobody maintains.
Provide the surrounding page or a preview, not just isolated sentences. A short label may mean different things on a menu, a form, or a confirmation message. Images, diagrams, downloadable files, and image alternative text may also contain information that needs translation or adaptation. Where the translated version cannot be completed yet, keep its status visible to the team rather than silently assuming that text-only changes cover the whole page.
Review the published page, not just the copy
Before publishing, have someone check the translated content in its page layout. Longer words can wrap awkwardly in buttons or headings. Links may lead back to a different language, and a translated instruction may point to a form that has not been translated. Check page titles, navigation labels, error messages, and any text attached to images as well as the main body copy.
After publishing, follow the page as a visitor would: use the language switcher, open key links, and try the main task the page supports. If your site uses language annotations for search engines, make sure they point to the corresponding versions rather than unrelated pages. Do not link to a translated version that does not exist. When only some pages are available in a language, make that limitation understandable instead of leaving visitors to discover it through broken or confusing navigation.
Make maintenance a recurring task
Assign a content owner for each group of pages and set a review interval that fits how often the information changes. A page with practical instructions may need closer attention than a stable description of the organization. During a review, compare each language version with its source page, check outstanding update requests, and confirm that links and contact details still work. Record the review even if no edits are needed.
If your team cannot update every translation at once, prioritize pages that help people complete important tasks. It may be safer to pause or clearly qualify an outdated translated page than to leave misleading instructions in place. Track what remains unfinished and revisit it at the next check-in. A modest workflow with named owners, visible statuses, and regular checks gives a small site a better chance of staying useful in every language it offers.
