Overview
Spek helps you discover App Store and Google Play keyword opportunities for your app and selected markets. Suggestions arrive with context so you can decide which changes belong in your listing.
Review proposed keywords alongside your current wording. A change can add, replace, or remove a term. Applying a suggestion updates your draft; publishing remains a separate action.
The Keywords list marks additions as New and removals as Removed so you can review what changes.
Relevance
Relevance describes how well a keyword fits what your app offers. When reviewing a suggestion, consider whether someone searching that term would find what they expect in your app.
Opportunity
Opportunity helps you identify keywords worth considering for your listing. Review the available estimates alongside the app and market context before choosing a change.
Estimates support a decision; they do not guarantee a ranking position, download volume, or growth result.
The metrics
Open a proposed value in the review inbox to see its supporting context. The panel shows Keyword, Volume, Relevance and Chance for the displayed terms.
Read these values within the selected storefront. Estimates from different markets or different tools are not directly interchangeable.
Volume
Volume is an estimate of search demand in a storefront. It is not an store-published search count. Use it to compare keyword opportunities, not as a forecast of installs.
Difficulty and chance
Difficulty describes how competitive a keyword is. Chance indicates the estimated ranking opportunity for your app. Both are estimates to help review a suggestion, not promises of a particular position.
Match
Match describes how closely a keyword fits your app. Check that the suggested term accurately represents a feature, benefit, or need your app serves.
Reviewing the keywords field
Apple limits the iOS keywords field to 100 characters. Review the proposed field in the context of your full listing, including the name and subtitle.
You can accept or dismiss the changes you see and continue editing accepted wording in the Editor. Check the final draft before publishing.
Common questions
Why might Spek suggest removing a keyword?
A proposal may recommend updating an existing term. Open the card to review its explanation and decide whether to keep your current wording or apply the change.
Review the proposed change against the complete listing and your product knowledge. Keeping the current term is a valid choice when the suggested replacement is less accurate. Estimates inform that review; they do not remove the need to check what users will expect from the app.
Can I review the context for a suggested keyword?
Yes. Open the proposed value to see its volume, relevance and chance alongside the other displayed terms.
Why can a keyword perform differently across markets?
Search habits, language and competing apps vary across storefronts. Review the evidence for the country you want to reach.
How should I compare two keyword suggestions?
Compare them within the same storefront and start with product relevance. Ask whether a person searching each phrase would find the feature or benefit they expect in your app. Then use the displayed demand and opportunity estimates as supporting context. A higher estimate does not make an inaccurate term appropriate, and two tools may define similarly named metrics differently. Review the full listing before accepting the change so the name, subtitle and other text still communicate a coherent promise to potential users.
What if a suggested keyword describes a feature I do not offer?
Keep that term out of the published listing. Review why the suggestion appears and check whether it has another relevant meaning in the selected language, but do not add a misleading product claim to pursue an estimate. You can dismiss the proposal or edit accepted wording in the Editor. Useful ASO starts with matching a real user need to a real feature. Your team's product knowledge is essential to that decision, particularly for specialized apps or features that are only available to part of your audience.
How do I review a keyword change after publishing?
Record the market, changed fields and approximate release timing, then follow the relevant ranking observations as history builds. Compare like-for-like storefront and keyword data instead of mixing countries or treating a global average as the result of one localized edit. A movement can provide useful search context, but competitors and other market changes can also affect it. Use your own store analytics for install and conversion questions. The ranking chart alone does not prove that a keyword change caused a business outcome.
Should the same keyword plan be used for both app stores?
Treat App Store and Google Play research and listing fields in their own context. A useful audience phrase can inform both reviews, but the stores expose different metadata fields and their search results should not be assumed to match. Apple's private keywords field is specifically an App Store concept; it is not a generic field to look for in every store. Review the selected store, country and language before using any estimate or applying a proposed wording change.