A fintech client once launched in Mexico with a homepage headline that, translated literally from English, promised to "take care of your money." In context, it read closer to "we'll keep an eye on your money," which is not what you want from a payments company. Sign-ups were a fraction of forecast until the copy was rewritten by a native marketer. The product was fine. The words were the problem.
Localization means adapting content so it feels native to a specific market. It's rarely the headline item in a launch plan, yet it decides whether new customers trust you. Here are seven pitfalls we see again and again.
1. Translating words instead of meaning
Literal translation preserves the dictionary meaning and loses everything else: tone, humour, persuasion and cultural fit. Slogans, headlines and calls to action are the most vulnerable, because they rely on wordplay and emotional shorthand. For these, brief a transcreation: give the linguist the goal and the feeling, not just the sentence, and let them write something new that does the same job.
2. Hard-coding dates, numbers and currencies
Is 04/07 the fourth of July or the seventh of April? Is 1.500 one and a half, or fifteen hundred? Hard-coded formats confuse users and, in checkout flows, cost real money. Store values in neutral formats and let each locale render them: dates, decimal separators, currencies, phone numbers, addresses and units of measurement.
Customers forgive a typo. They don't forgive a price they can't understand at checkout.Mercy Koech
3. Ignoring text expansion
German and French often run noticeably longer than English, and a two-word English button can become a five-word phrase elsewhere. If your designs only fit English, translated interfaces will truncate, overflow or wrap awkwardly. Design with roughly 30–40% extra space for short UI strings, test with pseudo-localized text, and give translators character limits up front.
4. Sending strings without context
"Book" could be a noun or a verb. "Free" could mean no cost or available. When translators receive a spreadsheet of isolated strings, they guess, and guesses produce errors. Always provide screenshots, character limits and a short note on where each string appears. A shared glossary of product terms prevents five different translations of your core feature name.
5. Forgetting multilingual SEO
Translating a page doesn't mean it will rank. People in different markets search with different words: Spanish speakers in Spain and in Mexico often use different terms for the same product. Research keywords per locale, localize title tags and meta descriptions, use proper hreflang annotations, and give each language its own clean URL structure.
6. Overlooking visuals and cultural cues
Colours, gestures, holidays, names in examples and stock photography all carry cultural meaning. A campaign built around a winter holiday lands strangely in the southern hemisphere, and testimonials featuring only one demographic can make a brand feel foreign. Review visuals, examples and references with the same care as the copy.
7. Treating localization as the last step
The most expensive localization projects are the ones that start a week before launch. When content is written with global audiences in mind from the start, with fewer idioms, clear sentence structure and flexible layouts, translation is faster, cheaper and more accurate. Build localization into your content workflow, not onto the end of it.
A pre-launch localization checklist
- Glossary and style guide approved for each locale.
- Key marketing copy transcreated and reviewed by a native marketer.
- Dates, numbers, currencies and addresses rendered per locale.
- UI tested for text expansion and right-to-left languages where relevant.
- Local keyword research completed; hreflang and metadata in place.
- Imagery, examples and legal copy reviewed for cultural fit.
Localization done well is invisible: customers simply feel the product was made for them. That feeling is worth investing in before the launch announcement goes out, not after the first wave of confused support tickets.