
Multilingual websites
- Price
- from $9,000
- Timeline
- 2.5–4 months
- Experience
- 100+ projects · 10+ years · 9+ countries
Websites in several languages: one structure, translated URLs and proper search markup
- Figma
- WordPress
- Nuxt
Our usual stack. We bring in other tools when the task or the project calls for it.
A multilingual website is more than translated copy. You need translated URLs, a language switcher that leads to the same page, and markup that tells search engines which version to show in which country.
We build websites where languages live in one structure and editors translate content in a familiar admin.
What we do
- Language structure and translated URLs
- A language switcher that keeps you on the same page
- hreflang markup and a sitemap for every language
- A content translation workflow in the CMS
- Localized forms, dates and currencies
Where multilingual sites go wrong
The language switcher always dumps people on the homepage
We link every page to its translations at the CMS level, so the switcher knows the exact URL of each version and visitors stay where they were.
Search shows the English page to visitors in Germany
We set up hreflang and a separate sitemap per language, then verify the markup in Search Console once the site is live.
Translations travel by email and get pasted in field by field
We set up export for translators in XLIFF or through a service like Lokalise, with import back into the CMS — no copy-paste.
Forms and emails still speak the default language
We localize everything around the copy: date and phone formats, currencies, form error messages and notification emails.
Every language is its own site with its own admin
We merge the versions into one structure with shared templates and a shared media library. Change a block once and it updates everywhere; the copy stays separate.
Who needs a multilingual site
A good fit if
- You sell abroad or work with partners and investors in other countries
- You need more than two languages, or the list will keep growing
- Each version has to rank in search in its own country
- Different people or vendors maintain content in different languages
Not a fit if
- One English page about the company is enough — we'll add it to your current site, no big project
- Each market needs its own product and brand — separate sites are the honest answer
- You only want a machine-translation widget on top of the site — we'll help pick and install one
Languages without duplicates or mix-ups
Translations tied to the source
Every version is linked to its original page, so editors can see which translations went stale after the source changed.Built for international markets
Our clients are in the US, Canada, the UK, Spain and Italy — we know how a site reads in each market, not just how to translate it.Long words don’t break layouts
We test designs against the wordiest languages, so German headlines and Russian buttons fit without manual fixes.Add a language anytime
The structure lets you switch on the next language on the live site instead of starting a new build.
Express website audit
We review your site and within 3 business days send a PDF with up to 10 specific growth points, sorted by priority.
- Load speed and the mobile experience
- Structure, copy and the path to a lead
- Technical SEO and search visibility
- Forms, analytics and conversion tracking
For live websites only. No strings attached: you can make the fixes in-house.
How we work
- 01
Language strategy
1–2 weeksWe decide which languages and regions you need, how URLs work (folders, subdomains or domains) and who owns translations.
You get A map of language versions, URL rules and a content localization plan - 02
Prototypes and design
3–4 weeksWe design one structure for every language and test the layouts with long and short copy so nothing breaks after translation.
You get Figma mockups with a language switcher and variants for long strings - 03
Development
4–6 weeksWe build the site with translated URLs, a language switcher and a CMS where every page is linked to its other-language versions.
You get A staging site where editors see every language version of a page in one place - 04
Content localization
2–3 weeksWe load translations, adapt dates, formats, forms and legal pages for each country, then proofread the layout in every language.
You get Every language version filled in and proofread on the actual pages - 05
Markup and launch
1–2 weeksWe set up hreflang, per-language sitemaps and redirects, test the forms and go live. Bugs found in the first 3 months are fixed under warranty.
You get A live site with verified hreflang markup and a sitemap for each language
What to prepare before adding languages
- A list of languages and markets: which you need now and which later
- Who translates: an in-house translator, an agency, or you need help finding one
- Access to the current site and CMS if we're adding languages to it
- Pages that don't need to exist in every language
- Access to Search Console and any regional webmaster tools
A call and a language map
We talk through your markets and how content is managed today. Then we send a URL scheme for each language, a work plan, a timeline and an estimate.
Related articles
All newsExpanding
into new markets?
Tell us which countries you’re targeting. We’ll plan the language structure, translated URLs and hreflang so each market sees its own version.
As many as you need: the structure doesn’t change when a language is added.
From $9,000. The total depends on the number of languages and markets, how many pages each version needs, connecting your translators or a translation service to the CMS and per-country details like currencies, forms and contacts. We send an exact estimate after a call, once the list of markets is clear.
We connect your translators or a translation service to the CMS. Machine translation can serve as a draft for review.
The website handles it: the switcher never leads to a missing page, and search engines don’t get empty versions.
Positively: each version is indexed separately and shown to users in its own country and language.


