> 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/search-results-page.md).

# Search results page

Supply Shopware's search results page with the results and order of InsightSearch: what changes, limits and restrictions.

When a customer presses Enter in the shop, Shopware opens its own search results page. With the setting "Deliver Shopware search results page via InsightSearch" this page stays as it is, but the results and their order come from InsightSearch. Customers get the same quality in the search window and on the results page, without you touching your theme.

You find the setting in the plugin configuration on the card "Search configuration" in the area "Search results page and variants". It is off by default.

## What stays with Shopware

* the page itself with your theme and the heading "Search results for …"
* the product tiles of the theme with wish list and buy buttons
* the filter bar
* the sorting selection
* the paging
* SEO data and hint texts

## What changes

* **Results and order** come from InsightSearch, with typo tolerance, AI results, rules such as pinning and hiding, personalisation and the rescue stages for zero results. The default sorting "Best results" follows the InsightSearch ranking completely.
* **Enter** in the search fields opens this page. Anyone who types in the search window still gets the results in the window.
* **Filters** narrow down only within the InsightSearch results, not across the whole catalogue. Counters and options of the filter bar refer to this result set.
* **Sorting and paging** (price, name and so on) work within this result set. You may choose Shopware's page size ("Products per page") freely.
* **Variants:** With "Combine variants of the same product into one hit" (default: on) the page shows the same number of results as Shopware's own product list. The filter counters still count variants.
* **Hint line** below the heading when a relaxed or corrected search was used ("No exact matches for …" or "Showing results for …" with the link "Search for … instead").
* **Product boxes** below the list: "You might also like" (related results) and "You may be interested in" (replacement products), each up to 12 products in your theme's standard tiles.

The stages for zero results are the same as in the search window. They are described on the page [No results](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/no-results.md).

## Limits

| Setting                                                | Effect                                                                                                                                                                                                            | Default |
| ------------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------- |
| "Maximum number of results on the search results page" | Upper limit for the results delivered by InsightSearch. Allowed are 1 to 10000, because Shopware can technically only page through 10000 entries. Larger values mean more queries on the first search for a term. | 2000    |
| "Combine variants of the same product into one hit"    | Combines variants into one tile, like Shopware's list.                                                                                                                                                            | on      |

There are also fixed limits that you cannot change:

* **Time budget:** Building the page waits at most about 3 seconds for the result list. If the time is exceeded, the page uses the list fetched until then (shortened). If nothing is there yet, Shopware takes over.
* **Temporary storage:** The result list per term, sales channel and language is kept for 120 seconds. This speeds up repeated searches. With active personalisation the storage is not shared, so that not all visitors get the order of the first one.
* **Zero results means zero results:** There is no fallback to Shopware's search. Otherwise window and page would contradict each other.
* **Fallback to Shopware** only happens on an error, on a timeout, for a language without assignment and when the switch is off. Shopware then shows its own results.

## Restrictions

{% hint style="warning" %}
The function cannot be combined with an active Elasticsearch or OpenSearch integration of Shopware for products. If it is active, the plugin does not take over the page, rather than delivering a wrong page.
{% endhint %}

* Third-party plugins that change sorting or the product list can change the order.
* The page is stored temporarily for all visitors. Therefore the recommendations and replacement products there contain no personalised selection.
* The replacement image for products without an image does not apply here. Shopware shows its own display.

## Impression tracking

So that the [Statistics](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/statistics.md) are correct, the page reports which results a visitor actually saw:

* A tile counts as shown when at least half of it is in view, once per tile.
* The reports are sent in bundles, after about one second, at 50 items and when leaving the page.
* After a filter change or paging, tracking starts again.
* Clicks on the result (also with the middle mouse button), "Add to cart" and the wish list are counted separately.
* If the number of displayed tiles does not match the delivered result list, nothing is tracked.
* Tracking uses the visitor identifier. With consent in the cookie banner ("Comfort features") this is the shared identifier, otherwise an identifier for the browser tab only.

## Search engine crawlers

Crawlers also get the InsightSearch results when they fetch the page. For crawlers, no replacement products from Cross-Selling Pro are requested, so that they do not use up the quota. Events from crawlers and scripts are not counted; they do not count as visitors.

## Redirect and banner

Rules from the [search term rules](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/search-term-rules.md) apply on the search results page even if the page is not supplied by InsightSearch:

* **Redirect:** It applies before the page is displayed, so also for bookmarks and Shopware's own search form. Allowed targets are relative paths, the domains of the sales channel and the domains entered under "Allowed external hosts for search term redirects".
* **Banner:** A shopping experience appears above the results.

## How to switch the function on

1. Open the plugin configuration and the card "Search configuration".
2. Switch on "Deliver Shopware search results page via InsightSearch". This includes "Allow redirect to Shopware search results page on Enter", you do not have to switch it on in addition.
3. Decide about "Combine variants of the same product into one hit" and the "Maximum number of results on the search results page".
4. Save, search in the shop and press Enter.

## Read on

{% 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/ONADSPn6JKPHifT1E0iD" %}
[No results](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/no-results.md)
{% endcontent-ref %}

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

{% content-ref url="/pages/v20EC98NJrD47BUleH4w" %}
[Plugin settings](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/plugin-settings.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/search-results-page.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.
