# Does Showing More Supported Languages Help, Even Half-Finished?

> A listing showing support for 20 languages looks more established than one showing 3. Whether that impression holds up once a user actually switches languages is a different question.


**Key points:**
- A long list of supported languages reads as a sign of an established app, no matter how complete each translation actually is.
- That first impression can fall apart fast, the moment a real user in that language finds a thin or clearly machine-translated page.
- The real trust loss happens in the gap between a language being listed and a language being properly supported.
- Whether to claim a language should rest on real usage and real quality, not just the pull of a bigger number.

A long list of supported languages looks like real investment. Whether that holds up depends entirely on what's actually behind it.

## Why the count works as a first impression

A user scanning a listing and seeing a wide range of supported languages reads that as a signal, often without digging deeper. It suggests an app that's been around, built for a broad audience. That read forms fast, from the count alone, well before anyone switches their device language and checks what's actually there.

| | What it signals at a glance | What it risks |
|---|---|---|
| A long language list | An established, well-built app | A thin experience once checked |
| A short, focused list | A narrower but more careful scope | Less instant appeal to a wide audience |

## Where the trust actually breaks

The good first impression a language count creates is fragile in one specific way. It holds up right until a real user in that language opens the app and finds something that doesn't match the promise. A few translated screens next to untranslated ones. Text that reads like it came straight out of a machine. That gap between the claim and the reality tends to cost more trust than never claiming the language at all.

> **Real-world scenario:** A team added several new languages to their listing's claim after a quick, automated pass over their text, hoping a bigger number alone would widen their appeal. Users who actually used the app in one of those new languages found uneven, clearly machine-translated text through much of the experience. The complaints that followed pointed straight at the mismatch between the promise and the app, a sharper complaint than if that language had never been claimed at all.

## What actually deserves the claim

Whether a language belongs on your list should rest on real use and real quality, not just the pull of a bigger number. A language with a real, sizable user base is worth doing right. One with almost no real use may not be worth claiming at all, if claiming it means doing it badly. The number on its own isn't the win. A number that matches real, usable support is.

## What to actually do about it

1. **Check real usage data before deciding which languages to claim.** A language barely used by anyone isn't worth a claim you can't back up properly.
2. **Don't run a quick automated pass and call a language done.** A half-finished translation tends to cost more trust than skipping the claim entirely.
3. **Check your current claimed languages for real completeness.** A claim made in the past can quietly go stale as your app grows and adds new text.
4. **Treat the count as a result of real quality, not a target on its own.** A smaller, fully done list beats a bigger one that falls apart once checked.

[AppRankr's ASO Inspector](/aso) checks your real listing signals, a useful way to confirm a claim actually matches what you're delivering.

