The quick answer
Prepare a website for translation by agreeing which visitor task the new language version must support, stabilizing the source copy and giving the reviewer the context around each string. Include navigation, metadata, forms and completion messages in the inventory. A page is ready for review when someone can follow the whole task in the intended language.

Prepare a website for translation by agreeing which visitor task the new language version must support, stabilizing the source copy and giving the reviewer the context around each string. Include navigation, metadata, forms and completion messages in the inventory. A page is ready for review when someone can follow the whole task in the intended language.
Define the journey before counting pages
For a fictional bookshop, the first task might be reserving a book for collection. Write down the arrival page, collection instructions, form and confirmation. Include any message that explains when the shop will reply. Decide who will review the wording and who can confirm the underlying business details.
Use one record per page or shared component. Identify the source version, target language and region where relevant, owner, translation status and next review. When the source changes during translation, flag the changed passage for the reviewer so the two versions can be reconciled.
Give short strings enough context
A translator receiving the word “Collection” needs to know whether it describes a group of products or picking up an order. Supply the page, the control’s job and the destination it opens. For an error message, include the condition that produces it and the action the visitor can take next.
Keep complete messages together when possible. Splitting a sentence into several independently translated pieces can create awkward word order or agreement. W3C’s internationalization tips recommend concise source text and care when constructing sentences from multiple strings. W3C internationalization tips
Build a short terminology sheet for recurring business words. Record the intended meaning, preferred translation after review and any names that should keep their original spelling. The shop might need consistent language for collection, reservation and availability. Have the business owner confirm that each term describes the actual service.
Allow translated text to change the layout
Translated text often occupies a different amount of space. Review the real translations inside buttons, navigation, cards and form errors at narrow widths. Allow wrapping where it preserves meaning. Check font coverage for the target script and inspect text alongside icons and photographs. W3C recommends flexible layouts and warns against tight fixed-width containers for translated text. W3C on text size in translation
For the bookshop, test a longer collection instruction in the mobile menu and on the submit button. If it becomes unclear, review the wording with the translator and the component with the designer. Preserve the information the visitor needs to choose the next step.
Include the content outside the visible paragraph
Record page titles, descriptions, meaningful image descriptions, form labels, validation feedback and confirmation messages. If an illustration contains essential words, plan a localized version or move that information into selectable page text. Include downloads and third-party booking steps in the journey review.
Ask the implementer to verify the document language and language changes inside the page, and to check names, addresses and date formats appropriate to the intended audience. W3C’s tips address language declarations, local form conventions and visible navigation to localized content. W3C internationalization tips
Finish with a task review
Give a fluent reviewer a concrete task and sample input. Ask them to reach the confirmation without coaching, then record unclear wording, broken destinations, unexpected fallback text and layout problems. Resolve those observations with the relevant owner and repeat the affected step.
After publication, assign a review trigger for changes to prices, service instructions or shared navigation. Keep the source and translated versions linked in the inventory so the next edit reaches both owners. Use the locale rollout worksheet to capture those decisions. Teams using Framer can also follow the localization rollout guide.


