> 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/customization/results-layout.md).

# Results Layout

Selecting the right search results layout for your website

You can choose between displaying results in an overlay window or on a standalone search results page.&#x20;

***

### Overlay

Display search results in a pop-up window in the browser that dims everything behind it. This option is ideal if you want users to quickly preview search results without leaving the page they’re on.

<figure><img src="https://592969535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8Uav4TSGmA5CSlyCq4is%2Fuploads%2F9HkSjf0ira21dUaPd2SS%2FGroup%202.png?alt=media&amp;token=12deae07-dd7f-44c4-897e-cf7a6b9258e1" alt="" width="223"><figcaption><p>Sample overlay results window</p></figcaption></figure>

To install AI Search in overlay layout, refer to the [Overlay](https://docs.direqt-search.com/result-layouts/overlay.md) installation guide.

### Search Results Page

Display search results on a dedicated page on your website, e.g., `https://example.com/search`. All search queries will be redirected to your chosen URL, with results displayed inline on the page.&#x20;

<figure><img src="https://592969535-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8Uav4TSGmA5CSlyCq4is%2Fuploads%2F2R0cvev9eZ3miuKqRrSo%2Fimage.png?alt=media&amp;token=a7ec029f-24c7-41a9-b66a-64bb8369603f" alt="" width="563"><figcaption><p>Sample search results page</p></figcaption></figure>

To install AI Search on a dedicated page on your website, refer to the [Search Results Page](https://docs.direqt-search.com/result-layouts/search-results-page.md) guide.


---

# 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/customization/results-layout.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.
