Lesson 1: App Store ASO Fundamentals · Lesson 1.3

The Fields Apple Actually Uses for Searchability

Focus on the searchable fields Apple names explicitly: app name, subtitle, keywords, and company name.

Why this lesson matters

Most wasted App Store effort comes from over-optimizing fields Apple does not identify as the primary searchable text inputs.

Core idea

Apple explicitly points teams toward app name, subtitle, keywords, and company name for searchability, so these fields should drive metadata architecture.

Real-world example

A language app ignores the publisher name opportunity

A publisher has three language-learning apps, but each one uses unrelated branding and an inconsistent company name. Users never build trust across the portfolio.

Why the example matters

Searchable fields are not only app name and subtitle. Publisher identity can also shape discoverability and trust.

Let's make it clearer

Why searchable-field clarity changes the whole curriculum

Apple explicitly identifying app name, subtitle, keywords, and company name as searchable fields gives the academy a cleaner foundation. Instead of teaching every field as if it were equally important for search discovery, the course can teach a more realistic architecture. Some fields are for discoverability, while others are better treated as interpretation and conversion tools.

This matters because beginners often import Google Play habits or generic “app SEO” thinking into the App Store. That creates bloated descriptions, confused metadata priorities, and unrealistic expectations about what copy changes can actually influence search visibility.

Why company name is more strategic than most teams think

Company name is one of the most under-taught App Store assets because many teams think only at the single-app level. But publisher identity becomes more valuable as a portfolio grows, as trust compounds, and as users begin to recognize the company behind multiple products.

That does not mean the company name should be manipulated aggressively. It means publisher naming, consistency, and brand architecture deserve real strategy rather than being treated as admin housekeeping.

A clear publisher identity can support multi-app trust.

Portfolio strategy should consider how company name and app naming interact.

Company naming decisions are harder to undo later than subtitle experiments.

Why description should usually be taught as conversion copy

Since Apple points explicitly to the main searchable fields elsewhere, the academy should teach description and promotional text mainly as conversion and reassurance tools. That is the more useful teaching model for students because it gives those fields a realistic job instead of inflating them into the center of search strategy.

This is also more practical. When students treat description as conversion support, they write clearer pages, cleaner screenshot narratives, and better promotional updates. When they treat it as a hidden ranking battlefield, they usually produce denser, weaker copy.

Step-by-step framework

Step 1

List the searchable fields Apple names explicitly.

Step 2

Assign a different job to app name, subtitle, and keywords.

Step 3

Review the company name as part of brand discoverability.

Step 4

Teach description as conversion support, not the main indexing lever.

Practical exercise

Rewrite one app’s metadata strategy by labeling name, subtitle, keywords, company name, and description with their intended jobs.

Key takeaways

Apple identifies the main searchable fields clearly.

Company name deserves strategic thought.

Description should usually be taught as conversion support.

Soft transition

Turn metadata theory into a field audit

ASO Miner can help you review app name, subtitle, keyword logic, and competitive context together when you want to move from theory into execution.

Continue within this lesson

Next lesson in the academy

ASO Myths That Waste Time

Remove the assumptions that make teams spend effort on low-leverage or misleading App Store tactics.