> 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/autocomplete-and-keyword-suggestions/autocomplete.md).

# Autocomplete

```
Autocomplete & Suggestions -> Autocomplete tab
```

Autocomplete feature will try to help the user finish what is being typed into the search box.

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

## Autocomplete Sources

Currently four different autocomplete sources are supported:

* Google keyword suggestions
* The search statistics database
* Post titles
* Post tags

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

You can multiple sources at the same time. Use the drag-and-drop box to select which sources you would like to use. **The order matters**.

The plugin will go through the selected sources (in order) until a keyword is returned.

## Maximal keyword length & exceptions

The maximal keyword length is definable, to avoid lengthy suggestions. Keywords above the defined length (60 by default) will be ignored.

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

You can type in the keywords you don't want to see as keyword suggestions. Use comma "," as a separator.

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


---

# 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/autocomplete-and-keyword-suggestions/autocomplete.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.