The loop
Spek supports ASO for the App Store and Google Play, working one storefront at a time. For each market you choose, it pulls real store data in that market's own language, works out which keywords are worth competing for there, drafts listing text that uses them, and puts the result in front of you as a proposal.
Every cycle runs in the same order.
- Research. Pull keyword and competitor data for one storefront, from that storefront.
- Draft.Write metadata that targets the keywords worth targeting, within each field's character limit.
- Review. You accept, edit or reject each proposal. Nothing skips this.
- Publish. A separate, deliberate action you take when the draft is ready.
- Measure. Applied keywords are tracked so the next cycle starts from what actually happened.
What you decide
Spek decides what to propose. You decide what goes live. That split is structural rather than a setting you can turn off.
Accepting a metadata proposal updates a Spek draft. It does not publish it. Publishing a listing, submitting an event or a product page, or starting a store test is a separate workflow, governed by what the store currently allows and by your own approval.
What Spek measures
Spek measures keyword rank and the search visibility it derives from rank. When you apply a keyword change, Spek starts tracking those keywords and shows how their positions move over the following days.
That is a real signal, and it is a narrow one. It tells you whether your listing is being found for a term, not how many people then installed the app.
Limits
Being clear about the edges is more useful than a long feature list.
- No install or conversion data. Spek does not ingest store impressions, product page views, downloads or conversion rate.
- No paid search. Apple Search Ads is not connected and its data is not used.
- No store experiment results.Spek can draft a product page test, but it does not read back the store's own result for it.
- No global score. There is no single number for how good your ASO is. Rankings are per storefront, so the work is too.
If a decision needs one of those inputs, it is a decision Spek will not make for you.
Common questions
Is Spek an analytics tool?
Spek includes keyword rank tracking and derived search visibility analytics. Impressions, downloads and conversion are not connected.
Use those search observations alongside the systems that measure your app's business outcomes. Keep the store, market and observation period identifiable, and avoid presenting visibility as a download count. This makes the result useful without implying that Spek measures data outside its connected scope.
Will it change my listing automatically?
No. Every change is a proposal you accept, and publishing is a separate action after that.
What should I use Spek for during a normal ASO review?
Start with a specific app and the markets you want to improve. Use the Agent to prepare keyword and metadata proposals, then review whether the suggested wording describes your actual product and suits the selected language. Accepted text becomes an editable draft. After a separate publishing decision, use ranking observations to follow search presence over time. This gives your team a repeatable way to move from research to a reviewed listing update, while keeping product knowledge, brand decisions and the final approval with the people responsible for the app.
Can I use Spek alongside my existing analytics tools?
Yes. Spek answers questions about keyword rankings and search visibility. Your store console and other analytics tools can answer different questions about installs, conversion, retention or revenue. Keep those sources identifiable when reviewing a release: a ranking change is a search observation, while a download or purchase belongs to another dataset. Compare the same app, market and time period where possible. Seeing two metrics move together is useful context, but it does not establish that one listing edit caused a business result.
Is Spek suitable for a team managing several apps?
A workspace holds your team's connected apps, members, store connections and drafts. Each app has its own markets, competitors and Agent configuration, so a review for one listing does not become a proposal for every app in the portfolio. Check the selected workspace and app before running research or publishing. For separate clients or developer accounts, keep the workspace and credential boundaries clear. Plan allowances determine how many apps a workspace can connect; the current package and credit balance are available in workspace settings.
What should I expect from the first set of proposals?
Expect material to evaluate, rather than an instruction to replace every field. Read the proposed value next to your current listing and check its product accuracy, local wording and brand fit. A proposal can be useful even when you edit it before publishing, and keeping an existing field can be the right decision. A new app or market also needs observed ranking history before a trend is available. Neither accepting a suggestion nor completing a run guarantees a particular ranking, install count or growth outcome.