> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/general-settings.md).

# General settings

Assign languages and sales channels to data sources and set a subtitle for product names.

The **Settings** area has two cards. With the language assignment you decide which data source applies to which sales channel and language. Without it the search is not shown in the shop. With the subtitle configuration you show an additional field above or below the product name.

## Assign languages to individual data sources

<figure><img src="https://923488348-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FebcjSiStaIxyVJ83vjsL%2Fuploads%2Fgit-blob-a23bc0cdceb5dab749fece4432c2ac8b982c7d3c%2Fsuche-intelligent-und-ki-optimiert-einstellungen.png?alt=media" alt="Card for assigning languages to individual data sources with product feed, sales channel and assigned languages"><figcaption></figcaption></figure>

A data source always covers one language only. For the search to know which products to show, it needs the assignment to a sales channel and one or more languages. When a customer searches in a sales channel, our system uses this assignment to find the matching data source automatically. For multilingual shops you therefore create a separate data source for each language and assign it.

### How to assign

1. Open **Settings** in the sidebar.
2. In the card "Assign languages to individual data sources", choose the source in the first row under "Product feed / data source".
3. Choose the "Sales channel".
4. Choose one or more languages under "Assigned languages".
5. Add more rows with "Add assignment", remove a row with "Remove".
6. Click "Save assignment".

When you create a feed, in the setup wizard or in the "Add another feed" dialog, the assignment for the channel and the chosen language is set automatically. Older assignments without a sales channel are displayed and must be assigned to a channel.

### Rules

| Rule                                                                             | Effect                                                                                                                   |
| -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ |
| Every filled row needs a data source, a sales channel and at least one language. | Otherwise you see: "Please choose a product feed, a sales channel and at least one language for each filled assignment." |
| Within one sales channel a language belongs to only one data source.             | Otherwise you see: "Within the same sales channel a language may only be assigned to one product feed."                  |
| The same language may use different sources in different sales channels.         | Each sales channel can use its own feed.                                                                                 |
| Completely empty rows are ignored.                                               | You do not need to remove them.                                                                                          |

After saving you see "The language assignment was saved."

### What happens without an assignment?

If the assignment for a combination of sales channel and language is missing, the search does not appear in exactly this combination. A wrong assignment, for example the data source of another language, also looks like "no results". If data sources exist but there is no assignment at all, the overview shows a yellow warning and leads you here with "Assign languages".

{% hint style="info" %}
Orders from languages without their own data source are counted in the statistics with the data source of the same sales channel.
{% endhint %}

### Several sales channels

If you have several sales channels, assign each channel in its own rows. Create a separate feed for each channel. When creating it you choose sales channel, domain, language, currency and customer group, because a feed contains the prices of exactly one customer group, one currency and one language.

## Subtitle configuration

A subtitle is an additional field shown with the product name in the search overlay. An example is a custom field "Material", so that the text "Leather, waterproof" appears under "Hiking boot Alpine". The setting applies per data source.

At the top, "Configured subtitles per data source" shows what is already set. The chosen field is shown in green, otherwise "not configured" appears in gray.

### Settings

| Setting             | Effect                                                                                                           | Default                |
| ------------------- | ---------------------------------------------------------------------------------------------------------------- | ---------------------- |
| Choose product feed | Which data source the setting applies to.                                                                        | none                   |
| Enable subtitle     | Switches the subtitle on for this source. Only then do the two following fields appear.                          | off                    |
| Subtitle attribute  | The field whose content appears as subtitle, e.g. a custom field. The data attributes of the source are offered. | none                   |
| Subtitle position   | "Below the product name" or "Above the product name".                                                            | Below the product name |

Finally click "Save". Then "Subtitle settings saved." appears. The field must exist in the data source to be selectable. Which fields are transferred is set under "Edit data fields".

## Further reading

{% content-ref url="/pages/UKhMX3Zla832boJXFREa" %}
[Sources](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/indices.md)
{% endcontent-ref %}

{% content-ref url="/pages/gwPJIHZL0Lc3ekLkAsPI" %}
[Edit data fields](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/feed-template-editor.md)
{% endcontent-ref %}

{% content-ref url="/pages/ONADSPn6JKPHifT1E0iD" %}
[No results](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/no-results.md)
{% endcontent-ref %}


---

# 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.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/general-settings.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.
