> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/docs/getting-started-guide/configuration.md).

# Configuration

![](https://883583471-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTV1CIVFU3DJKhWzkqLAG%2Fuploads%2Fgit-blob-6a396a273451687a031039ba07555d69861a8d33%2Fgetting-started-image-trs7lg4m.jpg?alt=media)

Once we receive the data feed and successfully import it into the FactFinder setup, we begin configuring FactFinder according to the requirements defined earlier.

> The basic configuration establishes initial settings so FactFinder delivers high‑quality results from the start. These settings combine best practices with your input and are tailored to your needs.

To achieve high-quality results, we typically perform the following during basic configuration:

* Optimize your top search terms
* Set field weights (which fields are most relevant for results)
* Configure at least two best‑practice ranking rules
* Set up best‑practice campaigns
* Configure thesaurus, blacklist, and synonym basics

## Prepare for configuration

As the product experts, you can assess whether a search result is of high quality or requires refinement. We rely on your input to achieve relevant results. Ideally, please provide the following to set up the basic configuration:

**Your top 50 search terms**

* Examples: product names, brand names, long‑tail keywords
* Exclude article or ID numbers

***

**Your most important business rules**

* For example: private‑label products to promote, sale items to highlight

***

**Further details relevant for search results, e.g.:**

* List of synonyms
* Redirects for certain search terms
* Other items specific to your domain

Once the basic configuration is established, one of our Business Consultants will provide an overview of the settings and discuss the results with you.


---

# 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.fact-finder.com/docs/getting-started-guide/configuration.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.
