Website translation · CMS localisation · Multilingual SEO

Website translation and localisation services

We localise websites across CMS and ecommerce platforms, adapting content, structure and user journeys for each market while protecting multilingual SEO, language relationships and the publishing workflow.

Specialists in the destination marketWorkflow matched to risk and volumeQA linguistic and editorial
MULTILINGUAL CONTENTSOURCE → MARKET
01 · DiagnoseGoal, audience, channel and marketbrief · context · terminology
02 · AdaptWebsite localisationlanguage · intent · brand voice
03 · ValidateReviewed and ready to publishQA · consistency · delivery
LANGUAGE EXPERTISEVALIDATED CONTENT ✓
01 / Website localisation

A multilingual website is a connected publishing system

Pages are only one part of a website localisation project. Navigation, reusable components, forms, taxonomies, media, metadata, structured content and integrations all need to work in the right language and context. We combine market research, professional localisation and in-context QA so the translated site feels native and remains manageable after launch.

Content types, components, forms, metadata, assets and language relationships all require controlled handling. We inventory the website and publishing system before choosing direct CMS, connector, API or file-based workflows.

Tell us about your project →
01

Website and content inventory

Pages, templates, components, forms, taxonomies, media and metadata mapped before localisation starts.

02

Market-specific localisation

Local search intent, terminology, brand voice, UX copy and cultural expectations built into the content.

03

CMS and file workflows

WordPress and WPML, Shopify, WooCommerce, PrestaShop, Magento, BigCommerce, XLIFF, XML, CSV and API-based delivery.

04

Live website QA

Language switching, hreflang, canonicals, links, forms, assets, responsive layouts and language leakage checked on the public site.

02 / How we work

A controlled workflow from brief to publication

Public QA checks URLs, language switching, hreflang, canonicals, links, forms, assets and responsive rendering. Existing slugs and IDs remain stable unless a documented migration requires change.

  1. 01

    Brief and diagnosis

    Audit the website, CMS, integrations, content types and current language setup.

    Controlled milestone
  2. 02

    Market and content research

    Map equivalent pages, templates, fields, taxonomies, assets and ownership across markets.

    Controlled milestone
  3. 03

    Localisation and production

    Research local demand, search intent, terminology, competitors and user expectations.

    Controlled milestone
  4. 04

    In-context quality assurance

    Localise content and metadata with specialists in the destination market.

    Controlled milestone
  5. 05

    Implementation and handover

    Implement through the agreed CMS, connector or file workflow without breaking relationships.

    Controlled milestone
  6. 06

    Launch QA and iteration

    Review the public website on desktop and mobile, then prioritise fixes and future updates.

    Controlled milestone
03 / Scope

Website localisation across CMS platforms

01

Strategy and inputs

We support website translation and CMS localisation for corporate sites, content platforms and ecommerce environments. The workflow can cover discovery and service pages, menus, forms, calls to action, reusable blocks, taxonomies, metadata, image ALT text, structured fields, legal content and ongoing updates.

02

Content and production

We can work directly in an agreed CMS workflow or through XLIFF, XML, CSV, JSON, API and other controlled exports. WordPress and WPML remain a core area of expertise, including page relationships, String Translation, menus, taxonomies, Yoast fields and fallback behaviour.

03

Quality and implementation

We also work with Shopify, WooCommerce, PrestaShop, Magento or Adobe Commerce, BigCommerce, headless builds and bespoke content systems where access and responsibilities are clearly defined. Deliverables may include a content inventory, UK or market-specific keyword research, a query-to-URL map, terminology and brand-voice guidance, translation memories, localised copy, implementation support, redirects where genuinely required, linguistic QA and a post-publication crawl.

04

Delivery and continuity

Existing IDs, URLs and language relationships are preserved unless the migration plan documents a reason to change them.

04 / Evidence

Website localisation · Ontranslation

Decisions grounded in market and content evidence

A CMS connector can move content between systems, but it cannot decide whether a query, category, CTA or proof point works in another market. Effective website localisation joins editorial and technical decisions: what to adapt, how to structure it, where it is stored and what the live user actually receives. We preserve the source architecture where it works, challenge it where local intent differs and document responsibilities between translators, developers, SEO teams and content owners. WordPress and WPML projects receive the same discipline as other platforms: correct language relationships, visible strings, menus, metadata, forms and frontend output. The final checkpoint is always the public URL after caching, because a correct CMS entry can still produce broken links, missing assets, mixed-language modules or incorrect search signals.

Discuss the project →
06 / Frequently asked questions

Questions about website localisation

Which CMS platforms do you work with?

We work with WordPress and WPML, Shopify, WooCommerce, PrestaShop, Magento or Adobe Commerce, BigCommerce, headless environments and bespoke CMS workflows. We confirm the safest method after reviewing the platform and access available.

Do you translate directly in the CMS?

Yes, when direct access is controlled and efficient. We can also use XLIFF, XML, CSV, JSON, APIs or other export-and-import workflows.

Do you configure WordPress and WPML?

We can support content-related WPML configuration, page and taxonomy relationships, String Translation, menus, metadata and multilingual publishing. Development work is scoped separately where required.

Is multilingual SEO and GEO included?

It can be. We research destination-market queries and adapt headings, metadata, internal links, entities and useful answers instead of translating an existing keyword list literally.

How do you prevent mixed-language or broken pages?

We test navigation, templates, reusable components, forms, assets, language switching and metadata on the public frontend in every target locale.

Can you maintain the website after launch?

Yes. We can design an ongoing localisation workflow for new pages, product updates, campaigns and editorial content, with terminology and QA controls that keep later releases consistent.

Next step

Services that can form part of the same project

Tell us about your project

What do you want your content to achieve?

Tell us about the scope, languages and timeline. We’ll respond with a clear proposal.

    Or send us your docs for a quote

    I've read and accept the Disclaimer and Privacy policy

    I consent to receive the information Ontranslation & Interpretation, SLU considers appropriate to send me by email (you can unsubscribe at any time).

    Privacy Overview
    Ontranslation

    This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.

    Strictly Necessary Cookies

    Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.

    Analytics

    This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.

    Keeping this cookie enabled helps us to improve our website.