> For the complete documentation index, see [llms.txt](https://docs.direqt-search.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.direqt-search.com/managing-results/synonyms.md).

# Synonyms

Handling synonyms and acronyms in your search results

Synonyms allow you to define equivalent terms in your content to accommodate alternate ways people might describe an item or concept. Adding synonyms to your search engine's knowledge base helps improve relevance and content discoverability.

### How to Use Synonyms

#### Adding Synonyms

1. Go to the **Synonyms** page in the [dashboard](https://dashboard.direqt.ai/login).
2. Enter the terms you want to associate with each other.
3. Click "Save".&#x20;

#### Deleting Synonyms

Click on the "X" button next to the pair of terms. Removing a synonym mapping will revert search behavior to its original state.

### Examples

#### Formal vs. Informal Language

Many users search with casual terms, while your content might use more formal language.&#x20;

* "Heart attack" ↔ "Myocardial infarction"

#### Acronyms vs. Full Names

Industry terms often have both an acronym and a full name.&#x20;

* "1PD" ↔ "First Party Data"


---

# 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://docs.direqt-search.com/managing-results/synonyms.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.
