> For the complete documentation index, see [llms.txt](https://academy.pakk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pakk.io/ecommerce-launch-mega-checklist/product-discoverability.md).

# Product Discoverability

* Quick global search should allow finding product by keyword from anywhere in site. *Pakk sites have global search by default*.
* Main product navigation menu should have 5-7 links, corresponding to the main sections or departments on your site. *Pakk sites autogenerate the main menu - make sure you have 5-7 parent categories*.
* Don't have an infinitely nested category hierarchy if you can avoid it - 2 to 3 nested levels at most. *Pakk product navigation menu goes shows only 3 levels deep.*
* Product category views (lists of products) should offer useful sorting and filtering (on pertinent product attributes). *Pakk sites implement functional filter bars on category views.*
* Do you allow customer to mark products as favourite or create a Wishlist? *Pakk sites allow this by default*


---

# 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://academy.pakk.io/ecommerce-launch-mega-checklist/product-discoverability.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.