> 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/advanced-options/keyword-exception-and-exclusions.md).

# Keyword Exception & Exclusions

Keyword exceptions are applied to the search phrase. Matches are replaced with an empty string (removed).

Location: **Advanced Options -> Keyword exceptions** panel

<figure><img src="/files/uAt8VqfIw1zfEoCAeho8" alt="" width="375"><figcaption><p>Keyword Exceptions options</p></figcaption></figure>

### Partial (fuzzy) keyword exceptions

<figure><img src="/files/O0JvJamSZmuM3Mdi3mdP" alt="" width="375"><figcaption></figcaption></figure>

These keywords are removed **anywhere** from the search phrase - including from start, end and middle of the matched words.

#### Example

*Keyword exception - replace anyhwere* is set to: `word1, word2, word3`

* User types in: *"test the**word1 word2** test**word3**tes&#x74;**"***
* Search query becomes: "*test the testtest"*

Notice how every single partial and full occurence of the keywords are removed from the search phrase.

### Full (whole word) keyword exceptions

<figure><img src="/files/JGbtgxFZ96etSDVkP5lj" alt="" width="375"><figcaption><p>Full keyword exceptions</p></figcaption></figure>

These keywords are replaced only if the **full word** is matched within word boundaries. This is best to used with common words like: *in, at, a, the* etc..

#### Example

*Keyword exception - replace anyhwere* is set to: `in, the, area`

* User types in: *"mechanic **in the** paris **area"***
* Search query becomes: "*mechanic paris"*

Notice how the search query became much simpler allowing broader, yet more accurate matches by ignoring certain common keywords.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.ajaxsearchpro.com/advanced-options/keyword-exception-and-exclusions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.