> 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/getting-started.md).

# Getting started

Checklist for the time after setup, in a sensible order, with links to the pages.

The wizard has read in your products, the search is running. With the following steps you bring it to a good level. Work through the list in order. Each point takes only a few minutes and links to the page with the details.

## Task list

### 1. Activate the search

The wizard switches the search on itself at the end. Check it anyway: open the plugin configuration, card "Search configuration", and check the switch "Enable search". The settings apply per sales channel, "All sales channels" passes them on to all channels. If the search is off, your customers keep seeing the Shopware search.

More: [Plugin configuration](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/plugin-settings.md)

### 2. Assign languages

In a language, the search only shows results if a data source is assigned for it. The wizard creates the assignment for the chosen language itself. If you have further languages or sales channels, assign them in the "Settings" area in the card "Assign languages to individual data sources". Within one sales channel, a language can only be assigned to one feed.

More: [Language assignment and subtitle](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/general-settings.md)

### 3. Check product data

In the "Sources" area, check that your data source has the status "Ready" and shows the expected number of products. In the "Products" area, under "Data quality", you find hints about incomplete product data, for example variants without a group ID. If fields such as brand or category are missing, activate them via "Edit data fields" and then read the products in again with "Re-import product data".

More: [Sources (indices)](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/indices.md), [Edit data fields](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/feed-template-editor.md), [Products in the dashboard](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/products-in-the-dashboard.md)

### 4. Choose the activation mode

The activation mode decides how the search window opens. You find it in the plugin configuration, card "Search configuration", under "Search activation mode". The default is "Use Shopware standard search field". The other modes are "Search field always visible", "Activate via external trigger" and "Activate via search button". The default fits most themes. If your theme has no search field or an unusually built one, try another mode.

More: [Search in the shop](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/search-in-the-shop.md)

### 5. Test the search in the shop

Open your shop and search for typical terms: product names, brands, article numbers, a word with a typo. Try the search overlay and the search results page, on desktop and on mobile. If you want to compare settings, the "Search sandbox" in the "Products" area helps. The search strategy is also worth a look: "Standard" is balanced, "Precise" suits article numbers in specialist shops, "Exploratory" delivers as many results as possible.

More: [Search in the shop](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/search-in-the-shop.md), [Search results page](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/search-results-page.md), [Search on mobile](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/search-on-mobile.md)

### 6. Set up filters

Filters help customers narrow down results. They are built on data attributes. In the "Data attributes" area, check that the desired attributes are "Active", then create your filters in the "Filters" area: name, display as list or slider, position. Changes to filters can take up to 5 minutes.

More: [Filters](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/filters.md), [Data attributes](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/data-attributes.md)

### 7. Create synonyms

Customers do not always search the way your products are named. In the "Synonyms" area, create equivalent terms, for example `Sweater, Sweatshirt, Hoodie`, or a one-way assignment such as `Trousers, Jeans => Pants`. New and changed synonyms take effect after a short time.

More: [Synonyms](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/synonyms.md)

### 8. Set up the rescue for zero results

When nothing is found, the search can try again in a relaxed way, correct typos and show replacement products. The switches for this are in the plugin configuration in the card "No results & related results". Most are on by default. Check whether the defaults suit your shop.

More: [No results](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/no-results.md)

### 9. Look at the statistics

After a few days with visitors, the statistics show what is searched for, which searches stay without results and how much revenue is generated through the search. The list of searches without results is especially useful: new synonyms can be derived from it. The statistics can only be seen by admin users who are allowed to view orders.

More: [Statistics](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/statistics.md), [Permissions](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/permissions.md)

### 10. Customize the design

Finally, adapt the look and arrangement of search overlay and results page to your theme: layout of the search results, colors, display of images and prices. These settings are also in the plugin configuration.

More: [Customize design](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/customize-design.md)

{% hint style="success" %}
You do not have to do everything in one day. With points 1 to 5 the search is already well usable. The other points improve it step by step, ideally guided by the statistics.
{% endhint %}

## Continue reading

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

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

{% content-ref url="/pages/cPKiMg6nNvV0NE0owXnG" %}
[Troubleshooting](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/troubleshooting.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/getting-started.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.
