App Store Keywords Aren't Google SEO. Here's What Actually Worked

I've spent 16 years in marketing at Samsung, TikTok and Ubisoft. SEO was part of the job. ASO still humbled me. Keywords combine across the name, subtitle and a 100-character field.

13 min read
Large official App Store icon beside the headline App Store keywords aren't Google SEO.

App Store keywords are not Google SEO keywords. You do not paste a full search phrase into a field and hope to rank. You pick the words that define the app, put the most important ones in the name, and let Apple combine them with the subtitle and a 100-character keyword field.

I've spent 16 years in marketing at Samsung, TikTok and Ubisoft. SEO was part of the job. ASO still humbled me. I treated the listing like a landing page I was writing for Google. Big, obvious terms. Calendar. Planner. On the App Store you are not ranking against blogs. You are ranking against apps with 100k reviews.

Search is how most people find apps. Apple says 70% of App Store visitors use search to discover apps, and almost 65% of downloads happen directly after a search. Those figures are from 2022, published on Apple Ads. They are about visitors and downloads, not payments.

I build hora Calendar, a native calendar for Mac, iPhone and iPad that works with Google Calendar. If I do not show up when someone types "Google Calendar" into the App Store, I do not show up. That is the sentence I should have written on a sticky note from the start.

Think in words that combine, not in phrases you paste

Every one of us has some idea of how people find things on the internet. Google trained us to write pages around search phrases. App Store search is a different machine.

Apple will combine single words that already sit in the name, the subtitle and the keyword field. If the name has "Google" and "Calendar", and the keyword field has menu and bar, you can aim for "google calendar menu bar" without pasting that whole phrase into keywords.

The fields Apple lists for text relevance

Apple's own App Store search page says search results are based on text relevance, "matches for your app's title, subtitle, keywords, and primary category", as well as user behavior such as downloads, ratings and reviews. So the indexed text fields, officially, are:

  • The app name, or title.
  • The subtitle.
  • The keyword field.
  • The primary category. Your app is also searchable by company name.

ASO practice treats the name as the strongest field you control, then the subtitle, then the hidden keyword field. Apple does not publish a weighting table. I am not going to invent one. What I can say from the trenches is simpler: if one phrase matters most, it belongs in the name.

The limits are tight. The name is 30 characters. The subtitle is 30. The keyword field is 100 characters on Apple's marketing pages, and "up to 100 bytes" in App Store Connect Help. Separate terms with commas and no spaces after the commas. A space inside a phrase, such as "Real Estate", is allowed and it counts. Do not repeat words from the name, subtitle or category, and do not spend characters on plurals you already included, on category names, or on the word "app". Promotional text, Apple says outright, does not affect search ranking.

What about the description? Apple does not list it among the fields that drive App Store text relevance. Apple does say the description is used for web search-engine results once the app is released, and it tells you not to add unnecessary keywords there to improve search results. Screenshots matter for conversion, but they are not a text-relevance field either.

For a competitive phrase, the name does the heavy lifting

For hora, the phrase that matters is "Google Calendar". It is popular, and it is crowded. Words in the subtitle and the keyword field are indexed too. The name is still the strongest place I control, and for a phrase that competitive it was where I had a real chance.

That is only possible because hora actually uses the Google Calendar API. Google's Workspace Marketplace branding guidelines say you should not use a Google trademark as the name of your own product. There is an exception if your product is compatible with a Google product: you may refer to it with "for", "for use with", or "compatible with" before the mark, including in the title. The documented pattern is "for Google Calendar". Their example is "for Gmail™".

"Works with Google Calendar" is documented as plain-text compatibility language, the kind of sentence you can use in a description. It is not the official formula for an app name. What I shipped in the name is the "for" pattern: App for Google Calendar: hora.

This is not a blank check from Apple. Guideline 2.3.7 says not to pack metadata with trademarked terms or other app names just to game the system. Guideline 5.2.1 says not to use someone else's trademark without permission. A referential name for an app that actually integrates is a different case from stuffing the mark into keywords.

App Review did not make this easy

In September 2026, version 1.1.0 was rejected under guideline 5.2.5 because the subtitle used "Mac" in a way Apple did not accept. The name at that point was hora Calendar for Google.

A few days later, on 23 and 24 September, the same version was rejected under 4.1(c) Copycats. Apple said the name contained another developer's product name, "Google Calendar", and asked me to remove it or provide proof of permission.

I changed the name to hora Calendar and put Works with Google Calendar in the subtitle. I filed a formal appeal to the App Review Board on 25 September, ticket APL591557. That same evening the submission was approved, still under the name hora Calendar. I do not have a written explanation from the Board in email, so I will not pretend I know exactly what convinced them. The listing that shipped afterwards used that subtitle.

