Short answer: translate meaning, respect limits, prove pixels

The costliest App Store localization mistakes are literal keyword translation, English-only screenshots, names that break the 30-character cap, funding too many locales too early, and skipping native review. Fix them by researching keywords per market, re-rendering screenshots per locale, drafting short names with headroom, starting with three locales, and paying a native speaker for one review hour.

Translating keywords word for word

A literal translation of your English keywords feels thorough and ranks for nothing. Shoppers type slang, abbreviations, and local genre words that dictionaries never list, so a textbook equivalent can sit in your 100-character field with zero searches behind it while the term buyers use sits outside. SensorTower's keyword team flags exactly this failure: Google Translate picks terms no shopper types, which burns the whole invisible budget on silence. AppTweak's complete guide to app store localization lists direct translation without cultural adaptation among the common mistakes in ASO localization, and AppFollow's 2026 playbook prescribes the standard fix: machine-draft candidate terms, then hand the list to a native speaker who swaps in slang and regional vocabulary. Since the keyword field never shows on the product page, nobody reports the damage, and the mistake can sit for months while you'll blame the market instead of the terms.

The fix runs as a small separate workflow. Draft your English core terms from words buyers use, not your internal feature names. Machine-translate them into candidates, then pay a native speaker for one focused hour to mark which candidates carry demand and add the slang you missed. Fill the field with survivors, keep it at 100 characters with no wasted space, and revisit it after six weeks of per-locale impressions. Our keyword-field guide walks the full routine step by step.

Watch for false friends while you review. A word that looks right but means something adjacent can pull the wrong shoppers and sink conversion even when it carries search volume. The reviewer earns that fee twice here: once for demand, once for meaning.

The screenshot mistake: leaving English pixels in place

Teams translate every string in App Store Connect and ship screenshots that still speak English. Captions, price badges, and dates in images keep selling to the wrong market because translation tools process text while a screenshot is a picture of text. Shoppers read images before they read a word of copy, so untranslated screenshots sit at the top of the damage list. AppTweak's guide makes the same point from the ASO side: localization means adapting messaging and visuals together, and text-only passes leave the highest-impact surface untouched.

The fix is re-rendering, not cropping. Write fresh captions in the new language, reflow the layout so longer words fit, and export at store sizes: iPhone 14 Plus 1284x2778 and iPad Pro 12.9-inch 2048x2732. Proof each caption at full size for spill, check that prices and dates use local formats, and confirm no English words survive in badges. Our screenshot-tools buyer guide compares the three ways teams produce localized shots, and our publish walkthrough covers the upload path once exports look right.

  • Captions rewritten per locale, not translated in place.
  • Prices, dates, and units in local formats.
  • Layout reflowed for longer words before export.

The limits mistake: names that break 30 characters

Thirty characters is generous in English and tight in German, Finnish, or French. A name that fits at home spills abroad, and the store truncates it mid-word on the product page. A cut-off name reads as carelessness before a single screenshot loads, and stuffing three head terms into the space fails review or looks like spam. The subtitle has the same cap and the same failure mode, since teams push exploratory phrases there without counting.

Draft with headroom. Keep the English name near 22 to 24 characters when German, French, or Spanish will expand it. Count after localization with the same rules App Store Connect uses, keep the brand token stable across locales, and localize the descriptive half only. Read each result aloud with a native speaker: would someone say this when recommending the app? Our name guide and subtitle guide cover each field's limits, review risks, and ASO tradeoffs in full.

Localizing ten locales before one pays

AppTweak names two budget mistakes in one line: launching too early and wasting budget on low-opportunity markets. Teams fund twenty locales on day one, spread review money across all of them, and end up with twenty thin listings instead of three strong ones. VerboLabs' 2026 mistakes roundup adds the planning side: unrealistic launch timelines turn localization into a rush task, and rushed tasks skip every check this guide describes. Small catalogs feel this hardest, since one wasted locale is a visible share of the budget.

Start with three locales your data already points to, or pick one long language, one mirrored script, and one character script to stress-test your flow. Read installs per page view by market after six weeks, then fund the next wave where the line moves. Our strategy guide shows how to sequence waves by revenue, our cost guide runs the per-locale math with screenshots included, and our worth-it guide helps you decide whether the next market deserves funding at all.

