Title, Subtitle, Keyword Field — written for you.

We pull every keyword we have ranked you on, score each by popularity and current rank, then distribute them across the three App Store Connect fields. No repetition, no plurals, no stop words.

1 keywords analyzed in

Title

6 / 30

issues

Visible. Apple counts "&", ":", "-" as 2 chars.

Subtitle

0 / 30

empty

Visible. Same char rules as Title.

Keyword Field

139 / 100

issue tracker,task manager,productivity tool,daily planner,goal setter,habit builder,focus booster,time organizer,work flow,personal growth

issue trackertask managerproductivity tooldaily plannergoal setterhabit builderfocus boostertime organizerwork flowpersonal growth

Invisible to users. Comma-separated, no spaces.

Excluded

Zero Issues: App name contains 'Issues' but is not a keyword to be allocated; it's the app title.
Gryzle LLC: Developer name, excluded per rule 5.
Utilities: Category name, excluded per rule 5.
issues: Already used in Title; no repetition allowed (rule 1).
habit tracker: Plural form 'trackers' avoided; singular 'tracker' used. Also, 'habit' and 'tracker' are kept together as multi-word keyword.
task manager: Kept intact as multi-word keyword; no splitting (rule 2).
productivity tool: Multi-word keyword, kept together.
daily planner: Multi-word keyword, kept together.
goal setter: Multi-word keyword, kept together.
habit builder: Multi-word keyword, kept together.
focus booster: Multi-word keyword, kept together.
time organizer: Multi-word keyword, kept together.
work flow: Multi-word keyword, kept together.
personal growth: Multi-word keyword, kept together.

· Title includes only the core keyword 'issues' for maximum visibility and relevance, placed first due to high popularity and rank.

· Subtitle is empty because no additional high-priority keywords remain after allocating 'issues' to the title.

· Keyword Field uses related, high-value singular, non-repetitive, non-stop words that enhance discoverability without violating any rules.

Want to override the input or test a hypothetical? Use the custom allocator.

Allocating… (~10s on cold call)