Quality in website translation

Website translation is not just the transfer of texts from one language into another. A translated website must work in the target market, preserve its commercial meaning, respect the technical structure of the site and maintain a coherent user experience.

In a multilingual website, many elements are involved: visible text, menus, buttons, forms, metadata, URLs, automatic messages, legal pages, calls to action, images, tags and the SEO structure. If one of these elements is mistranslated or left outside the process, the result can look unprofessional even if the main paragraphs have been translated correctly.

The ISO 17100 standard provides a useful framework because it requires work by professional translators, independent revision, clear specifications and project management.

What website translation is

Website translation is the linguistic adaptation of a site's content so that it can be used in another language or market.

It may include service pages, product pages, blog articles, menus, forms, legal texts, SEO titles, meta descriptions, buttons, error messages, automated emails, alternative text for images, slugs or URL paths and downloadable content.

In simple projects, translation can be carried out from Word or Excel documents. In more technical projects, work may be done with HTML, XML, JSON, XLIFF, CMS exports or localization platforms.

Website translation and localization

Translating a website is not always enough. In many cases, localization is also required.

Localization adapts content to the country, the audience and the real use of the website. It can affect currency, units of measurement, cultural references, forms of address, commercial tone, date formats, examples, legal texts, local search engines and user behaviour.

A sentence that works in Spanish may sound cold, exaggerated or unnatural in French, German, Italian or English. The opposite can also happen: a literal translation may preserve the basic meaning, but lose commercial force.

That is why pre-production matters. Before translation starts, the target market, tone, language variants, SEO objectives and technical elements that must be preserved should be defined.

International SEO in website translation

A translated website must be able to rank.

SEO-oriented website translation is not about repeating keywords. It requires adapting search intent, the terms actually used by users and the way each market searches for the service.

In a multilingual website project, it is advisable to review the SEO title, meta description, H1, H2 and H3 headings, slugs, internal links, anchor text, button text, mobile-visible content, structured data, hreflang tags, canonical tags, sitemap, duplicate content and local search intent.

A translation that is linguistically correct may still perform poorly in search engines if these elements are not adapted.

ISO 17100 applied to website translation

ISO 17100 is not an SEO standard. It is not a specific web development standard either. But it does help to control the translation process.

In a website translation carried out under ISO 17100, there must be prior project analysis, definition of specifications, selection of a qualified translator, the translator's check, independent revision by another person, project management, final verification and release, and handling of comments.

This reduces frequent errors in translated websites: inconsistencies, omissions, translations without context, tone problems, poorly chosen terms or texts that do not respect the intended use of the page.

The problem of context

One of the main risks in website translation is translating isolated strings without seeing the page.

A button such as “Send”, “Request”, “Learn more” or “Book” can be translated in different ways depending on context. The same applies to menus, forms, legal notices, automated messages and calls to action.

For that reason, whenever possible, screenshots, URLs, a staging environment or information about where each text will appear should be provided.

The translation process improves when the translator and reviser understand the function of each element.

Independent revision and in-context review

Independent revision is mandatory in a service conforming to ISO 17100. In website translation, it may also be advisable to carry out an in-context review after the texts have been integrated.

That review can detect truncated text, buttons that are too long, incomplete forms, untranslated labels, incorrect links, inconsistencies between pages, errors in SEO titles, tone problems, unnatural calls to action, duplicate content and poorly adapted metadata.

A website may be well translated in an Excel file and still fail once published. Context changes the perception of the text.

Terminology and consistency

Website translation often combines commercial, technical, legal and corporate content. That is why terminology management is important.

A company should use its services, product names, job titles, sectors, processes, guarantees, certifications and calls to action consistently.

Translation technologies help through translation memories, glossaries, CAT tools and quality checks. But the final decision must be taken by a professional.

A poorly defined glossary can produce a website that is consistent, but wrong.

Translation of legal pages and forms

Legal pages and forms require special attention.

Privacy texts, cookie notices, terms of use or consent wording should not be translated automatically without reviewing the destination country and the real use of the website.

Confirmation messages, autoresponders, form validations, mandatory fields and texts related to data protection must also be reviewed.

For this type of content, it may be necessary to coordinate the translation with legal review or with the client's legal officer.

Website translation and conversion

A translated website must preserve its ability to generate contacts, sales or requests.

This affects headlines, commercial arguments, social proof, calls to action, forms, trust signals, frequently asked questions, navigation structure, error messages and confirmation texts.

A translation that is too literal can sound correct but fail to persuade. An adaptation that goes too far can move away from the original. Quality lies in finding the balance between fidelity, naturalness and commercial purpose.

Website project management

Translation project management is decisive in websites with many pages or several languages.

The project manager must control files, versions, glossaries, deadlines, translators, revisers, deliveries and client changes. Where appropriate, the project manager must also coordinate with the SEO team, developer, designer or CMS manager.

In website projects, a small change can affect several pages. Without control, it is easy for one version to become outdated or for unrevised texts to be published.

Quality and pricing in website translation

The price of website translation depends on many factors: number of words, languages, format, text extraction, revision, SEO, localization, integration, quality control and in-context review.

That is why translation rates should be compared by looking at what each quotation includes.

Translating an exported document is not the same as working on a complete multilingual architecture with SEO titles, slugs, meta descriptions, internal links and review in a real environment.

LinguaVox and website translation

LinguaVox translates and localizes websites for companies that need to publish content in several languages. It can work with exported texts, structured files, SEO content, metadata, glossaries, translation memories and in-context review depending on the scope of the project.

The company applies professional translation processes with independent revision and project management under ISO 17100 when the service requires it.

Request a website translation quote

Frequently asked questions about website translation

What is website translation?

It is the translation of a website's visible and technical content: pages, menus, buttons, forms, metadata, automated messages, legal texts, blog posts and other elements that form part of the user experience.

What is the difference between website translation and website localization?

Translation transfers the content into another language. Localization adapts that content to the target market, including tone, cultural references, formats, currency, calls to action, SEO and user expectations.

Does ISO 17100 apply to website translation?

Yes, when the service is provided as professional translation with a qualified translator, check, independent revision, project management and final verification.

Should SEO titles and meta descriptions also be translated?

Yes. SEO titles and meta descriptions influence SEO and the way users understand the page in search results. They should not be left untranslated or translated literally without checking search intent.

Why is it important to review a website after integration?

Because truncated texts, buttons that are too long, formatting errors, untranslated strings, incorrect links or context problems may appear only after the translation is implemented.

Which files can be used to translate a website?

It depends on the site. Work can be done with Word, Excel, HTML, XML, JSON, XLIFF, CMS exports, localization files or controlled access to a translation platform.