> For the complete documentation index, see [llms.txt](https://documentation.ajaxsearchpro.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.ajaxsearchpro.com/getting-started/custom-result-box-position.md).

# Custom result box position

*Custom results position will only work as a "block", thus it won't hover over the desired position, but push it down.*

As you may have seen on the demo page, the results are not always appearing in a "hovering" style under the search bar. In some cases they are placed elswehere on the page.

{% hint style="warning" %}
The results shortcode is **not made** to be used as a custom results page! It is only to position (detach) the **live search** results list away from the search bar, on the **same page**.
{% endhint %}

If you want to place the results somewhere else, you need to place the results box shortcode to the desired position. (the shortcode can be found for each instance on the options panel)

![](https://1706764988-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9jkFgNo4lpUof35gvS%2F-LPVK5wd16qoHtLsdzbZ%2F-LPVKOIIQQhtN4l4dDBz%2Fimage.png?alt=media\&token=391de8c9-d9bd-447a-afd9-207bab6e3068)

Both regular and theme shortcodes are provided.

You can quickly insert this shortcode to a page or post, by using the post editor.

![](http://i.imgur.com/b8ZZPda.png)

After the changes you should see the results appearing on the desired position, pushing down the content below it.


---

# 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://documentation.ajaxsearchpro.com/getting-started/custom-result-box-position.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.