> 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/general-settings/limits-number-of-results.md).

# Limits (number of results)

Number of results on the live results list as well as the results page

`Search Sources -> Limits`

![](https://1706764988-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-L9jkFgNo4lpUof35gvS%2Fuploads%2F7N8EsvYrcGl7yLgmpAre%2Fimage.png?alt=media\&token=14588b7f-4f9f-41ba-b191-b79a0f236c94)

For each results group there is a separate opion to control the live results list results count, as well as the results count on the search results page.

#### Distribute the posts limit between each post type equally?

When this option is enabled, the number of results (post type results limit) is distributred within the selected post types. For example.: if the limit is set to 10, and you have posts and pages selected, then the plugin will show at most 5 posts and 5 pages as results.

![](https://1706764988-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-L9jkFgNo4lpUof35gvS%2F-MVGcGEIO_OpgQZj0vnb%2F-MVGeFP9KJSuvROhxDso%2Fimage.png?alt=media\&token=76de2841-486d-4dd1-aaae-76838ecf4660)


---

# 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/general-settings/limits-number-of-results.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.