What we do

We build the agreed language version inside your existing website.

Talanum handles the buyer-facing language and the website elements needed for the new version to work as a complete launch, not as a folder of translated text.

Business owner reviewing website and project materials

Included when confirmed

The project can include language, implementation, and QA.

Each project states exactly what is included. The final price is based on the agreed work, not on an undefined promise to translate everything.

01

Buyer-facing content

Headlines, service and product text, buttons, calls to action, trust messages, and supporting explanations are adapted for meaning and natural reading.

02

Brand voice and terminology

Product names, protected terms, slogans, preferred tone, and specialist wording are recorded before production begins.

03

WordPress implementation

The agreed pages, builder content, menus, reusable blocks, forms, links, products, posts, and other supported content types are prepared for the new language.

04

Search and URL fields

Page titles, descriptions, and localized URLs can be included when the website architecture supports them and they are part of the agreed project.

05

Pre-launch QA

Routes, language consistency, links, forms, media, buttons, and buyer paths are checked as part of the agreed delivery.

06

Handover and ownership

The delivered version remains part of the client website. Additional languages, future compatibility work, and new integrations are separate unless included.

Before production

You receive a defined project, not an open-ended estimate.

The review identifies the pages and content types to launch, what should remain unchanged, what can wait, and what technical access or protection is required.

Any material difference between the public scan and the internal inventory is resolved before production begins.

Project definition

  • Included pages and content types
  • Deferred work and exclusions
  • Language and URL policy
  • Technical access requirements

Delivery evidence

  • Review and approval checkpoints
  • Pre-launch QA results
  • Publishing or handover path
  • Post-launch smoke check where included

Define the first launch

Start with the pages and buyer paths the new market needs.

Use the public website check for an initial view, or request a review to confirm the work involved and the final price.