App store listings have to satisfy a keyword algorithm and a human who is already half-scrolled past. We write both stores properly, working from the search terms people actually use for apps like yours, and we measure the store listing conversion rate rather than guessing at it.
“We get impressions but few installs.”
That’s a listing conversion problem, and it’s the cheapest thing in acquisition to fix. See the plans
“We wrote the listing once at launch.”
Keyword fields and short descriptions reward iteration. Most apps never touch them again. See the process
“We’re localising to new markets.”
Translating a listing literally loses the keywords. It needs rewriting per market. See the plans
“We need the app itself improved.”
That’s development, not copy. We’ll tell you if that’s the real problem. Read who this isn’t for
These figures cover every Gatilab service, not this one alone. We’d rather say that plainly than imply a per-service record we haven’t published.
Brands we’ve delivered work for
Store listing conversion is measurable in your own console, so this is one of the few places in acquisition where the result is unambiguous within weeks.
For live apps getting store impressions that don’t turn into installs at a reasonable rate.
One app, one language · 1 to 2 weeks
Credited against the full listing package booked within 30 days.
For apps where the screenshots and the copy are currently telling different stories.
One app, one language · 2 to 3 weeks
We measure store conversion before and after, from your own console data.
For apps releasing regularly, testing creatives, or expanding into new language markets.
3-month minimum
If your install volume is too low to test on, we’ll tell you to buy the one-time work.
Two stores with different rules, different character limits, and different indexing. Treating them as one listing is the most common mistake.
Week 1
App store search behaves nothing like web search. Queries are shorter, more branded, and more category-driven. We pull actual store keyword data rather than importing your web SEO keyword list.
You leave with: A keyword set with volume and difficulty, specific to app stores.
Week 1 to 2
Google Play indexes the long description; Apple does not and uses a separate keyword field instead. The same words in the same place would waste one of them, so each store gets its own version.
You leave with: Separate, rule-compliant copy for both stores.
Week 2
The first two lines and the first two screenshots carry most of the decision. Those get the majority of the attention, and the rest supports whoever is still reading.
You leave with: Copy structured so the decision happens above the fold.
Week 3 onward
Store listing conversion rate gets baselined before the change and measured after, from your own console. Play Store experiments let this be tested properly rather than argued about.
You leave with: Before-and-after conversion data from your own console.
This is a narrow service with a real ceiling, and it’s worth saying so. Two of these are reasons we decline.
Something not covered? Ask directly and you’ll get a straight answer, not a calendar link.
Because they index differently. Google Play reads your long description for keywords, so the words have to appear there naturally. Apple ignores the description for search entirely and uses a separate hidden keyword field with a strict character limit. Writing one listing and pasting it into both wastes Apple’s keyword field and usually under-optimises Play.
Store listing conversion rate is what we influence, and that’s measurable in your console within weeks. Meaningful improvements are common when a listing has never been revisited since launch, which is most of them. We won’t quote a percentage before seeing your baseline, because a well-written listing has much less headroom than a neglected one.
Then we’ll tell you, and it’s worth hearing before you spend on acquisition. Better copy on an app with a retention problem increases installs and then increases churn and bad reviews, which costs you ranking. It’s one of the few cases where doing the marketing well makes the outcome worse.
We write new listings per market rather than translating. A literal translation preserves the meaning and loses the keywords, because people in different markets search for the same app with different words and often in a mix of languages. Say which markets and we’ll scope it, working with native speakers where we don’t have the language.
On Google Play, yes, properly. Store listing experiments let you run variants against real traffic and get a real answer. Apple’s tooling is more limited, so there we recommend changing Play first, learning from it, then applying what won. The retainer exists for teams who want to keep doing this.
You can, and the package includes reusable templates so they stop being written from scratch in a hurry. The retainer includes us writing them per release. It sounds minor, but release notes are one of the few places you can talk to existing users inside the store, and almost everyone wastes it on “bug fixes and improvements”.
Share the Play Store or App Store link and your rough impression-to-install rate if you have it. We’ll tell you whether the copy is the constraint or whether something else is, before you pay.