Nine days, one formal appeal, and a lot of second-guessing. Later I put "Google Calendar" back into the name, this time as App for Google Calendar: hora. That was a conscious risk. The new name went live with version 3.0.0 on 7 November 2026, on Mac, iPhone and iPad.

How to choose App Store keywords: build the phrase column

This is the part I wish I had understood on day one.

The keyword field is 100 characters, commas included, so it is tight. The job of that field is not to hold finished SEO phrases. It is to hold extra words that can combine with the name and the subtitle. Kickstart's 7-step pipeline is a good way to collect those words. What turned out absolutely necessary, for me, was a table in Google Sheets with one extra column: the phrases that get formed from the words I already have. That column is how I understand how I will rank.

Here is hora's English (US) metadata in version 3.0.0. The name and subtitle are shared by Mac and iOS. The keyword field below is the Mac one.

Name: App for Google Calendar: hora (29 of 30 characters).

Subtitle: Planner, Reminder & Schedule (28 of 30).

Keywords: gcal,widget,menu,bar,alert,agenda,sync,language,natural,work,ai,keyboard,timer,plan,dark,video,adhd (99 of 100).

I do not paste "google calendar menu bar" into that field. I already have "Google" and "Calendar" in the name. I have menu and bar as separate keywords, so they can form "menu bar" with each other and "google calendar menu bar" with the name. The useful words from the name are Google and Calendar, not "App" or "for". Those last two are weak on their own, and Apple already tells you not to spend keyword characters on the word "app".

Words I already havePhrase that can form
Google + Calendar (name)google calendar
Name + Planner (subtitle)google calendar planner
Name + Reminder (subtitle)google calendar reminder
Name + Schedule (subtitle)google calendar schedule
Name + widget (keywords)google calendar widget
Name + menu + bar (keywords)google calendar menu bar
Name + agenda (keywords)google calendar agenda
Name + sync (keywords)google calendar sync
gcal (keywords)gcal
natural + language (keywords)natural language
Phrases that can form from hora's English (US) name, subtitle and Mac keyword field in version 3.0.0. Combinations stay inside one locale.

Once I could see that column, the keyword field stopped feeling like a tiny SEO title tag and started feeling like a box of spare parts. I add a word only when it creates a phrase I actually care about, and only when that word is not already in the name or the subtitle.

Before the name change, Kickstart had hora around #85 in the US on "google calendar", and closer on narrower phrases such as "gcal" at #9. Those are Kickstart observations from late October 2026, not official Apple ranks, and I do not have a matching measurement from after 7 November in front of me.

Ten localizations on the US storefront, not a shared phrase pool

If the US storefront is the one you care about, you have more than the English (US) keyword field. Apple's App Store localizations table lists English (US) as the default language for the United States, plus nine additional languages: Arabic, Chinese (Simplified), Chinese (Traditional), French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico) and Vietnamese. That is ten. English (UK) is not on that list.

Apple writes that table as the languages shown to customers on that storefront, not as a search-index white paper. ASO tools treat those additional languages as also indexed on the US storefront. I filled all ten.

100 characters times 10 locales is 1,000 characters in the keyword field. That is a large pool. It is not one shared phrase-combinator. A word that lives only in English (US) and a word that lives only in Vietnamese will rank as separate words on the US store. They will not form "google calendar menubar" together. Combinations stay inside a single locale.

If I run out of room in English (US), I can put leftover English tokens in another locale's keyword field, mixed with useful local-language words. That is common ASO practice, not something Apple advertises. I keep the visible title and subtitle of those locales localized.

The ASO tools I actually use

I did not need a stack of dashboards as much as I thought. I needed three jobs done, and I ended up with one tool for each.

ToolWhat I use it forUS list price, as of November 2026
Kickstart, by Paul HudsonKeywords, and a double-check that I hadn't forgotten anythingPro is $69.99/year
NorthstarI track positions thereIndie is $10/month; Pro is $220/year; Studio is $550/year
Helm for App Store ConnectMetadata, together with the App Store Connect CLIPro is $9.99/month; the US listing also shows yearly options at $34.99 and $54.99, and Lifetime at $274.99
US list prices checked 10 November 2026. Local App Store pricing varies. These are public prices, not my receipts.

Kickstart is a Mac app by Paul Hudson, from Hacking with Swift. I use it to research keywords and to check I have not dropped a word I care about. Northstar, from Lotus Labs, is where I track positions after a change. Helm for App Store Connect is how I edit live metadata, together with the Helm CLI (helm-asc).

None of those tools replaced the spreadsheet. The phrase column is still how I see the listing the way the search box does.

What the numbers look like now

