> For the complete documentation index, see [llms.txt](https://docs.direqt-search.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.direqt-search.com/result-layouts/search-results-page.md).

# Search Results Page

Installing AI Search on a dedicated search page on your site

This guide will show you how to integrate AI Search onto a dedicated search results page on your site, e.g., `https://example.com/search`. Direqt will automatically redirect user queries to your specified URL and display search results on that page.

***

{% hint style="success" %}
You should now see a search bar and a list of suggested searches on your site's search page.
{% endhint %}

### **(Optional) Using Your Own Search Bar**

If you have an existing search bar on your site you'd like to use in conjunction with your search results page, refer to the guide on [Integrating Your Search Bar with Direqt](https://docs.direqt-search.com/search-bars/integrating-your-search-bar-with-direqt.md).

### **(Optional) Adding Additional Search Bars**

Your search results page will have a Direqt-provided search bar at the top of the page. If you wish to add an additional Direqt search bar to any other location on your site, e.g., your site header, refer to the guide on [Embedding the Direqt Search Bar](https://docs.direqt-search.com/search-bars/embedding-the-direqt-search-bar.md).


---

# 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://docs.direqt-search.com/result-layouts/search-results-page.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.
