Jump to a section
Leave with a decision
Leave with an output that helps somebody do the next piece of work.
Start with the visual explanation, work through the example, then try the exercise on your app.
Which tool should you open first?
Start with the decision, not the size of the tool dashboard.
Do you know the problem?
Write the question you want the tool output to help answer.
Not yet → diagnose
Use the audit checklist to record evidence and prioritise the question.
Yes → choose the task
Use metadata tools for text, the storyboard for creative, review research for themes or the test planner for hypotheses.
Work through it · fictional example
Pick the tool by the decision you need to make.
The fictional Speak Daily team has a list of keywords, vague screenshots and no agreed test. Buying another dashboard will not connect those pieces.
Why this changes the decision
Use the keyword workbench to record relevance and sources, then transfer the approved ideas into a listing draft. Build a storyboard that proves the same promise. Use the experiment planner to record the proposed change, metric and interpretation rule. Export the work with its assumptions attached.
What to check before calling it a win
Ask whether a teammate can use the export without a meeting to decode it. A tool that counts characters cannot tell you whether the message is persuasive; a clean report cannot create evidence you did not supply.
Choose from the 12 free tools
Your turn · a five-minute start
Make one useful decision for your app.
Choose one unresolved decision and one tool. Write the output you expect before entering data.
What a useful answer looks like
“A prioritized list of three relevant terms with sources” is a usable output. “More insights” is not.
Separate the jobs
An ASO tool may provide market research, rank observations, metadata editing, creative testing or reporting. Those jobs require different evidence and capabilities. Start by naming the decision you cannot currently make. Buying a broader dashboard does not help if the actual problem is an unclear product message or a missing owner for implementation.
Use your consoles as a starting point
Native store consoles provide access to your own app’s reporting and supported workflows. Third-party estimates can add context but should not silently replace measured first-party data. Keep the origin of every metric visible. A public scanner cannot know your hidden iOS keyword field, private conversion results or retained user value without an appropriate data connection.
A useful tool output becomes an action
Do not leave the result stranded in another tab.
Input
Enter relevant, accurate material with its source and context.
Interpret
Read what the tool actually measures and what it cannot tell you.
Decide
Choose one change or investigation supported by the output.
Handover
Save the result, assign an owner and define how you will verify the work.
Evaluate research data with a small trial
Choose a real app, target market and set of questions. Check whether a provider covers the needed storefronts, how observations are dated and what its scores mean. Ask about exports and history retention. A precise-looking number is not necessarily a measured search count. Compare usefulness for your actual workflow rather than ranking tools by the number of features on their pricing pages.
Use utilities for concrete preparation
A metadata checker, keyword-field builder or image checker can catch formatting issues and make drafting easier. These utilities do not decide product relevance or guarantee rankings. The free tools on this site show their limitations and process inputs locally, so you can complete a small task without connecting a store account.
Make a purchase decision you can revisit
Record the problem solved, required coverage, seat needs, recurring cost and exit/export options. Test the workflow before committing to a longer term. Reassess whether the team actually uses the outputs in decisions. This page is a buying framework, not a scored vendor ranking: no hands-on evaluation or price comparison is implied.
Your next steps
- Write the decision the software needs to support.
- Identify whether the required data is measured, observed or estimated.
- Trial the exact store/market workflow and export the result.
- Compare total operating cost and revisit usage before renewal.
Sources and platform guidance
Platform documentation checked 29 September 2026. Verify the applicable console settings before publishing.
Questions and answers
Does this guide rank commercial tools?
No. It provides an evaluation framework and links to practical utilities. A vendor ranking would require a documented hands-on method and dated evidence.
Can a free checker replace an ASO strategy?
It can remove mechanical friction. Strategy still requires deciding which users to serve and which changes the evidence supports.
Work directly with Gabriel
Make your team harder to bullshit.
Use your own app to practise keyword choices, metadata drafts, screenshot briefs and evidence review. Leave with a method your team can repeat after the workshop. The next agency deck should face a tougher audience.
Help me turn tool output into action →Or email gabriel@asoprofessional.com. Bring your app link, market and the decision you need help with.
Want a first opinion? Get a free video teardown of your listing.