> 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/behavior/results-page-override.md).

# Results page override

```
Search Behavior -> Magnifier and Return Actions
```

### Redirection to results page

Before you start, you might want to enable the magnifier or return buttons to redirect to the results page. [Please read this section](/behavior/return-key-and-magnifier-icon-click-actions.md) on how to do that.

![](https://1706764988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-L9jkFgNo4lpUof35gvS%2Fuploads%2FOAssZmbukJqLi8Cl9Fct%2Fimage.png?alt=media\&token=370f4bdd-76d6-4777-a970-1e0bc0983603)

### Override

This option allows you to display the results from Ajax Search Pro instead of the default WordPress search results on the search results page.

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

{% hint style="warning" %}
**NOTICE:** This option **does not affect** the layout nor the styling of the results page.
{% endhint %}

{% hint style="success" %}

#### The override does not seem to work, even though I enabled it. What do I do?

Under the **Compatibility Options** submenu, click on the **Query Compatibility** panel, and try enabling the "*Do a soft-check only..*" option.
{% endhint %}

![Soft check options, when the override feature does not work](https://1706764988-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9jkFgNo4lpUof35gvS%2F-Ly-iwJ7ty0rZWby4Djq%2F-Ly-knoxx6yyDt1v5R_Z%2Fimage.png?alt=media\&token=acbeeda1-1d39-4125-9bcb-d0ee905313b0)

## Override Method

Some information has to be sent when overriding, so the override handler knows which search instance is the override sent from, what options were selected etc.. and to store that information even when the user paginates through the results page.

There are two ways of doing that:

* **Get** (default) - the search override data is appended to the end of the URL as a query string
* **Post** - the search override data is sent as post data and stored in COOKIES during pagination

It's a matter of your preference, I recommend using the default Get method, as it does not rely on cookies at all.

## Results count per page

This should be set to the same as the number of results originally displayed on the results page!

Most themes use the system option found on the `General Options -> Reading` submenu, which is 10 by default. If you set it differently, or your theme has a different option for that, then **set this option to the same value** as well.


---

# 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/behavior/results-page-override.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.
