> For the complete documentation index, see [llms.txt](https://docs.onside.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onside.io/console/marketing-and-promotion/aso-and-discovery-tips.md).

# ASO & Discovery Tips

Learn how to optimize your app's product page for better visibility, more downloads, and greater success on the Onside Store.

App Store Optimization (ASO) is the process of improving your app's visibility in a marketplace to increase downloads. Onside is a new and growing platform, which means there is less competition and a greater opportunity for your app to stand out.

This guide provides a checklist of best practices to help you succeed.

{% hint style="info" %}
**Your First-Mover Advantage on Onside:** Because our marketplace is growing, effective ASO can have a huge impact. Optimizing your page now gives you a significant advantage in ranking well and being discovered by our expanding user base.
{% endhint %}

***

### Your Onside ASO Checklist

A great product page is crucial for converting views into downloads. Use this checklist to optimize every element of your app's listing.

<details>

<summary><strong>Click here to expand the ASO checklist</strong></summary>

* **1. App Name**
  * Your app's name should be unique, relevant, and easy to remember. While you can include a keyword or two if it feels natural, prioritize brand identity and clarity. (Character limit: 30)
* **2. Subtitle**
  * This is a short phrase that appears under your app's name. Use it to summarize your app's main purpose with strong, compelling keywords. (Character limit: 30)
* **3. Keywords**
  * Choose up to 10 relevant keywords that users might search for to find your app. Think about your app's features, category, and target audience. Research competitors to see what terms they use.
* **4. App Icon**
  * Your icon is your app's first impression. It should be simple, recognizable, and look great at all sizes. Avoid using words in your icon. Remember, this is synced from your App Store Connect listing.
* **5. Screenshots & App Previews (Videos)**
  * Showcase your app's best features in action. The first 1-3 screenshots are the most important. Use them to tell a story and highlight your app's core value proposition. A short video preview is highly effective. These are also synced from App Store Connect.
* **6. Description**
  * The first few lines are the most critical. Start with a compelling sentence that clearly explains what your app does and for whom. Use bullet points or short paragraphs to list key features and benefits, making it easy to read.
* **7. Ratings and Reviews**
  * High ratings and positive reviews significantly impact downloads. While Onside is a new platform, we often sync reviews from the App Store to provide immediate social proof. Encourage your happy users to leave reviews directly on Onside to build your reputation here.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onside.io/console/marketing-and-promotion/aso-and-discovery-tips.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.