Translation and localisation - Zephyra Studio
Our own site is built for 38 countries and 24 languages - here is exactly how we did it.
What you get
- Text translation that reads naturally to a native speaker, not literal machine output
- Currency and payment method localisation per market
- Hreflang tags so Google knows which version serves which market
- Cultural adaptation of content (examples, references, tone), not just word-for-word translation
- A local contact channel (WhatsApp number, business hours) per market where applicable
- A language goes live only once its translation is actually reviewed, not before
Why Zephyra Studio
This is not a theoretical service for us - we use it ourselves. The site has folder-based i18n routing (/language/path), hreflang tags for every language, and locale-specific currency/WhatsApp numbers per market. No language goes live until its translation is actually reviewed - unreviewed machine translation does not ship, not for us and not for you. For example, the English version of the site is not a translation of the Serbian one - English is the root (the default domain, no prefix in the path), and every other language gets its own prefix. That decision was made because English is the largest market, not a random choice - we make the same kind of decision for your site based on your actual markets.
When this is not the right fit
If you operate exclusively in one market and one language, with no concrete plan to expand into other countries, investing in a full i18n architecture (per-language routing, hreflang, local currencies) is probably not a priority - the focus should be on the core site and SEO for the existing market.
How we work
We decide which languages/markets are the priority, based on where you already have or expect clients
We translate content with a native speaker's review, not just a machine tool with no check
We set up routing, hreflang tags and local data (currency, contact) for each market separately
We check how the content reads to someone who actually belongs to that market, not just whether it is grammatically correct
The language goes live only after review, with more languages added as translations are finished and reviewed
Industries we do this for most
Price and timeline
What drives the price:
- Number of languages and markets
- Amount of content that needs translating
- Whether payment/currency localisation is needed, not just text
- Whether a native speaker is available for review or a translator needs to be engaged
Frequently asked questions
Translation and localisation is more than translating text - currency, payment methods and cultural adaptation have to match the market. Our own site is architecturally built to serve 38 countries and up to 24 languages - English and Serbian are published today, and here is exactly how it works.