Why mistakes cluster in localization
Most errors happen because teams treat localization as a direct text swap. But image text has constraints: space, hierarchy, and visual context. A literal translation can break all three.
Avoiding these mistakes requires process, not just proofreading.
Literal translation without context
The correct word is not always the common one. Use customer language from reviews and search terms.
Example: replace a literal term with what shoppers actually search for in that market.
Broken hierarchy
Longer translations can break layout balance. If the headline loses dominance, the message gets lost.
Adjust spacing to keep a two-level read: headline and detail.
Mixed units
Mixed units cause returns. If text says cm but the image shows inches, trust drops.
Standardize all measurements and icons across all images.
Typography that becomes unreadable
Shrinking type to fit more words kills legibility. Instead, simplify the claim or move details to another slot.
Mobile readability should be the standard for every market.
QA step
Run QA at 200% zoom and check cuts, alignment, and mobile legibility. Check all numbers and units.
Ask a native reviewer to read each image at mobile size.
Metrics to track
Log error types and their frequency across markets. If the same issue repeats, update the checklist.
Review support tickets for confusion and fix the relevant slot.
Quick checklist
Avoid literal translations, preserve hierarchy, standardize units, and keep type readable.
Run native review and mobile QA before launch.