> For the complete documentation index, see [llms.txt](https://uxsmart.gitbook.io/velare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://uxsmart.gitbook.io/velare/customize-your-pages/search-behavior.md).

# Search behavior

Search is how customers with a specific product in mind find it, and they are usually the closest to buying. These settings control how the search interface opens, how results are laid out, and what customers see before they have typed anything, including suggested keywords and a highlighted product. Getting this right shortens the path from intent to product page, especially on a large catalogue.

### Where to find these settings <a href="#where-to-find-these-settings" id="where-to-find-these-settings"></a>

Go to **Online Store > Themes > Customize > Theme settings > Search behavior**.

<figure><img src="/files/Y9rC5Tyw7jqQVXY4Vgfh" alt=""><figcaption></figcaption></figure>

### Settings <a href="#settings" id="settings"></a>

<table data-search="false"><thead><tr><th>Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>How the search interface opens: as a <strong>popup</strong> over the page, or as a <strong>drawer</strong> sliding in from the side.</td></tr><tr><td><strong>Show results</strong></td><td>How results are grouped. <strong>Tab</strong> separates them by result type (products, collections and so on), while <strong>Default</strong> uses a simpler unified text layout.</td></tr><tr><td><strong>Search placeholder</strong></td><td>The hint text shown inside the empty search bar.</td></tr><tr><td><strong>Popular search</strong></td><td>Suggested keywords that guide customers towards common or trending terms (e.g., t-shirt, dress, black).</td></tr><tr><td><strong>Products recommendation</strong></td><td>A specific product to highlight inside the search area.</td></tr><tr><td><strong>Show product price</strong></td><td>Shows prices directly in the search results, so customers can compare without opening each product.</td></tr></tbody></table>

### What customers see <a href="#what-customers-see" id="what-customers-see"></a>

When a customer taps the search icon, the interface opens as a popup or a drawer depending on the **Type** you chose, and both keep them on the page they were browsing. Before they type anything they already see your popular searches and the recommended product, which gives shoppers who do not know what to look for a place to start. As they type, results appear either grouped into tabs (useful when a query matches products, collections and pages at once) or in a single simple list. Showing prices in the results lets customers rule products in or out without leaving the search panel.

### Related pages <a href="#related-pages" id="related-pages"></a>

* [Search](/velare/customize-your-pages/overlay-group/search.md): the search overlay section itself
* [Product cards](/velare/customize-your-pages/product-cards.md): the card settings applied to products shown in search results
* [Header](/velare/set-up-your-store/header-group/header.md): the search icon customers use to open search
* [Currency format](/velare/set-up-your-store/currency-format.md): how prices are displayed in search results
* [Vélare Intro](/velare/readme.md): overview of the theme and where to start


---

# 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://uxsmart.gitbook.io/velare/customize-your-pages/search-behavior.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.