> 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/integration/factfinder-search-integration/caching-search-results.md).

# Caching search results

FactFinder includes a search results cache that speeds up repeated queries. To decide whether a request matches a cached query, FactFinder checks the submitted search parameters. Only pass parameters that FactFinder actually needs. By default, FactFinder treats every received parameter as relevant for caching \[1]. Extra parameters reduce cache efficiency.\
You can also cache FactFinder results in your shop system. If you do, remember that FactFinder can invalidate its own cache when the configuration changes or product data is updated. Your shop system does not learn about those internal changes automatically. As a result, the shop may keep serving outdated cached results.

***

\[1] Parameters that FactFinder does not use directly may still be used by custom extensions and can therefore change the search result. That is why all parameters are treated as relevant for the cache.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.fact-finder.com/integration/factfinder-search-integration/caching-search-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.