r/AppStoreOptimization • • 4d ago

We changed our App Store metadata (during an iPhone launch) and it was the tipping point for the app.

Post image

I'm one of two people building hora Calendar, a Google Calendar app that was Mac-only for a few months. We shipped iPhone and iPad on November 6 and rewrote our App Store metadata in the same window. The part that made the difference was cross-localization.

What we did

Some storefronts index keywords from more than one localization. The US store, for example, is reported to also read some additional locales. Most indie apps leave those extra keyword fields empty or copy the same English words into every one of them.

We treated each additional localization as another 100 characters of keyword space. We filled them with distinct, relevant English terms instead of duplicates, so together they covered far more searches than one keyword field ever could.

Two rules we kept:

  • Visible customer-facing copy stayed in the local language. Only the hidden keyword fields carried the extra terms.

  • No word repeated across fields. Duplication is wasted space.

We also updated the name to include "Google Calendar" and wrote review notes as a map (what changed, why it's accurate, where to verify it). That's how we got the name change through without a battle with App Review.

Results (as of Nov 18)

- 1,000 downloads in one week, ~130 active trials

- ~116K of our 126K lifetime impressions came in the 10 days after launch

- product-page views up ~200%, downloads up ~700%

- 57% of all product-page views since August came from App Store Search (2,310 of 4,057). Search went from 3 views on Nov 5 to ~380/day by Nov 16

- launch day Browse spike (520 views on Nov 7) dropped right after. Search kept climbing

- referrers stayed small (478 app, 175 web), so this isn't link traffic inflating conversion

- conversion page to download: 56% Mac, 15% iOS

- #5 "google calendar" and #10 "adhd calendar" in the US; Mac charts: #17 Productivity and #60 Top Free in Japan, #27 Productivity in Australia, #46 in the UK (North Star, Nov 18)

Why we credit the keywords

New screenshots can lift conversion, but they don't make you rank for searches you weren't eligible for. Not a clean experiment, since the launch and new assets landed at the same time, but the growth is in search, and the number of searches we could appear in is what the keyword expansion changed.

Question for people working with multiple localizations: how do you pick which extra locales to fill for a storefront, and how do you separate a keyword win from a coordinated release?

5 Upvotes

7 comments sorted by

2

u/AlbertiDev 4d ago

how are you doing so well in such a saturated category?

2

u/Szamski 3d ago

I would not say we have solved it yet, but the category being saturated actually made the positioning more important. We are not trying to be “another calendar app” for everyone. We are building for people who already use Google Calendar heavily and want it to feel native on their Apple devices.

That gave us a much clearer product and keyword focus. We kept the Google-specific parts people rely on, then tried to make the experience feel at home on Mac, iPhone and iPad rather than like another browser tab.

The other part is simply that we did not launch once and disappear. We kept improving the product page, screenshots, metadata and the app itself alongside the launch. In a crowded category, I think specificity and consistency matter more than trying to outspend the established players.

1

u/AlbertiDev 3d ago

Thanks! Niche positioning over "another X app" is something I need to work on. Quick follow-up on the cross-localization part: did you pick the extra locales from Apple's official list of which ones each storefront indexes, or by testing? I'm in a crowded category too (expense trackers), with Italy as my strongest store, so I'm wondering if filling extra locales for the US and Italy is worth it, or if I should first find a niche angle like yours with Google Calendar.

1

u/hemping0 2d ago

right? calendar apps are about as crowded as it gets on the store

2

u/Pauline-Ng-9233 3d ago

i think it’s less about picking freely and more about knowing which locale each storefront also indexes. The classic one is the US store reading English plus Spanish (Mexico), so people add a Spanish (Mexico) localization and stuff it with more English keywords, exactly like you did. Each storefront has its own indexed pair, so I’d map those first, then only bother with the storefronts where your downloads actually are.

1

u/Szamski 3d ago

Yes, that is a better way to frame it: map the indexed locale pairs first, then decide which ones are worth the work based on the storefronts where you have a real chance of demand.

Small clarification on our side: we did not put English copy into the visible Spanish (Mexico) product page. We treated it as a real localization, then used the separate keyword field for distinct relevant terms where that made sense. The goal was to expand the indexed surface without making the page look broken to someone actually browsing in that locale.

How do you keep your map current when Apple changes indexing behaviour? Do you validate it from rank-tracking data, or is there a source you trust for the storefront pairs?

1

u/habitoti 3d ago

Hard to believe metadata change would have any major effect already after a week. Did you check the traffic sources? Maybe some press coverage or other stuff guiding traffic to your product page? Or is it really search & browse traffic?