Country priority

Market choice is usually made on instinct: “Germany is a big market”, “Brazil is cheap to acquire in”. Those can be right for one category and completely wrong for another. In countries where your rank is actually measured, no guessing is required.

Localization is one of the most expensive things to undo: the text is written, submitted, and a version is waited on. Starting with the wrong country costs a version cycle, not just time.

A storefront's score depends on how many keywords are measured there and how many rival reviews are on file. Producing a confident order from thin data is easy, and that is exactly what makes it dangerous.

In that case rankcusp leaves the score blank and says what is missing: more keywords to track, or more rivals to add in that market.

A phrase can sit at 13 in one storefront and 84 in another. That is not a fault - the whole idea of country priority is hidden inside that gap.

The first cause is competitive density. The number of apps competing for a phrase varies by country. In large markets hundreds have entered it; in smaller ones it may be left to a handful. The same metadata lands in a crowd in one and an opening in the other.

The second is language. The same language being searched differently in different countries is not the exception: local equivalents, everyday usage and brand names all diverge. A phrase that works in one country may not be searched at all in another where the same language is spoken.

The third is the metadata itself. Each country has its own keyword field and most teams fill only a few. A band being empty in a country you left blank is not surprising - no relevance was ever built there.

Phrases are lower-cased before they are stored, and the folding rule depends on the country. In Turkish and Azerbaijani a capital I becomes a dotless ı; everywhere else a dotted i.

What happens if one rule is applied everywhere? A phrase like "AI" becomes "aı" in the Turkish pool and matches nobody searching for it. No error message appears; the phrase sits in the pool, gets measured, gets reported - it is simply the wrong phrase.

The reverse holds too: applying the Turkish rule everywhere splits the same phrase into two separate rows in other countries and divides the measurement.

That is why the function that normalises a phrase always takes the country as a parameter. It looks like a small detail, but it is what determines the pool's unique identity - and applied wrongly, working out which measurement broke is nearly impossible.

Adding a country costs more than adding a phrase, and knowing why shapes your plan.

Each rank measurement is one search request to Apple, and the requests per second are capped. Measurement runs per phrase rather than per row: every app tracking the same phrase in the same country is read out of one search. That is why adding a rival costs nothing.

But adding a country means searching all of your phrases again in that country. Tracking forty phrases in five countries costs the same as two hundred phrases in one - and managing five separate lists takes far more attention.

The practical route: run the loop for a month in the storefront where you get the most downloads, learn how it behaves, then add the second. Starting in ten countries at once ends with measurement in none of them.

When return is measured per country the result surprises most teams: the storefront where you get the most downloads is not the one that returns the most.

The first move in a country whose keyword field was left empty - filling it - is usually the highest-return move there is. The reason is simple: it builds relevance from nothing, and all 100 characters there start being used.

A rank won in a lightly contested country also lasts longer. Holding the same position in a large market takes constant maintenance; in a small one the few apps that get in stay for a long time.

Visibility still has to be read against market size: being first in a small market can reach fewer people than being fiftieth in a large one. The screen puts the two side by side, because neither decides anything alone.

There is a timing difference too: how long a metadata move takes to reach the index varies by country. An effect visible in three days in one storefront can take a week in another - and looking early and writing the move off is a common mistake.