One app, 175 separate review pages
The App Store is split into storefronts, one per country or region. Ratings and reviews belong to the storefront they were written in. When you open your product page from the United States you see US ratings and US reviews only — a five-star review from Türkiye or a one-star crash report from Brazil is not there.
This barely matters while an app is only listed in English and only found in one market. It matters a lot after you localize: translated metadata makes the app rank in new storefronts, those storefronts send downloads, and those users leave reviews — in their own storefront, often in their own language.
Where the rest of your reviews are
- App Store Connect → your app → Ratings and Reviews
- Written reviews from every storefront, with a country filter. This is also where you reply. The App Store Connect API exposes the same reviews, each tagged with its territory.
- Each storefront’s product page
- The public “4.6 · 128 Ratings” figure. It counts star-only ratings, which never appear in App Store Connect’s review list or API, and it is different in every country. Check yours across all storefronts with the ratings by country tool.
So there are two different numbers, and neither is wrong. Written reviews tell you why; storefront ratings tell you how many and what shoppers in that country see before they tap Get.
Why replying is worth ten minutes a week
- The reviewer is notified when you reply, and can edit their review and rating. A one-star “it crashes” answered with “fixed in 2.1, please update” is the most reliable way to recover a rating.
- Replies are public. Prospective users reading a low review see a developer who responded, which reads very differently from silence.
- Apple checks replies before publishing them. A new reply shows as pending for a short while. You can edit or remove it later; each review has one reply.
- Answer in the reviewer’s language when you can. A translated reply to a translated storefront is small effort and rare enough to be noticed.
Getting more ratings in the first place
- Ask at a success moment. Use Apple’s review request API after someone finishes a task, wins a round, or hits a streak — not at launch, and never right after an error. Apple shows the prompt at most three times in 365 days per person, so spend it where the answer is likely to be yes.
- Fix the top complaint before asking again. Read the low reviews across all storefronts first. A prompt shown to people hitting the same bug collects the same one-star review.
- Consider a summary-rating reset only for a release that truly fixes what dragged the rating down. App Store Connect offers it when you submit a version; written reviews stay visible, but the star average starts over — including the good ones.
- Watch ratings per storefront after localizing. A new language that brings downloads but a 2.8 average usually means a translation, pricing, or regional-expectation problem, not a bad app.
A weekly routine that covers every storefront
Open the reviews list in App Store Connect with no country filter, sort by most recent, and answer anything at one or two stars first. Then check the public rating in your top storefronts and note the rating count, so next week you can see how many new ratings arrived and where.
Manifest does this for you: it keeps every written review from every storefront in one inbox, sorted so unanswered low ratings come first, lets you reply from the same screen, and records each storefront’s public rating daily so growth per country is a number rather than a guess. It never calls an AI; reply templates are starting points you edit. See the weekly metrics review for the rest of the checklist.