ASO Metadata Hierarchy: Which Fields Drive Rankings vs Conversions
Most ASO advice treats metadata like a checklist. Fill in the title, stuff the keyword field, write a description, move on. That approach misses the most important distinction in app metadata optimization: some fields drive keyword rankings, some fields drive conversion rate, and a small number do both. Mixing up which is which is how you end up ranking for a term that never converts — or optimizing copy so hard for clicks that you drop out of the search results you needed to get those clicks in the first place.
This post maps every metadata field on iOS and Android to its actual job. Use it as a decision framework when you're prioritizing optimization effort.
The Core Distinction: Indexing vs. Convincing
The App Store and Google Play are two separate algorithms, and within each one, the ranking algorithm and the conversion algorithm pull in partially opposite directions.
Ranking is about signal input: what keywords does the store associate with your app, and how strongly? This is a function of where and how often a keyword appears in indexed fields.
Conversion is about persuasion: once someone lands on your product page, do they install? This is a function of your visual assets, social proof (ratings and reviews), and whether your value proposition is immediately legible.
A perfectly ranked app with weak screenshots and a confusing subtitle will have a poor conversion rate. A beautifully designed product page built around the wrong keywords will never get the traffic to convert.
Neither half works without the other. But they require different thinking.
iOS Metadata Fields: What Each One Actually Does
Apple's indexed fields are well-documented, but developers consistently over-invest in the wrong ones.
| Field | Character Limit | Indexed for Search? | Visible to User? | Primary Job |
|---|---|---|---|---|
| App Name | 30 | ✅ Yes (high weight) | ✅ Yes | Rankings + first impression |
| Subtitle | 30 | ✅ Yes (medium weight) | ✅ Yes | Rankings + context |
| Keyword Field | 100 | ✅ Yes | ❌ No | Rankings only |
| Description | 4,000 | ❌ No | ✅ Yes (truncated) | Conversion only |
| Promotional Text | 170 | ❌ No | ✅ Yes | Conversion only |
| In-App Purchase Names | varies | ✅ Yes | ✅ Yes | Rankings + context |
| Developer Name | varies | ✅ Yes (low weight) | ✅ Yes | Minimal |
App Name is the highest-weighted ranking signal Apple has. Getting your primary keyword into the app name — without making it read like spam — is the single highest-ROI move in iOS ASO. A name like "Truck'N: GPS Load Tracker" indexes for GPS, load tracking, and owner-operator terms while still being brand-legible.
Subtitle is the second-highest-weighted indexed field and the most underused. Thirty characters that are visible below the app name in search results. This is prime real estate for a secondary keyword cluster that supports but doesn't repeat your name. Don't duplicate. If your name already has "fitness," don't burn the subtitle on "fitness app."
Keyword Field is indexed but invisible to users. The cardinal rules: no spaces (commas only as separators), no repetition of words already in your name or subtitle, and no competitor brand names (Apple will reject or suppress). This field is purely for extending your keyword footprint with terms that don't fit anywhere visible.
Description does not affect iOS keyword rankings. Apple does not index it for search. Its entire job is conversion — specifically, the first three lines visible before the "more" truncation. Think of those 255-ish visible characters as a product page headline, not a keyword dump.
Promotional Text sits above the description and can be updated at any time without a new app submission. This makes it useful for seasonal messaging, feature announcements, or A/B test experiments. It's not indexed. It's a conversion lever.
If your ASO strategy for iOS needs a professional audit — keyword research, metadata restructuring, and conversion copy — our mobile app marketing services team handles the full stack.
Google Play Metadata Fields: A Different Ruleset
Google Play's indexing works differently because Google's core competency is search. The algorithm is more sophisticated, reads more fields, and even indexes content from your reviews.
| Field | Character Limit | Indexed for Search? | Visible to User? | Primary Job |
|---|---|---|---|---|
| App Title | 30 | ✅ Yes (high weight) | ✅ Yes | Rankings + first impression |
| Short Description | 80 | ✅ Yes (medium weight) | ✅ Yes | Rankings + conversion |
| Long Description | 4,000 | ✅ Yes (lower weight) | ✅ Yes | Rankings + conversion |
| Developer Name | varies | ✅ Yes | ✅ Yes | Minimal |
| App Category | — | ✅ Yes (indirect) | ✅ Yes | Rankings + browse |
| Reviews (content) | — | ✅ Yes (Google reads) | ✅ Yes | Rankings signal |
The most significant difference: Google Play indexes the long description. This means keyword placement in the description matters for rankings, not just conversion. The conventional guidance is to use your primary keyword in the first paragraph and approximately three times total without forcing it. Going beyond that reads as spam to both the algorithm and to users.
The short description does double duty — it's indexed and it's the first text a user reads on your listing. On Google Play, this is the field where you should concentrate the most editing effort because it has to accomplish both ranking and conversion simultaneously.
Reviews are a passive signal. Google observes the language users use when reviewing your app and uses it to inform relevance. You can't control this directly, but you can encourage reviews post-install for high-value keywords by naming features clearly in your onboarding and support flows. If users consistently call your feature a "sleep tracker" in reviews, that term gets associated with your app.
Visual Assets: Pure Conversion, Zero Ranking
Screenshots, preview videos, and the feature graphic on Android are not indexed for keyword search on either platform. They have no direct effect on rankings.
They have enormous effect on conversion.
In our engagements, the first screenshot is typically the highest-leverage single asset on a product page. It needs to communicate the primary use case in under two seconds for a user scrolling search results. Captions on screenshots matter — they should reinforce the value proposition, not describe what the UI is doing ("See your stats" is weaker than "Know exactly where your money goes").
Preview videos autoplay on iOS in search results. If yours doesn't communicate value in the first three seconds, it's working against you. Approximately half of users make an install decision before they finish watching a 15-second preview.
Ratings and reviews occupy a middle position: they're a ranking factor (both stores weight them in their algorithms), and they're a major conversion factor (social proof). A 4.7-star rating with 2,000 reviews outperforms a 4.9 with 50, both algorithmically and psychologically.
The Field Priority Matrix
When you're resource-constrained — which is always — this is the order to work through:
- App Name (both platforms) — highest ranking weight, high conversion visibility. Nail the primary keyword here first.
- Subtitle (iOS) / Short Description (Android) — second-highest indexed field, user-visible. Do this before touching anything else.
- Keyword Field (iOS) — extend coverage with non-overlapping terms. Takes 30 minutes if you've done the keyword research.
- First screenshot — highest-impact conversion asset, no ranking value.
- Long Description (Android) — keyword placement matters for Play rankings; conversion-focused structure matters for iOS.
- Preview video — high effort, high conversion impact when done well.
- Promotional Text (iOS) — conversion only, can be iterated without resubmission.
If you're building keyword research from scratch, the process in A Thorough Guide To Deep Linking And Strategic Marketing has relevant thinking on how users navigate to and through app experiences — which shapes what keywords they actually search.
Common Mistakes That Hurt Both Ranking and Conversion
Duplicating keywords across fields. If "meditation" is in your app name, putting it in the subtitle and keyword field wastes indexable space. Apple and Google don't multiply ranking weight by repetition — they just see redundancy.
Writing the description for the algorithm on iOS. Apple doesn't index it. Every keyword you stuff in there comes at the cost of conversion copy that could have driven an install.
Ignoring localization. Localized metadata is treated as a separate set of fields by both stores. An English-only metadata set leaves ranking and conversion opportunity on the table for every other locale you're distributed in — including international English markets like the UK and Australia, which have meaningfully different search behavior.
Treating the keyword field as a dump. Single-word terms compete with every well-funded app in your category. Long-tail combinations — three words formatted as weightlifting,log,tracker — often have better ranking probability and closer intent match.
Never iterating. Metadata is not a one-time task. Keyword volumes shift, competitors enter, and new feature releases create new ranking opportunities. Treating your metadata as set-and-forget is the fastest way to see organic install volume decay.
FAQ
Does the iOS description affect keyword rankings?
No. Apple does not index the description for search. It is purely a conversion asset. Use it to persuade users who land on your page, not to extend your keyword coverage.
Can I use competitor app names in my keyword field?
No. Both Apple and Google prohibit using competitor brand names in metadata. Apple actively rejects or suppresses apps that do this. It's not worth the risk.
How often should I update my ASO metadata?
Approximately every 60–90 days is a reasonable default, or sooner when you launch a significant new feature, observe a ranking drop, or see a competitor move into your keyword territory. On iOS, you can update Promotional Text at any time without a new submission.
Does having more ratings always help rankings?
Volume matters, but so does recency and rating quality. A steady flow of recent four- and five-star reviews signals an active, healthy app. A large volume of old reviews with recent negative trends can actually depress rankings on Google Play, which weighs recency more explicitly.
Is the Google Play long description worth investing in?
Yes, because it's indexed. Unlike iOS, keyword placement in the long description affects your Play Store rankings. It should be written to convert, but keyword research should inform which terms you use naturally throughout.
Do in-app purchase names matter for ASO?
On iOS, yes — IAP names are indexed and can add keyword coverage for terms related to your purchase items. This is a minor signal but worth optimizing if your primary metadata fields are already well-structured.
Getting the metadata hierarchy right is the difference between an ASO effort that compounds over time and one that spins its wheels. The ranking fields and the conversion assets need separate strategies, separate KPIs, and separate iteration cycles. Conflating them is the most common and most costly mistake we see in app store optimization work.
If you want an audit of where your current metadata is leaving ranking or conversion opportunity behind, the mobile app marketing services team at Semnexus does exactly that — or book a 30-minute call and we'll walk through your specific store listings together.
