One Webflow site for every language Finesta's markets speak.
Finesta's site published in English only, while its markets work in four other languages. We are rolling it out into Estonian, Finnish, Lithuanian and Latvian, with the scope agreed page type by page type before translation started. Lithuanian and Finnish are already live.
- Client
- Finesta
- Sector
- Workforce solutions
- What we did
- Multilingual rollout, Webflow localisation, Content scoping, Legacy URL planning, HubSpot forms
- Built to drive
- Better talent connections.
- Live site
- finestaworks.com
The problem
An English-only site for four markets that work in other languages.
When we started, Finesta's Webflow site published in English only. Its Estonian, Finnish, Lithuanian and Latvian paths all returned a 404. Old Finnish and Estonian pages from an earlier build still showed up in search, pointing people at pages that no longer existed. Nobody had yet decided which parts of the site a translation should cover.
- English only, with every language path returning a 404.
- Old Finnish and Estonian URLs still listed in search results.
- No agreed line between what gets translated and what stays in English.
The solution
English stays the source, and every language follows it.
We kept the English Webflow site as the single source and built the four languages on top of it with Webflow's localisation. Before any translation, each content type got an explicit in or out. That gave the rollout a fixed edge, so nothing half-finished could go live.
Our intervention
What we are delivering.
Most of a language rollout is decisions. We made them first, then built.
- 01
Scope, settled in writing
Blog, landing pages, legal pages, cookie consent and chatbot text were each marked in or out. The final scope covers the core static, service and industry pages.
- 02
Four locales in Webflow
Estonian, Finnish, Lithuanian and Latvian versions of every page in scope. The contact form is localised in each language and still sends enquiries to HubSpot.
- 03
Translation with a reviewer
We reused terminology from Finesta's earlier builds where it still fit. Changed content gets machine-assisted drafts that Finesta's own reviewer approves before anything publishes.
- 04
A plan for old URLs
The Finnish and Estonian pages still listed in search are part of the plan, so they get a destination instead of a 404.
The Stega fix
Decide what moves before anything is translated.
Translation is the easy part of a language rollout. The trouble comes from page types nobody decided on and old URLs nobody remembered.
Every content type gets an in or out
An undecided page type is how half-translated pages reach a live site. We did not start translating until each one had an answer.
English is the only source
Content changes happen once, in English, and the four languages follow. That stops five versions from drifting into five different sites.
Old URLs are part of the job
A previous build left Finnish and Estonian pages in search. We count them as traffic worth keeping and plan where each one should land.
Stega initiatives
What comes next.
The rollout gives Finesta a base in each market. These are the next steps we are working on.
Local calls to action
We are adding market-specific calls to action and jobs links to each language as Finesta supplies them.
Localised legal copy
Legal and cookie pages can stay in English where Finesta approves it. When local versions arrive, we place them in the matching language.
Search checks per language
Next we are watching how Google indexes each new language and whether the old Finnish and Estonian links land where they should.
Toolstack
The tools behind it.
- WebflowThe English source site and its four localised versions.
- HubSpotReceives contact form enquiries from every language.
- Google Search ConsoleIndex checks for the new language pages and the old locale URLs.
- SlackThe shared scope canvas where Finesta confirmed each in or out.