Metadata was written once, at launch
Title, subtitle and description were set on release day and never revisited: store limits, keywords and the What's New field have sat untouched ever since.
ASO starts with a store link, not with access
Paste an App Store or Google Play link — the platform is detected from the URL and the audit reads keywords, competitors, reviews, visuals and metadata. Every score opens up to its inputs, its weights and the source the data came from.
Why the store never surfaces your app
Keywords live in someone's spreadsheet
Rankings get checked by hand and irregularly, so a drop is noticed through the install count rather than through the store results.
Reviews are read at random
The rating slides and the reason stays a guess: nobody counts which topics repeat across a thousand reviews, or in what mood.
Three steps from a link to a fix list
Paste the store link
App Store or Google Play — the platform is detected from the URL. Several links can go in at once and queue up for analysis together.
Run the audit
The pass reads metadata, keywords, competitors, reviews and visuals, and returns scores for visibility, conversion, keywords, visuals and reviews.
Fix in priority order
Issues are sorted by severity with recommendations beside them, and the result exports to JSON, so the next audit shows the difference.
What the ASO module covers
Both stores, several apps
App Store and Google Play in one interface; the iOS and Android builds of the same product are analysed in parallel with shared progress.
Keywords with honest metrics
AI keyword discovery, search popularity, difficulty, chance of ranking and the current position with its change since the previous pull.
Competitors from the store itself
Direct and indirect competitors found in the store, with their category, rating and average score sitting right next to yours.
An audit that ranks the problems
Scores for visibility, conversion, keywords, visuals and reviews, an issue list ordered by severity, recommendations and a JSON export.
Visuals and metadata against store limits
Icon, screenshots, preview video and field completeness: title, subtitle or short description, description and What's New, each against the store's character limit.
Reviews as a source of reasons
Rating distribution, the sentiment split and the topics that keep recurring — instead of scrolling the review feed at random.
In numbers
- 2
- stores in one module: App Store and Google Play
- 6
- audit scores: overall, visibility, conversion, keywords, visuals, reviews
- 0
- App Store Connect or Play Console credentials needed — a public link is enough
Questions about the ASO module
Do I need App Store Connect or Google Play Console access?
No. The analysis starts from the app's public store page, so there is no developer console to connect and no credentials to hand over. Whatever an ordinary store visitor can see, the module reads too.
Can I analyse iOS and Android at the same time?
Yes. Paste several links at once: the platform is detected from each URL, the jobs join one queue, and the progress of every app stays visible on screen while they run.
Where does the ASO score come from?
The score opens up in full: you see the inputs — title and description length, rating, number of ratings, screenshot and localisation counts — the weight of each component, and the data source: official API, page parsing or cache, labelled with its quality.
Are keyword positions tracked?
Yes. Every keyword keeps its current and previous position, the change between them, search popularity, difficulty and chance of ranking. New keywords are found by an AI search that runs in the background while you work in other tabs.
What does the module do with reviews?
It shows the star distribution, the split between positive, neutral and negative reviews, and the topics that repeat inside them. That points at the reason behind the rating, not only at the rating itself.
Start with one link to your app
No credentials and no console exports: the audit starts on the public store page and ends with a list of fixes.