Field limits
Unicode-aware character counts for the 30-character name and subtitle limits and the 4,000-character description limit.
Select an iOS app to audit its public name, subtitle, description, repetitions, localization signals, screenshots, ratings and update recency. Receive a deterministic list of ASO priorities without exposing private App Store Connect data.
Guest
3 analyses per day
Free account
10 analyses per day
No AI, no private App Store Connect data, and no report URL unless you publish one.
The report separates confirmed public fields from unavailable source data and from localization opportunity signals. It never labels a public storefront comparison as a confirmed private App Store Connect issue.
Unicode-aware character counts for the 30-character name and subtitle limits and the 4,000-character description limit.
Compares visible title, subtitle and description metadata across selected storefronts and reports likely fallback cautiously.
Adds public ratings, screenshot counts, release dates, update recency and binary language support to the priority list.
If an app repeats the same significant term in both its public name and subtitle, the report may recommend reviewing that limited space. It explains that repetition is not automatically a ranking penalty and suggests testing distinct relevant wording only when it remains natural.
The analyzer uses public Apple metadata and storefront pages through the platform's cached gateways. It does not estimate search volume, access unpublished localizations or inspect the private keyword field.
It checks public app name, subtitle, description, repetition, storefront differences, ratings, screenshots, release dates, update recency and binary language signals for an iOS app.
No. The analyzer uses public App Store data only and cannot see the private 100-byte keyword field or unpublished App Store Connect localizations.
No. It means public title and description metadata look similar across the compared storefronts. Only an authorized App Store Connect user can confirm the internal localization setup.
Not automatically. Repetition is shown as a limited-space editorial signal so teams can decide whether distinct relevant wording would communicate more value.
No. Personal results remain in the browser. A crawlable report is created only after a registered user explicitly confirms publication.
Live public Apple data is preferred. Cached data is clearly labeled when Apple temporarily limits or interrupts requests, and individual unavailable storefronts produce a partial report instead of a false result.