> 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.pakk.io/ecommerce-launch-mega-checklist/product-discoverability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.