Website translation and software localisation

We start by defining the content, markets and technical format. Marketing pages, interface strings, documentation, automated messages and SEO elements each have their own context, length limits and checks.

Translation and localisation: what is the difference?

Translation conveys meaning in another language. Localisation adapts the entire user experience to the target market: feature names, tone, date and number formats, units, legal notices, keywords and user expectations.

Localised text should sound natural while preserving the product’s functionality and avoiding promises unsupported by the original.

What the project can include

  • Home, service and sales pages, blog posts and help centres
  • Menus, buttons, forms, notifications and error messages
  • Mobile and web apps, account settings and onboarding
  • Automated emails, order confirmations and transactional messages
  • App store descriptions, FAQs, instructions and knowledge bases
  • SEO titles, meta descriptions, image alternative text and internal link text
  • Legal and information pages, with separate specialist review where needed

Variables, tags and text without context

Software files often contain variables, HTML tags, abbreviations, plural forms and strings that are unclear outside the interface. These elements must be protected against accidental changes. Reliable translation therefore needs context such as screenshots, feature descriptions or access to a test environment.

A word such as “Submit”, “Save” or “Order” can require different translations depending on whether it is a button, noun, command or status. Translation in context reduces later corrections and maintains interface consistency.

For developers
Supply a locked or clearly labelled file structure, a list of elements that must remain unchanged and a test version of the product. Use controlled files where possible instead of manually copying translations from email.

SEO localisation is more than literal keyword translation

People in different markets do not always search for direct translations of the same term. Important landing pages should align the primary topic, search intent, title, headings, meta description and link text. Content must remain useful and natural, without mechanical repetition.

We distinguish language translation of existing content from a separate market-specific SEO analysis, which can include keyword research, structural changes and internal linking recommendations.

Files and workflow

We can work with editable documents, spreadsheets, CMS exports and common localisation formats, depending on the project. We check character encoding, repeated segments, protected tags and the method for importing translations back into the system.

WordPress and similar systems can use a controlled content export or agreed access. Changes to the theme, plugins or site structure require a separately defined technical brief.

Website and software localisation process

  1. We define target markets, languages, audiences and the business objective.
  2. We inventory content, files, repetitions, length limits and protected elements.
  3. We agree terminology, tone, product names and forms of address.
  4. We translate and localise the content in an editable format.
  5. We check text in its interface context, including wrapping, buttons and messages.
  6. We deliver final files and record approved terms for future updates.

Project prices and turnaround

The cost reflects unique text volume, language count, format, available context, SEO adaptation, technical checks and the number of revision rounds. For frequently updated websites, phased delivery and a terminology database help keep new content consistent with approved translations.

Frequently asked questions

Can you translate directly in WordPress?

Controlled access or content exports may be used, depending on the system and security rules. We define who enters text, approves changes and creates backups before starting.

Do you translate SEO titles and meta descriptions?

Yes. They can be translated and adapted to the target market. Full SEO localisation also checks actual search terms and intent.

How do you protect variables and code?

We work in files where variables, tags and code elements are protected or clearly labelled, followed by a technical format check.

Can you localise an app without its source code?

Yes, if we receive exported text strings and enough context, such as screenshots or test access. The source code is usually unnecessary for translation itself.

Do you handle subsequent updates?

Yes. Updates are quickest when approved terminology is recorded and only new or changed strings are supplied.

Send your document: Send a link, content export or sample localisation file and specify target languages, markets, CMS, SEO scope and deadline. You will receive a proposed workflow, delivery format and clear quote.

Request a quote