We localise your website, e-commerce platform and software in 64 languages, adapting them to the target market’s culture, search behaviour and user experience.
Send us your file or service requirements. We will provide a written price and delivery plan based on the language pair, document type, field of expertise, notarisation requirements and expected delivery date.
Answers to common questions about website, software and localisation services
Translation transfers the meaning of a text into the target language. Localisation also takes into account the culture, usage patterns and user-interface context of the target market. Date, number, currency and measurement formats, as well as button lengths, menus and brand tone, may be included in the scope. Websites and digital content can be localised with the target audience’s language and usage habits in mind. Headings, product descriptions, buttons and communication text are prepared in line with the brand’s tone of voice. Date, number and currency formats may also be adapted. Additional work such as SEO copy, content uploading and technical integration is defined separately during the quotation stage.
Yes. The language content of SaaS and web applications, iOS and Android mobile applications, and desktop and enterprise software can be localised within the project scope. User-interface text, onboarding content, error messages, notifications, store descriptions and help content are planned together. The translatable fields, target languages, screen context and delivery format are defined at the outset. Technical integration and on-screen testing are scoped separately.
We can work with language and content files such as JSON, XML, HTML, CSV, PO and XLIFF. Word and Excel files or string lists exported from a platform can also be assessed. A sample file is reviewed first to establish the appropriate workflow and identify the translatable fields, keys, tags, variables and character limits. The delivery format and any required technical preparation are clarified during the quotation stage.
For most projects, there is no need to share the software’s complete source code. Language files or string lists exported from the platform, screenshots and contextual notes may be sufficient. If text is embedded directly in the code, the extraction method is agreed with the development team. Variable functions, plural forms, character limits and details of any test environment are assessed at the outset.
The translatable text is separated from the file’s technical structure. File keys, HTML/XML tags and placeholders such as {name} or %s are identified as protected elements. Required order, plural forms and contextual information are checked, and only the text designated for translation is processed. Delivery-format checks are planned within the project scope. Functional software testing and code integration are carried out separately with the development team.
Target-market keyword research and the adaptation of titles, descriptions and metadata can be planned within the requested scope. Technical implementation, such as multilingual URL structures and hreflang, is assessed separately together with the website infrastructure and the responsibilities of the development team. SEO copy and technical implementation are not automatically included in every translation quote. The work to be completed is specified in writing during the quotation stage. No guarantee is given regarding search-result rankings.
Content entry and language-file delivery for WordPress, Shopify, Magento, WPML or other platforms can be planned according to the platform’s capabilities and the requested service scope. Direct website upload, application integration and publication are not automatically included in every translation assignment. The fields to be uploaded, access method, test environment and person responsible for publication are defined at the outset. Any need for technical development is assessed separately.
On-screen linguistic quality assurance (LQA) can be planned according to the available screens and project scope. Text is reviewed for contextual suitability, consistency, overflow or truncation, along with buttons, menus, notifications and variable use. Where necessary, the target language’s writing direction and display conventions are also assessed. Findings are shared with the relevant team. The scope of linguistic review and the software’s general functional testing are defined separately during the quotation stage.
Files containing version or date information are compared to identify new and changed strings, and the update scope can be planned based on these changes. Unchanged text, terminology choices and previous approvals are reviewed for consistency. Terminology lists and translation memories may be used according to the needs of the project. Company-approved terminology, product names and previous translations support consistency. The files to be used, responsibility for updates and data-sharing conditions are agreed in advance. Repetitions stored in the translation memory are checked in context, and previous translations are not automatically assumed to be correct. Text whose context has changed is reviewed again. Delivery dates and update responsibilities are clarified in advance.
The translation price is calculated according to the language pair, text volume, field of expertise, file legibility, delivery schedule and formatting requirements. Sworn translation, notarisation and additional services also affect the scope. After reviewing your file, we prepare a quote specifying which charges are included. General prices provided before the file is reviewed may not constitute a final quotation. For website and software projects, the word or string count, number of target languages and markets, repetition rate, file format, technical preparation, SEO, content entry and LQA scope are assessed together. Delivery time varies according to the language, text length, level of specialisation, file quality and any need for official certification. Short standard documents may be prepared more quickly, while multi-page or technical files require more work. We confirm the delivery date after reviewing the file and determining the scope. Revision and any required certification stages are also considered when calculating the timeframe. After the source file or sample content has been reviewed, the scope, total price and delivery schedule are provided in writing.
Information Notice: These answers are provided for general information only. The process may vary according to the technical scope, file format, number of languages and requested additional services.
Explore related services that complement your website and software localisation process.
Specialist translation for software, APIs, user manuals and technical documentation.
Corporate translation aligned with your brand voice for company, e-commerce and digital marketing content.
Sector-specific translation for clinic websites, treatment pages and international patient communications.