---
title: Mapping fields for search results
related:
  - https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes/creating-local-search-indexes.md
  - https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes/building-a-search-interface-for-local-indexes.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).

When setting up search using [locally stored indexes](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes.md), you can separately configure the indexed objects (Page types, Custom tables, Forms, etc.), and choose which data appears in search results.

The appearance and design of the results always depends on the [search interface implementation](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes/building-a-search-interface-for-local-indexes.md). However, the system allows you to map specific object fields to the most common parts of search results, such as the title, content extract or image. Developers can then access the mapped data in their code using the corresponding properties of **SearchResultItem** objects, which they process within the search implementation.

1. Edit the indexed object (most commonly in the **Page types**, **Custom tables** or **Forms** application).
2. Select the **Search** tab.
3. In the **Field mapping for search results** section, choose source fields for the following parts of search results:

   |                   | Description                                                                      | SearchResultItem property |
   | ----------------- | -------------------------------------------------------------------------------- | ------------------------- |
   | **Title field**   | The field whose value is used for the title of search results.                   | Title                     |
   | **Content field** | The field whose value is used for the content extract of search results.         | Content                   |
   | **Image field**   | The field that contains the image displayed in search results.                   | Image                     |
   | **Date field**    | The field whose value is used for the date and time displayed in search results. | Created                   |
4. Click **Save**.

The search results for the given object type now display data from the assigned fields, provided that developers use the corresponding _SearchResultItem_ properties within the search implementation.

All selected fields are **automatically included within search indexes** that cover the object type. This applies even for **Pages** indexes and page types using the **HTML output** data source (in this case the search itself is based on the processed HTML content of pages, but data for search results is loaded from the assigned fields).

> **Note:** **Note**: Search result field mapping does not have any effect for [Azure Search](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-azure-cognitive-search.md) indexes. The format of Azure search results is fully controlled by the implementation of your search interface. See [Integrating Azure Search](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-azure-cognitive-search/integrating-azure-search.md).