App Keyword Profile

Build a profile

Select an app and country. The run prepares metadata, generates candidate keywords, checks observed rankings and stores a profile snapshot.

• Profiles are storefront-specific.
• Observed rank is separated from modeled difficulty.
• Unavailable keywords remain data gaps rather than invented values.

Use the results

Start with relevant terms where the app already has visibility, then inspect realistic gaps and weak metadata coverage.

• Review strongest observed keywords.
• Compare unranked relevant candidates.
• Open the tracker for terms worth monitoring.
• Use suggestions to broaden the next iteration.

Data statuses

Results identify how their underlying data was produced. Always read the source and update time before making a decision.

• Live: returned by the source during the current request.
• Observed: public source data stored with an observation time.
• Cached: a previous source response shown when live collection is limited.
• Estimated: a modeled score or range, not private Apple-reported performance.
• Exact: authorized first-party data only.
• Beta: provider-dependent coverage that may be incomplete.

Run recovery

Queued and stale runs are processed by the shared ASO job system. A recoverable stale run can resume; a repeatedly failed old run is marked failed instead of remaining active forever.