14 ASO Mistakes That Keep Your App Invisible (and How to Fix Them)
Avoid the ASO mistakes that bury apps in search, from keyword stuffing and wasted characters to untranslated listings, stale screenshots and untested changes.
ScreenShipper team · · 8 min read
TL;DR: Most apps that stay invisible in search make the same few ASO mistakes: stuffing or wasting metadata characters, chasing keywords they cannot win, shipping screenshots that are outdated or say nothing at thumbnail size, leaving every market in English, and changing several things at once without measuring. Each one is fixable in your next release, and the table below shows the quick fix for all fourteen.
The 14 ASO Mistakes at a Glance
| # | Mistake | Quick fix |
|---|---|---|
| 1 | Stuffing keywords into the app name or subtitle | Brand plus one natural phrase |
| 2 | Wasting characters in the keywords field | No spaces, no repeats, no duplicates |
| 3 | Using competitor names as keywords | Describe what your app does instead |
| 4 | Targeting only broad head terms | Add specific long-tail phrases you can win |
| 5 | Treating the description the same on both stores | People-first on iOS, keyword-aware on Google Play |
| 6 | Never updating screenshots | Refresh when your UI or message changes |
| 7 | A first screenshot that says nothing at thumbnail size | One big benefit headline |
| 8 | Misleading visuals | Show the real app in use |
| 9 | An icon that blends in with competitors | Distinct silhouette and color |
| 10 | One English listing for every market | Localize metadata for your top markets |
| 11 | Translating words instead of researching them | Local keyword research and localized screenshots |
| 12 | Changing everything in one release | One variable at a time against a baseline |
| 13 | Ignoring ratings and reviews | System prompt at success moments, reply to reviews |
| 14 | Not testing, or calling tests too early | Native A/B tests with enough traffic |
If you need the fundamentals behind these fixes, start with App Store Optimization (ASO): The Complete Guide.
Metadata Mistakes
1. Stuffing keywords into the app name or subtitle
"Budget App Money Tracker Expense Finance Planner" tells nobody what makes your app different, and App Store Review Guideline 2.3.7 explicitly warns against packing metadata with irrelevant phrases just to game the system. Compare it with "YourApp: Budget Planner" plus a subtitle like "Track spending, hit savings goals". The second version still covers budget, planner, spending and savings, and it reads like a product.
2. Wasting characters in the keywords field
The App Store keywords field holds 100 characters, and small habits eat it quickly:
- Spaces after commas:
budget, money, savingswastes two characters thatbudget,money,savingskeeps. - Words already in your app name, subtitle or category, which Apple tells you not to repeat.
- Plurals of words you already use. Apple says "budget" and "budgets" count as duplicates.
- Generic and filler words such as "app", "game", "the" or "to", which Apple also advises against.
More rules and examples are in App Store Keywords Field: 100 Characters Best Practices.
3. Using competitor names as keywords
Guideline 2.3.7 also prohibits using trademarked terms and popular app names in your metadata, and Apple's search guidance lists competing app names among the keywords not to include, noting that improper keyword use is a common reason for rejection. Besides the rejection risk, competitor-name traffic rarely converts: people searching a brand want that brand.
4. Targeting only broad head terms
A new or small app competing for "photo editor" is up against apps with years of downloads and ratings, which Apple lists among its search factors. Mix in specific phrases like "photo collage maker" or "retouch portraits" where the top results are weaker and the intent matches your app.
5. Treating the description the same on both stores
On iOS, Apple's search guidance does not list the description as a text relevance factor, so writing it as a keyword list only hurts conversion. The same goes for promotional text, which Apple says does not affect search ranking at all. On Google Play, there is no keywords field and the full description is used for search, so ignoring keywords there is the opposite mistake. See How App Store Search Ranking Works for the details.
Visual and Conversion Mistakes
Metadata gets you into search results. Your icon and screenshots decide whether anyone taps.
6. Never updating screenshots
Screenshots that show an old interface, retired features or a device style from years ago signal an abandoned app. They can also confuse people who install and see a different UI. Refresh your screenshots whenever your interface or core message changes, and review them at least with every major release.
7. A first screenshot that says nothing at thumbnail size
Search results show only your first three portrait screenshots, or the first landscape one, at a small size. A raw UI capture, a logo splash or a 14-word headline all fail at that size. Use one short benefit headline per screenshot, set in large type, and lead with the reason people should care. 17 App Store Screenshot Mistakes That Hurt Downloads goes deeper on design errors.
8. Misleading visuals
Guideline 2.3.3 says screenshots should show the app in use, not merely title art, a login page or a splash screen. Google Play's metadata policy likewise prohibits misleading store listing content. Features that are not in the app, invented ratings or fake awards risk rejection and produce angry reviews from people who feel misled.
9. An icon that blends in with competitors
Search for your main keyword and look at the icons around yours. If every app in the category uses a blue gradient and a white glyph, yours should not. A distinct shape and color makes your result easier to spot and easier to remember.
Localization Mistakes
10. One English listing for every market
If you only provide English metadata, people searching in their own language in markets like Germany, Japan or Brazil may never see your app. Localizing the name, subtitle, keywords field and screenshot headlines for a handful of markets where you already get impressions opens up new keyword space with little extra development work.
11. Translating words instead of researching them
A literal translation of your English keywords often misses how people actually search. Research local terms for each market, check that translated headlines fit (German text, for example, often runs longer than English), and translate the screenshot text too. A localized subtitle above English-only screenshots looks unfinished. How to Localize App Store Screenshots for Every Market covers the workflow.
Process and Measurement Mistakes
12. Changing everything in one release
If you ship a new subtitle, new keywords, new screenshots and a new icon at once, you will not know which change helped or hurt. Record your baseline in App Store Connect Analytics, filtered by the App Store search source, then change one group of elements per release.
13. Ignoring ratings and reviews
Apple names the number and quality of ratings and reviews as a search factor, and ratings appear next to every search result. Use the system review prompt after a success moment (Guideline 5.6.1 requires the provided API), never offer rewards for ratings, and reply to reviews, especially critical ones.
14. Not testing, or calling tests too early
Product Page Optimization lets you test up to three treatments of your icon, screenshots and app previews against your original, and Google Play offers store listing experiments. The mistake is either never using them or stopping after a few days because one variant looks ahead. Wait for the confidence indicators the stores provide. See Product Page Optimization (PPO).
How to Audit Your Listing in 30 Minutes
- Open your listing on a phone in each of your top three markets and read it as a stranger.
- Count characters in your name, subtitle and keywords field, and list every repeated word.
- Search your five main keywords and screenshot the results. Note where your icon and first screenshot stand out or disappear.
- Compare your screenshots with your current app. Flag anything outdated.
- Check which markets bring impressions but have no localized metadata.
- Write down your current conversion rate and pick one change for the next release.
Frequently Asked Questions
Why is my app not showing up in App Store search?
Common reasons are missing keywords in the name, subtitle or keywords field, very high competition for the terms you target, or a recent release that is still being indexed. Search your exact app name first; if it appears, the issue is relevance or competition rather than indexing.
Can ASO mistakes get my app rejected?
Some can. Keyword stuffing, competitor trademarks in metadata and screenshots that do not show the real app all touch App Store Review Guideline 2.3, which covers accurate metadata.
How often should I update my ASO?
Review keywords and screenshots with every significant release, and whenever conversion drops. On iOS, most metadata changes go out with a new app version; promotional text can change anytime.
Is it a mistake to use the same screenshots on the App Store and Google Play?
Using the same design is fine and keeps your brand consistent, but export each store's sizes and check its rules. Google Play rejects images with an alpha channel and has its own size ratios.
Sources
Your screenshots are your biggest conversion lever
Make test variants for product page optimization and custom product pages in minutes, in every size and language.