Listing audit
Each field in both stores read against the published limits and rules: name, subtitle, keywords, descriptions, icon, screenshots and category. You receive: the audit, with each finding tied to the limit or guideline it comes from.
App store optimization
We rewrite your App Store and Google Play listings, test the icon and screenshots with each store’s own tools, and report what changed in conversion rate and installs.
Get your store listing reviewWhat we run
App store optimization services start from your live listing and its current conversion rate. We check each field against the store’s published limits, then run the tests each store offers.
Your name, subtitle, keywords, icon and screenshots are checked against Apple’s and Google’s published limits, so a rejection or a wasted field shows up first.
Icon and screenshot changes run in Apple’s product page tests and Google Play’s experiments, and the result sheet shows which version to keep.
Conversion rate and installs are reported store by store and source by source, with each figure read from the console that counted it.
How it’s run
Two ways to treat your store pages. The first keeps the listing changing as the evidence arrives.
| A one-time rewriteAnother way to run it | Tested listingHow we run it | |
|---|---|---|
| Starting point | A keyword list and a rewrite of the text | Your current conversion rate and search terms, read from the store consoles |
| What changes | The text fields, in a single pass | Text written, icon and screenshots tested in turn |
| How a change is judged | Where the app ranks for the chosen keywords | Its result in the store’s own test tool |
| Who sees which page | One listing for all visitors | Custom pages for an ad group or an audience, where the stores allow them |
| The store accounts | Set by whoever opened the accounts | App Store Connect and Play Console in your name, with the role you grant us |
The report names the console screen behind each result, so you can open the same screen and read the same number.
Store rules
Apple’s field limits and guidelines, the tests each store offers, and Google Play’s metadata policy, each with its source.
The app name and the subtitle each stop at 30 characters. The keyword field holds 100 bytes, each keyword must be longer than two characters, and the app and company name stay out of it. Promotional text holds 170 characters and the description 4,000.
Guideline 2.3.7 says not to pack metadata with trademarked terms, popular app names or pricing to game the system, and that Apple may modify inappropriate keywords at any time. Keyword lists are checked against it before they go to you.
Product page optimization compares up to 3 treatments against the original. Apple judges treatments on estimated lift in conversion rate plus checks on how reliable the result is. Tests are not available for custom product pages.
Each custom page can change the screenshots, promotional text and previews, and can be given its own keywords so it can appear in search for them. Each has its own URL for ads and posts, and review can run apart from an app update.
A default graphics experiment tests the icon, feature graphic and screenshots in your default language only. A localized experiment can also test the descriptions, in up to five languages. Both can run on custom store listings.
A title is 30 characters or fewer, with no emoji. Listing text and images cannot signal rank or awards, such as “#1” or “Popular”, and repetitive or unrelated keywords are not allowed. A listing can also carry up to 50 custom versions.
The scope
The listing audit comes first, then the changes and tests that follow from it.
Each field in both stores read against the published limits and rules: name, subtitle, keywords, descriptions, icon, screenshots and category. You receive: the audit, with each finding tied to the limit or guideline it comes from.
Search terms chosen from your market and your own console data, then placed in the fields each store provides. You receive: the draft text for each field with its length, for your approval before it goes into the console.
The order and message of the screenshot set, written for what a first-time visitor needs to know. Design is produced for each size the stores ask for. You receive: the screenshot brief and the finished set, for your approval.
Icon and screenshot variants run in Apple’s product page optimization and Google Play’s store listing experiments. You receive: the test plan, then a result sheet for each finished test.
Custom product pages and custom store listings for an ad group, a keyword or an audience, plus App Store in-app events for launches and seasons. You receive: the page list, with the audience, the link and the approved text for each.
Conversion rate and installs by store and by source, beside the average rating and the reviews that need an answer. You receive: the report as set in the written scope, and reply drafts to approve.
How it runs
You approve each document below before anything changes in your store consoles. The App Store Connect and Play Console accounts stay in your name.
Listing audit
| Field | Now | Limit | Finding |
|---|---|---|---|
| App Store name | Sample Stride (13) | 30 characters | Room for a search term |
| App Store subtitle | Your daily run (14) | 30 characters | Says nothing about plans |
| App Store keywords | 71 bytes | 100 bytes | Repeats the app name |
| Play short description | Track your runs. (16) | 80 characters | 64 characters unused |
| App Store screenshot 1 | Login screen | App in use | Guideline 2.3.3 asks for the app in use |
| Play title | Sample Stride (13) | 30 characters | Room for a search term |
Our stack
The store consoles and the checks around them, with what each tool does and where we use it.
Google Play Console is where a developer manages the listing, runs store listing experiments and creates custom store listings.
We work in your Play Console account with the role you grant, and keep the experiment results beside the listing changes.
Questions
Keep exploring
Search ads in your account, reported as cost per client.
Performance Max, call ads and policy-checked search ads.
Meta ads in your account, judged on booked clients.
Setup, verification and lead disputes for pay-per-lead ads.
One budget across Meta, TikTok, LinkedIn and more.
Posts planned from client questions, measured in calls and bookings.
Articles and guides written from your team’s answers, counted in calls.
Welcome, cart and win-back flows first, reported in revenue per recipient.
Review requests, replies and policy-based flagging.
Start here
Send us your app link. We’ll read the listing, check it against the store’s published limits, and tell you which change to test first.