After the name change, and after version 3.0.0, the App Store Connect overview looks better on reach. App Store Connect does not let me pick this date range. The screenshot runs from early August to mid-November 2026. The percentages are compared with the previous period, as App Store Connect shows them. That window includes the iOS 3.0.0 launch on 7 November, so this is not ASO alone.

App Store Connect overview, from early August to mid-November 2026. First-time downloads 300 (+39.5%), redownloads 98 (+109%), conversion rate 2.23% daily average (−88.3%), impressions 23.4K (+912%), product page views 1.94K (+91.5%), updates 2.66K (+514%)
  • First-time downloads: 300, up 39.5%.
  • Redownloads: 98, up 109%.
  • Conversion rate: 2.23% daily average, down 88.3%.
  • Impressions: 23.4K, up 912%.
  • Product page views: 1.94K, up 91.5%.
  • Updates: 2.66K, up 514%.

The conversion rate falling is not a mystery. Impressions jumped. More people saw the listing, including people who were never going to download. Wider reach often looks like a worse conversion rate. I would rather have that problem than the old one, when almost nobody saw us.

I cannot split those totals into the name change versus the iOS launch. Both sit in the same window.

For context, under the old name, in the 90 days to 25 October 2026, 98.6% of Mac impressions already came from App Store Search: 2,541 of 2,577. Only 79 first-time downloads came from those search impressions, a 3.1% conversion. People could see us. They mostly did not tap. That is why the name and the subtitle, the two lines you read in a search list, mattered more than another word in the keyword field.

If there is one thing I would tell myself last spring, it is this: stop writing App Store keywords as if they were Google titles. Write the words. Build the phrases in a spreadsheet. Spend the name on the one phrase you cannot afford to lose.

Writing the app is still the easier half. Go-to-market is the hard part: screenshots, localization, the listing itself. I would spend as long on those three fields as on any feature.

App Store keywords FAQ

How do I choose App Store keywords?

Start with the words that define the app, not with finished search phrases. Put the most important words in the name, use the subtitle for what the app does, and spend the 100-character keyword field on extra words that are not already in the name, subtitle or category. Then add a spreadsheet column of the phrases those words can form, so you can see how you will rank.

Does Apple index the app description for App Store search?

Apple does not list the description among the fields that drive App Store text relevance. Those fields are the name, subtitle, keywords and primary category. Apple does say the description is used for web search-engine results, and it tells you not to add unnecessary keywords to the description in an attempt to improve search results. Promotional text, Apple says outright, does not affect search ranking.

Do App Store keywords combine across localizations?

No. On the US storefront you have ten relevant localizations, English (US) plus Arabic, Chinese (Simplified), Chinese (Traditional), French, Korean, Portuguese (Brazil), Russian, Spanish (Mexico) and Vietnamese. Extra locales add more keyword slots, not a shared phrase pool. A word stored only in English (US) and a word stored only in Vietnamese will not combine into one phrase.

What ASO tools do you use?

Kickstart, by Paul Hudson, for keywords and a double-check that I haven't forgotten anything. Northstar to track positions. Helm for App Store Connect, together with the Helm CLI, for metadata. The tool that turned out absolutely necessary was a Google Sheets table with a column of the phrases formed from those words.

Can I put Google Calendar in my app name?

Only if the reference is accurate, and even then Apple and Google both have rules. Google's documented title pattern is "for Google Calendar". Their branding-guide example is "for Gmail™". "For use with" and "compatible with" are also allowed. Apple forbids packing trademarks into metadata just to game search, and it can reject a name under 4.1(c). hora uses the Google Calendar API, so a referential name is defensible, not automatic.

If Google Calendar is where your week lives, try hora free for 14 days.

Small print: hora is an independent app that works with Google Calendar. It is not affiliated with, endorsed by, or official from Google. The 14-day free trial on horacal.app (Direct) does not require a card. On the App Store, the 14-day trial comes with the Annual plan only. Plans are $2.99/month, $29.99/year, or $59.99 Lifetime. One purchase covers Mac, iPhone and iPad.

Related stories

Event details lost via CalDAV and EventKit, kept by hora.
Engineering

Why EventKit Isn't Enough for Google Calendar

On macOS, Google Calendar reaches EventKit through CalDAV, and event types, colors, OOO, rooms and Meet get flattened. Why that gap is the reason hora exists.

Maciej Szamowski3 min read
Google Calendar API vs CalDAV: Which Should You Use?
Engineering

Google Calendar CalDAV vs Calendar API: Which Should You Use?

Does Google Calendar support CalDAV? Yes. Compare Google CalDAV with the Calendar API, including sync, OAuth, event data, and multi-provider tradeoffs.

Maciej Szamowski11 min read
Stay in the loop

Want to stay updated?

Subscribe for hora news and updates for Mac, iPhone and iPad.