Listing & naming — audit and name an app

What this module is for

Two questions everyone asks before publishing: is my listing any good? and what should I name my app? This page answers both with data, not opinions. The audit reads the public listings on both stores — free and instant, unlike the App Stores module which goes through billed scans. The naming advisor reads the titles that actually dominate your keywords before proposing anything.

Tab 1 — Listing audit: how it works

• Paste the App Store ID or URL and/or the Google Play package or URL. Fields pre-fill from the project's ASO configuration when one exists.
• The App Store subtitle is optional but useful: no public Apple API exposes it, so if you don't paste it, that criterion is simply skipped.
• Add up to 2 competitors to get the measured gaps. Without competitors you only get the score and the fixes.
• The tool then reads the public listings: title, description, visuals, icon, rating, review count, update date.

How the /100 score is computed

• Each criterion carries a weight: update freshness (15), title ≤ 30 characters (14), at least 5 visuals (14), rating ≥ 4.0 (13), description ≥ 500 characters (12), icon present (9), subtitle filled (8, App Store), preview video (8), rating volume (7).
• An unverifiable criterion is removed from the calculation, never counted as a failure. This is common on Google Play, whose public page does not always expose the rating or the update date: those criteria show in grey marked “not verifiable” and the score is computed on the rest.
• Every failed criterion comes with the precise fix to apply.

The gaps against competitors

• Six metrics are compared to your competitors' average: listing score, number of visuals, average rating, number of ratings, description length, title length.
• The Gap column is red when you are behind, green when ahead. For title length, being *above* the average counts as being behind: overly long titles get truncated in search results.
• Claude then writes three blocks: what's missing (with what competitors do instead and the estimated impact), the actions doable in under an hour, and the ranked priorities with their effort.

Tab 2 — Naming advice: the method

• Enter the brand (e.g. “Marmiton”) and your target keywords, most important first, one per line.
• The tool fetches the real top 10 of the App Store for each of your keywords, then measures across those titles: what percentage contains the keyword, what percentage places it before the brand, the average length, and the most used separators (“:”, “-”, “|”, “,”).
• It also measures the popularity of each of your keywords through store autocomplete.
• Claude relies on those figures — and only those — to rule: brand first or keyword first in your market, not in the abstract.

What the advisor returns

• A recommended title with its data-backed rationale, and one decisive sentence on where the brand belongs.
• Three title options, each labelled by its pattern (brand first, keyword first, brand only), with pros and cons.
• Three subtitles, chosen to cover what the title does not — never to repeat it.
• The matching 100-character iOS keywords field, built without repeating a single word from the title or subtitle: Apple indexes each word once, a repeat is pure waste.
• All lengths are recounted server-side and turn red when over the limit: a language model counts characters poorly, we don't trust it there.
• Finally, the titles that dominate each of your keywords, with their length and review count — so you can judge for yourself.

A concrete example

“Marmiton” or “Marmiton: recipes”? The answer depends on the market. If 80% of the top 10 puts the keyword in its title, a brand-only name gives up a signal every competitor sends. If your brand is already searched for on its own, leading with it protects your brand queries. The tool measures both realities before recommending — and shows you the figures it relies on.