Start with the user journey
A multilingual experience is not complete when its menus have been translated. Users need to find the same service and page in their chosen language, understand the form and read the result of an action. Review key journeys such as viewing a project, sending an enquiry and receiving an error in each language, rather than counting translated strings.
Treat text direction as structure
In Persian and Arabic, reading order, punctuation and mixed content such as numbers, email addresses and Latin terms require attention. Visually reversing a page is not enough. Forms, directional icons, navigation and mixed text need to be reviewed together. Brand marks should not be mirrored simply to match the page direction.
Keep the underlying meaning consistent
Dates, amounts, phone numbers and order states should represent the same facts in every language, even when formatting differs. One stored timestamp can be presented through a suitable calendar without creating a different reality for each locale. Official product names and translated descriptions likewise need explicit editorial decisions.
Evaluate quality in the rendered page
A translation that looks correct in a text file may add lines to a button or card and disrupt the experience. Review after fonts have loaded and at different viewport sizes. Checking meaning, layout and behaviour together makes multilingual delivery part of product quality.