> 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/skeleton/sections/main-search.md).

# Search page

The results page at `/search`. It shows a search field, a result count, and a grid of results — products render as full product cards (with quick view and badges), while matching pages and blog posts render as simple text cards labeled with their type. 24 results per page with pagination.

The header's magnifying glass opens an inline bar that submits here (with prefix matching, so partial words like "hood" find "hoodie").

**Where to find it:** theme editor → page selector → **Others → Search**.

## Settings

### Section style

* **Top padding** / **Bottom padding** (0–120 px, default 64), **Background color**, **Text color**.

## No blocks

Product cards follow **Theme settings → Product cards**.

💡 **Pro tip:** search quality depends on your product data, not the theme — searches match titles, descriptions, and tags. Tag products with the words customers actually type ("tee" as well as "t-shirt", "crewneck" as well as "sweatshirt") and your search instantly feels smarter.


---

# 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/skeleton/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.