> For the complete documentation index, see [llms.txt](https://sitesbyseth.gitbook.io/sitesbyseth-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/main-search.md).

# Search page

The `/search` results page: a search field, a result count, and a 4-column grid (2 on mobile). Product results render as full product cards — with quick add, hover images, and badges per your **Theme settings → Product cards** — while pages and articles show as title + short excerpt. Results paginate at 24 per page; an empty search shows "No results found."

This section has **no settings of its own**. Visitors reach it from the search field in the menu drawer (Header section → **Show search in menu**).

💡 Search matches titles, descriptions, and tags. If a product isn't being found by an obvious word ("hoodie"), add that word as a product tag — it also helps the [size finder](/sitesbyseth-docs/showcase/size-finder.md) recognize the product as clothing.


---

# 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://sitesbyseth.gitbook.io/sitesbyseth-docs/showcase/sections/main-search.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.