> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/front-office/search-result-pages.md).

# Search result pages

Understanding the different search result page versions depending on the activated bundles

[**Listings search results page (Time-Based rendering type)**](/v2.0/front-office/search-result-pages/listings-search-results-page-time-based-mode.md)

How to use the search results page

[**Listings search results page per category (All rendering types)**](/v2.0/front-office/search-result-pages/listings-search-results-page-per-category-all-rendering-types.md)

Understand the search results page per category

[**Users search results page (User search feature)**](/v2.0/front-office/search-result-pages/users-search-results-page-user-search-feature.md)

Understand the user search results page

[**Listing Alert management (Listing Alert feature)**](/v2.0/front-office/search-result-pages/listing-alert-management-listing-alert-mode.md)

Push an alert to the user when a listing matches the user’s criteria search

[**Listings search results page (RFC rendering type)**](/v2.0/front-office/search-result-pages/listings-search-results-page.md)

The RFC rendering type changes the search process.


---

# 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://features.scnd.com/v2.0/front-office/search-result-pages.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.