Listings for other marketplaces: localize, don't translate
- You understand why translating and localizing are two different jobs.
- You know the localization workflow: research keywords anew, then write.
- You know which image and compliance elements must change per marketplace.
- You pick the right translation route for your budget.
Your listing runs on amazon.de — and amazon.fr, .it, .es are one click away. The reflex: get the copy translated, done. The result: a grammatically correct listing that neither ranks nor sells. Because buyers in France don't search for the translation of your German keywords — they search their own terms. This lesson shows the difference between translating and localizing. (Whether expansion pays off at all, and how the logistics work, is the Growth track's job — here we cover the listing craft.)
1Why literal translation fails
- Search terms are culture: Germans search “Duschtuch 70x140”, the French “drap de bain”, Italians may use entirely different size conventions. Translated keywords often hit words nobody types there.
- Buying arguments travel badly: OEKO-TEX pulls strongly in Germany, barely known elsewhere; other seals or features matter instead. Your German bullet order isn't automatically the right one.
- Conventions differ: title-length practice, formality (Sie/tu/usted), date and measurement formats, even humor — all market-specific.
Translating means saying the same text in another language. Localizing means offering the same product the way people there actually search for it. The difference is like a joke: translated word for word it's still correct — but nobody laughs. That's why localization starts not with a dictionary but with the question: what does a customer in Lyon type when she needs exactly my product?
The AURELO spice grinder set (€24.99) is heading to France. The literal translation of the main keyword “Gewürzmühle” would be “moulin à épices”. But a look at the search suggestions on amazon.fr shows: the French mostly type “moulin à poivre” (pepper mill) and “moulin à sel” (salt mill) — they search by contents, not by the umbrella term. A title built around “moulin à épices” is grammatically clean — and barely shows up in the searches that actually happen. The local main keyword is often a different concept, not just a different word.
2The 12 Amazon marketplaces at a glance
Relevant for European sellers: Germany, France, Italy, Spain, the Netherlands, Poland, Sweden, Belgium, the UK, Ireland and Turkey — plus the US as the biggest single market. Each has its own language(s), search culture and partly its own mandatory info. The good news: your product and image foundations stay the same — what gets localized is the text and keyword layer plus image overlays.
3The localization workflow
- 1. Research keywords ANEW in the target market — don't translate. Amazon suggestions on .fr/.it/.es, local top-10 titles, research tool set to the target market. Result: a separate keyword map per marketplace.
- 2. Build the title by the local formula: same structure (brand + main keyword + variant + feature), but with the LOCAL main keyword — often a different concept than the German one.
- 3. Adapt bullets culturally: order by local buying motives (read local competitor reviews — review mining works in every language).
- 4. Fill the backend locally: the target country's synonyms and regional terms; the 249-byte rule applies everywhere.
- 5. Translate image overlays: infographic texts, dimension labels, usage steps — German text on images is an instantly visible “not for me” signal abroad.
- 6. Check mandatory info per country: instruction language, country-specific markings, local EPR registrations (France and others run their own systems — details in the Growth track).
4Three translation routes — compared honestly
| Route | When sensible | Risk |
|---|---|---|
| Specialist translator with Amazon experience | Big markets, products needing explanation | Expensive (per listing and market); quality varies — ask for references |
| Raw translation + local keyword research yourself | The budget route with time investment | Without language feel, idioms and conventions stay bumpy |
| AI localization built on local search data | Fast and scalable across many markets | Only as good as the keyword base behind it — pure translation AI isn't enough |
The third route is why Listimo creates listings per marketplace in the local language with local search terms instead of translating — for all 12 marketplaces, from the same product photos. Whichever route you choose: the quality test stays the same.
5Quality control without speaking the language
- Back-translation: have a second tool translate the target text back — nonsense surfaces immediately.
- Test the local search: type your local main keyword on the target marketplace — do products like yours appear? If not, the keyword is wrong.
- The native-speaker quarter hour: a short review (acquaintance, freelancer) catches the three most embarrassing errors — often that's all it takes.
The triple check for the AURELO set's Spanish version: 1. Back-translation — the tool turned “steplessly adjustable” into “sin escalones”, literally “without stairs”; translating it back exposes the blunder immediately. 2. Search test — typing “molinillo de especias” on amazon.es: spice grinders like yours appear, the keyword carries. 3. The native-speaker quarter hour — a Spanish freelancer finds two more wooden phrasings in the bullets. Effort: under €20 and one afternoon — the cheapest insurance against months on the wrong main keyword.
The Google-Translate listing: German keywords translated literally, German image texts kept, German bullet order — and then wondering why amazon.fr sells nothing. A badly localized listing isn't “at least we're present”, it's burned money: it attracts ad clicks without conversion and collects misunderstanding-driven reviews.
- Own keyword map researched in the target market (not translated).
- Title built by formula with the local main keyword.
- Bullets ordered by local buying motives (local reviews read).
- Backend filled with local synonyms.
- All image overlays translated.
- Instructions and mandatory info in the local language settled.
- Back-translation and search test passed.
6Expert insight: Byte budgets in localization
The lesson established: the 249-byte backend rule applies on every marketplace. The expert part hides in the word byte — because Amazon doesn't count characters there. The field is stored in UTF-8, where every accented or special letter costs two bytes instead of one: é, à, ç, ñ, ü, å, ł, ğ. The title, by contrast, is limited in characters (75 since July 2026) — an é costs one of 75 there, but two of 249 in the backend. Two fields, two currencies. Plan France, Poland or Turkey with a character counter and you overrun the backend field without noticing.
| Keyword | Characters | Bytes (UTF-8) |
|---|---|---|
| molinillo de especias (ES) | 21 | 21 |
| młynek do przypraw (PL) | 18 | 19 |
| moulin à poivre (FR) | 15 | 16 |
| Gewürzmühle (DE) | 11 | 13 |
Individually that looks harmless; across a full field it adds up: a French backend with 12 accented letters loses 12 bytes — roughly one complete keyword. And the penalty for overrunning isn't one truncated word: exceed the limit and you risk Amazon not indexing the field at all. The symptom then looks like “backend keywords don't work” — the cause is a handful of invisible accent bytes.
- Visible copy: always the correct spelling. Customers read titles and bullets — dropping accents saves nothing there (character counting) and looks sloppy.
- Backend: test variants instead of doubling. Before entering both “moulin à poivre” AND “moulin a poivre”, run this lesson's search test with the accent-free form on the target marketplace: if it returns the same results, search treats both forms as equal — one entry suffices, and the saved bytes pay for the next real synonym.
- Singular and plural likewise: test per marketplace instead of entering both forms — every doubled form costs budget that another search term then lacks.
- Byte counter, not character counter: the quick check — count characters and add one byte per accented letter. At 240-plus characters with accents you are almost certainly over the limit.
A German backend of 245 characters gets localized word for word into French and refilled to 245 characters. With 13 accented letters that's 258 bytes — field over the limit, in the worst case zero indexing. The listing ranks on .fr for not a single backend term, and the ad data looks as if the market were dead. The fix takes two minutes: cut to around 235 characters and re-check in bytes — you just have to know it's needed.
The first lessons of every track are open to everyone. From here on you just need a free account — no subscription, no costs.
- 2The 12 Amazon marketplaces at a glance
- 3The localization workflow
- 4Three translation routes — compared honestly
- 5Quality control without speaking the language
- 6Expert insight: Byte budgets in localization
- ✓Quiz: 6 questions with instant feedback
- All 41 lessons in 3 tracks — completely free
- Your progress is saved across devices
- Certificate + 100 free Listimo credits per completed track
Check yourself
6 quick questions — one at a time, instant feedback. With a free account your progress is saved.
Frequently asked
Do I have to produce separate images per marketplace?
The image base (product, studio, lifestyle) stays the same — only the text overlays (infographics, dimensions, steps) get swapped per language. Keep your overlays as separate layers and you localize a full gallery in under an hour.
Which language do I use for backend keywords abroad?
The marketplace's local language — with locally researched terms. Add English terms only where buyers demonstrably search in English (search-suggestion test on the target marketplace).
Doesn't Amazon auto-translate listings anyway?
Partly — programs like EFN show machine-translated listings if you provide nothing. That's exactly the opportunity: the automation translates literally and ranks accordingly badly. A properly localized listing beats it clearly — in visibility and conversion.
Check your listing for free against the rules from this lesson — or have Listimo build the whole listing from one product photo: images, copy and A+ content.
Go deeper: the complete guide to optimizing Amazon listings →
Everything in this academy comes from day-to-day selling practice — the same playbook behind Listimo, the tool that turns product photos into complete Amazon listings.