|
|
The numbers behind our work Continuous translation work since 2002, with every project recorded in our own system since 2009. The figures below come from those records, not from estimates.
|
▮What we translate
- Corporate websites and brand pages
- Product pages, feature pages, and pricing pages
- Landing pages and campaign microsites
- Signup flows, forms, and transactional messages
- Help centers and technical documentation pages
- Cookie banners, privacy pages, and legal web content
- Case studies, white papers, and downloadable assets (plus web summaries)
▮Let’s localize your site without slowing releases
Tell us:
- your site stack (CMS/framework),
- target markets and languages,
- release rhythm,
- and which pages are which pages are compliance-sensitive vs high-volume.
We'll propose the right workflow, QA level, terminology plan, and delivery format, so you can ship globally with confidence.
▮Questions We Hear Before Every Project
- What does website localization include beyond translation? Website localization goes well beyond replacing source text with target language text. A conversion-ready localized website also requires market-fit messaging, headlines and CTAs adapted for local intent, not copied from the source. It requires SEO localization, search intent by market, metadata, slugs, and internal linking rules aligned with how local users actually search. UX microcopy such as forms, error messages, hints, and onboarding snippets must read naturally in the target language. And compliance-aware language with privacy notices, cookie banners, warranties, and regulated wording must meet local legal expectations. Alafranga builds all of this into the workflow from the first segment,
- Which website content types do you localize? We localize the full range of website content: corporate pages, product and feature pages, pricing pages, landing pages, campaign microsites, signup flows, forms, checkout flows, validation messages, consent notices, cookie banners, help centers, technical documentation pages, case studies, white papers, and downloadable assets. For each content type we apply the appropriate workflow, QA level, and terminology standard.
- How do you handle SEO localization for different markets? SEO localization is not keyword translation but it is keyword research in the target market. We identify how local users search for your product or service, adapt metadata titles and descriptions accordingly, localize URL slugs where appropriate, and align internal linking rules with local search intent. A translated website that ignores local search behaviour will not rank, and will not convert. We build SEO adaptation into the localization workflow from the start, not as a separate step.
- Can you localize our website without disrupting our release cycle? Yes. We work natively with standard CMS and localization file formats such as XLIFF, JSON, HTML, and others and can connect directly to your content management system where integration is available. For teams with regular content updates, we set up shared translation memories and glossaries from the first project, so each subsequent update is faster and more consistent. We propose the right workflow based on your site stack, target markets, and release rhythm.
- Which languages are covered for website localization? We work across 40+ languages including German, French, Italian, Spanish, Dutch, Polish, Romanian, Turkish, Arabic and Greek. For websites launching in several markets at once, we manage all languages through a single point of contact, with one shared glossary and the same QA for every language. Yes. Turkish is our founding language pair, active since 2002. Turkish website localization requires specific knowledge of Turkish search behaviour, which differs significantly from European markets in keyword patterns and user intent. Turkish also has distinct character set requirements including dotted and dotless i variants that must be handled correctly across all metadata, URL slugs, and on-page content. We deliver Turkish website localization with SEO adaptation built in and terminology governance applied from the first segment.
|
We work in Trados and memoQ, or in the client's own translation system, with client-specific translation memories and glossaries maintained across every project. AI drafts are produced with the whole document in view, not sentence by sentence through a machine translation API, so terminology, cross-references and tone hold from the first page to the last. We are not tied to one model: we test models on your own sample files. A named specialist reviews and approves every output. → How we manage projects |