Treating App Store Connect as one flat form

App Store Connect splits fields across two levels: some strings live at the app level and some ride with each version you submit. Teams that treat the form as one flat page translate the wrong layer, then wonder why a locale shows stale text after release. App-level fields persist across versions while version-level fields need fresh words with every submission, so release notes and descriptions follow different rhythms. Missing that split means shipping a version whose listing mixes new English with old translations.

Map every field to its level before you write a word. Keep a sheet where each locale row shows name, subtitle, keywords, description, screenshots, and release-notes status, then upload one locale at a time and confirm each shows the right text before you submit. Our Connect setup guide walks the screens and the two-level model, and our release-notes guide covers the version-level layer that changes most often.

Shipping without a native review pass

Machine output plus zero review is the mistake inside most other mistakes. Raw translation drafts a listing in seconds, and every shortcut after that compounds: dead keywords nobody checks, names nobody counts, screenshots nobody proofs. AppTweak's guide closes on the same lesson with different words: run localization quality assurance with native reviewers, or confusing copy ships to shoppers you paid to reach. One paid hour per locale catches what machines miss, and the order matters when the budget is tight.

  1. Keywords first, by a native speaker, for demand and false friends.
  2. Name and subtitle second, counted against the 30-character caps.
  3. Screenshots third, proofed on device for spill and leftover English.
  4. Description fourth, skimmed against the source for flipped meaning.
  5. Connect upload last, one locale at a time with levels confirmed.

Our machine-translation guide details this pass field by field, and our one-afternoon listing guide folds it into a single sitting from draft to upload.

How App Store Localizer fits a fix-first workflow

App Store Localizer (https://asolocalization.com) fits the draft stage of a fix-first workflow. Paste a public App Store URL. The tool pulls your title, description, icon, and screenshots through Apple's public lookup API. It translates the title, subtitle, description, and the 100-character keyword field per target locale. It drafts localized keywords from free heuristics over your listing. It re-renders your screenshots with translated captions in iPhone 14 Plus 1284x2778 and iPad Pro 12.9-inch 2048x2732 sizes. Coverage runs to 20-plus target locales, from Japanese, Korean, and both Chinese scripts through German, French, Spanish, and Brazilian Portuguese down to Hindi, Thai, and Vietnamese. You download the finished assets or publish straight to App Store Connect.

Prices are one-time per listing, which keeps the fix-first math friendly. Starter at $19.99 covers 3 languages with each available screenshot. Global at $99.99 covers all supported languages. No subscription, no per-seat fees. Two honest limits hold. Output is machine-generated, so run the native review pass from this guide on your top locales before you ship, starting with keywords, name, and screenshots. Keyword ideas come from listing heuristics rather than paid search-volume data, so confirm your top market's terms with a native speaker. The tool serves the store listing only, never app screens or code.

Frequently asked questions

  • What are the common mistakes in ASO localization? The frequent ones are literal keyword translation with no demand check, English-only screenshots, names that break character limits, funding low-opportunity markets too early, and skipping native review. Each has a cheap fix when you catch it before upload.
  • Does machine translation hurt App Store rankings? Raw output hurts through the keyword field: translated terms that match no demand waste all 100 characters invisibly. Draft by machine, then finalize terms with a native speaker and recheck after six weeks of per-locale impressions.
  • Should I localize screenshots or just text? Localize both, screenshots first if money is tight. Shoppers read images before copy, so English captions under a German description convert poorly. Re-render captions per locale and export at store sizes.
  • How many locales should an indie app start with? Three, picked from data or chosen to stress-test your flow across a long language, a mirrored script, and a character script. Measure installs per page view per market after six weeks, then fund the next wave where the line moves.
  • Will Apple reject my app over a bad translation? Poor translation quality isn't a published rejection reason, and clumsy listings routinely pass review. The risk is conversion, not approval: a listing that passes review can still read as careless in every storefront it touches.

Paste your App Store URL at https://asolocalization.com today and draft your first three locales this afternoon. Then work this guide's fixes in order: keywords, screenshots, limits, levels, review. Ship the listing, read installs per page view by market in six weeks, and fund the next wave only where the numbers earn it.