Definition
Listing health is an aggregate read of how complete and well-maintained an app's marketplace listing is across the signals merchants and the marketplace's own quality systems look at: title length, description word count, screenshot count and quality, video presence, last-update freshness, support response rate, and pricing transparency. A listing that scores well on every completeness signal converts marketplace impressions to installs at 2-4x the rate of a listing missing screenshots or with a thin description, even when rating and review count are identical. Most marketplaces don't publish a single listing-health number — instead, each signal feeds the ranking algorithm independently — but the concept is cross-platform: Shopify, Atlassian, WordPress, and Zendesk all reward listings that present a complete, recently-updated, support-responsive picture. AppRanks computes a 0-100 audit score that aggregates these listing-health signals into one number; the audit page surfaces the per-signal breakdown so developers can see which specific gaps are dragging the headline.
Where you see it on AppRanks: Audit page (/audit/{platform}/{slug}) — every check is a listing-health signal.
Why this metric matters
Listing health is the highest-leverage lever a developer can pull because, unlike rating or install velocity, every signal is fully within the developer's control. Fixing a missing screenshot, padding a thin description to the recommended word count, or tightening pricing transparency takes hours of work and typically lifts the audit score and conversion rate immediately. The trade-off is that listing health is necessary but not sufficient: a perfectly-healthy listing in a stagnant category still won't grow without distribution or product investment, and a healthy listing with low rating won't convert. Read listing health as a floor — the minimum bar the listing must clear before other levers matter.
How AppRanks computes it
AppRanks computes listing health as part of the audit score (0-100) on every /audit/{platform}/{slug} page. The underlying rubric splits across categories: title length and keyword presence, description completeness and word count, screenshot count and resolution, video presence, last-update freshness pulled from the marketplace timestamp, and pricing tier visibility. Each check is deterministic (pass/warn/fail) and the weighted average produces the headline number. Refresh cadence is 12-24 hours when the underlying snapshot crawls; an on-demand recompute is available when a developer flags a listing change. The per-check breakdown is visible inline on every audit page so the score is fully auditable.
Use cases
- Pre-launch readiness: run the audit before submitting a major listing update — every warn/fail flagged is a known-fixable conversion drag that's better to address before the marketplace re-indexes.
- Quarterly listing review: scoring the listing every 90 days catches drift (outdated screenshots, stale pricing, fading update freshness) before it shows up in install velocity.
See also: Audit hub — listing-health scoring per app · Audit score — the 0-100 listing-health number · ASO — the parent discipline covering listing health