Yannick
Audit sequence
Diagnose visibility before changing creative
Verify the listing
Check metadata, assets, localizations, ratings, and release state.
Find the bottleneck
Separate discovery, conversion, trust, and retention problems.
Ship one hypothesis
Change one meaningful variable and define the expected result.
App name and subtitle match the strongest search intent.
Keyword field avoids repeats, protected terms, and irrelevant words.
Screenshots explain the product before the user reads the description.
Feature graphic, icon, and preview video match the same visual system.
Store listing is localized with translated screenshots where the market matters.
Ratings, reviews, and conversion data have a clear next action.
1. Metadata audit
Check app name, subtitle, short description, full description, and keywords first. Apple and Google both keep visible metadata tight: Apple app names and subtitles are limited, while Google Play titles and short descriptions have their own character limits. If the main value proposition is not clear in those fields, screenshots have to work too hard.
2. Visual asset audit
Review the first three screenshots, icon, feature graphic, and video together. Google says preview assets help promote apps across Play surfaces, and Apple lets you show up to ten screenshots plus app previews. Your audit question is simple: would a cold user understand the app from the first screenful?
3. Localization audit
A translated description with English screenshots is usually a half-finished localization. Check whether your screenshots, captions, metadata, and screenshots match the market. Google and Apple both support localized store assets, so high-potential markets deserve localized creative, not only translated strings.
4. Experiment audit
Apple's Product Page Optimization supports alternate product pages for testing icons, screenshots, and app previews. Google Play has store listing experiments. If an asset is important enough to debate, it is usually important enough to test with a clean hypothesis.
Score issues by impact, evidence, and effort
A useful audit ends with a ranked backlog, not a page of observations. Prioritize issues that affect the first impression or block trust, then improvements with measurable growth potential, and finally visual polish. Add the evidence behind each item so the team knows whether it came from store data, user feedback, or a design review.
P0
Blocks trust
Broken assets, misleading claims, or missing localization.
P1
Limits growth
Weak search coverage or unclear first screenshots.
P2
Improves polish
Consistency, spacing, and secondary-message refinements.
