---
title: Configuring caching
related:
  - https://docs.kentico.com/13/macro-expressions/caching-the-results-of-macros.md
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

Cache is a storage space that duplicates previously requested data, and allows faster access to the data in the future. Correctly using caching can significantly improve the performance of your website.

Caching the content of web pages provides two primary benefits:

- Quicker loading of data (retrieving data from the cache avoids communication with slower storage spaces, such as the website's SQL database and file system)
- Reduction of unnecessary page processing on repeated requests

The built-in caching mechanisms of Xperience work primarily on the server side, and utilize the application's memory to store data. The system saves data into the cache in the form of _**cache keys**_. Cache keys have unique names that exactly identify the cached content. Each key stores the cached data itself (depending on the type of the cache), as well as other information such as the expiration time or [dependencies](https://docs.kentico.com/13/configuring-xperience/configuring-caching/setting-cache-dependencies.md).

To learn about the available caching options, see [Caching on MVC sites](https://docs.kentico.com/13/configuring-xperience/configuring-caching/caching-on-mvc-sites.md).
