> For the complete documentation index, see [llms.txt](https://docs.nosto.com/shopware-6/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nosto.com/shopware-6/getting-started/guides/caching.md). # Caching Feature flag introduced in Nosto Plugin 3.5.5 / 5.1.5 / 6.0.0 **Default Shopware Caching**\ Only the **first** load of a Category (PLP) or Search (SERP) page was served by Nosto; subsequent visits were served from Shopware’s core cache, potentially showing stale data. This could affect personalisation and analytics on Nosto, ### 1 Where to find it ``` Shopware Admin → Extensions → My Extensions → Nosto → Configuration ``` ***
### 2 Behaviour Overview | Flag | Cache interval | Result | | ------------ | -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Disabled** | n/a | Caching is disabled for all PLP & SERP requests. Every page load fetches fresh results from Nosto. | | **Enabled** | *N* minutes (set below the flag) | Caching is enabled for PLP/SERP response in its HTTP cache. The first request after *N* minutes triggers a fresh call to Nosto; all other requests within the interval are served from cache. | *** ### 3 Configuration Steps 1. **Open Nosto plugin settings** (see path above). 2. Toggle **Enable Cache**: * Off – real-time results (no cache). * On – enable caching. 3. If enabled, set **Cache interval (minutes)** to your preferred TTL, e.g. **15**.\ *Minimum*: 1 min · *Typical*: 10–30 min · *Maximum*: any value 4. **Save** the configuration. Changes take effect immediately—no Shopware cache clear is required. *** #### How it works under the hood * **Flag off** → The plugin tells Shopware to add the route `/product-listing/*` and `/search/*` to the cache exclusion list. * **Flag on** → The plugin attaches the configured TTL so Shopware’s HTTP cache invalidates pages automatically. *** ### 4 FAQ **Does this affect CMS/PDP pages?**\ No. Only Category and Search result pages rendered via Nosto are affected. **What would happen if I enable caching?**\ Category and Search result pages would be caching for a selected timeframe. This would affect Search and CM analytics on Nosto as well as show stale data when it comes to personalisation, and rules depending on affinity/segments
--- # 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.nosto.com/shopware-6/getting-started/guides/caching.md?ask=&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.