Analysis
ASO Audit Checker
Paste your current title, subtitle, and description. Get an ASO score with actionable recommendations.
Comma-separated, no spaces after commas. Apple combines them.
Live score across 10 weighted checks. Aim for 80+.
- 15ptTitle lengthTitle is required.
- 10ptSubtitle present and within limitsMissing. Subtitles boost App Store ranking.
- 15ptKeywords field used efficientlyMissing. You're leaving free indexing on the table.
- 5ptKeywords formatted correctlyComma-separated, no extra spaces.
- 15ptDescription depthMissing. Descriptions drive conversion.
- 10ptDescription uses structure (bullets, breaks)Add bullets or line breaks to improve scanability.
- 10ptTitle contains a meaningful keywordThe first word in your title carries the most weight.
- 10ptTitle avoids promotional termsClean.
- 5ptDescription avoids US-only referencesWill translate cleanly.
- 5ptHas a clear call-to-actionAdd a closing line like 'Try it free today.'
How it works
Paste, audit, iterate
No upload, no account, no waiting. The audit runs live in your browser as you type.
- 01
Pick your platform
iOS or Android. Limits and checks adapt to each store: the keywords field is iOS-only, and the short description differs.
- 02
Paste your metadata
Title, subtitle, keywords (iOS), and description. Live character counters keep you within store limits.
- 03
Read the live audit
Up to 10 weighted checks across 5 categories run on every keystroke (8 checks on Android, which has no keywords field). No submit button: the score updates as you type.
- 04
Iterate to 80+
Follow each hint to clear warnings. 85+ is excellent, 65 to 84 is good, anything lower has structural problems.
Scoring methodology
How the ASO score works
Five weighted categories. The same inputs the store algorithms use to rank you, and the same fields reviewers check before approving a submission.
Title
25%Length against the 30-character limit, plus the presence of a meaningful keyword. The first words carry the most ranking weight.
Subtitle / Short description
10%Presence and length of the second-most indexed field. 30 chars on the App Store, 80 on Google Play.
Keywords (iOS only)
20%Use of the 100-character budget and correct comma formatting, without wasted spaces.
Description
30%Depth, scannable structure (bullets, breaks), and a clear closing call-to-action.
Overall health
15%Promotional terms ('best', 'free', '#1') that trigger rejections, and US-only references that hurt international ranking.
Why ASO audits matter
Search is where the installs come from
Apple says over 65% of App Store downloads come directly from search. Not ads, not browse, not the Today tab. Your metadata is the input the ranking algorithm reads, and a small set of fields drives the bulk of the result. Getting them right is the highest-leverage free thing you can do as a solo developer.
An audit doesn't guess at keyword volume or simulate a competitor. It catches the structural problems that gate everything else: missing fields, overflowing limits, promotional phrasing, weak descriptions. Fix those first.
Pre-flight before submit
Catch limit overflows and rejection triggers before they cost you an extra review cycle.
Spot the empty fields
An unfilled subtitle or empty keywords field is invisible traffic loss. The audit names them.
Tighten conversion copy
Bullets, breaks, and a CTA in the first lines lift conversion more than any keyword swap.
FAQ
Six questions, answered
A structured review of the metadata on your App Store or Google Play listing (title, subtitle, keywords, description), measured against the inputs the store algorithms actually weight, plus the rejection patterns reviewers flag most often.
Weighted checks run live across five categories: title (25 pts), subtitle (10), keywords (20, iOS only), description (30), and overall health (15). Each check is pass / partial / fail; the partial state gives half credit. On Android, where the keywords field doesn't exist, the remaining checks are re-weighted to 100.
85+ is excellent and means you've covered the structural fundamentals. 65 to 84 is good: you'll rank, but you're leaving some indexing or conversion on the table. Anything below 65 has at least one missing field or limit violation.
For the structural pre-flight (character limits, missing fields, promotional language, formatting), yes. For competitive keyword research, install attribution, and A/B testing of variants in production, no. Use both.
No. The audit runs entirely in your browser. Your metadata never leaves the page. Reload and it's gone.
Before every submission, and again whenever you change any metadata field. Stores re-index on each update, and the cost of an unforced rejection is an extra review cycle of a day or more.
Related tools