---
title: Defining custom table indexes
related:
  - https://docs.kentico.com/13/developing-websites/defining-website-content-structure/managing-custom-tables.md
  - https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes/creating-local-search-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 editing custom table indexes on the **Indexed content** tab in the **Smart search** application, you can see a list of [custom tables](https://docs.kentico.com/13/developing-websites/defining-website-content-structure/managing-custom-tables.md) included in the index.

> **Note:** **Note**: Custom table indexes are only available as [locally stored indexes](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes.md) (not as [Azure Search ](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-azure-cognitive-search.md)indexes).

To add custom tables to the index, click **Add custom table**. You can also **Edit** () the way listed custom tables are indexed or **Delete** () them from the list.

When adding a new custom table to the index or editing an existing one, you have the following options:

- **Custom table** – selects which custom table is indexed.
- **Where condition** – sets the WHERE clause of the queries that the system uses to load data from the custom table when building the index. Allows you to limit which records (rows) are included in the search index.

![Adding a new custom table to an index](https://docs.kentico.com/docsassets/13/defining-custom-table-indexes/Indexed_Content_Custom_Tables.png "Adding a new custom table to an index")

> **Note:** **Note**: You need to **Rebuild** the index on the **General** tab in order for changes to take effect.

## Configuring search settings for custom table fields

Each custom table has a different set of fields and stores different types of data. You can configure exactly how the system searches through the fields of individual tables and how the data appears in the search results. We recommend indexing only necessary fields to keep your indexes as small (and fast) as possible.

To edit the field search settings for custom tables:

1. Open the **Custom tables** application.
2. Edit () a custom table.
3. Select the **Search** tab.

The options in the _Field mapping for search results_ section allow you to configure how the system displays records from the custom table in search results. See [Mapping fields for search results](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes/mapping-fields-for-search-results.md) for detailed information. Note that the final appearance of the results always depends on your site's [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).

The grid in the bottom section of the tab determines how the smart search indexes the custom table's fields (as defined on the **Fields** tab). You can set the following options for individual fields:

| Content            | If selected, the content of the field is indexed and searchable in the standard way. Within search indexes, the values of all fields with the _Content_ option enabled are combined into a system field named **\_content** (this field is used to find or filter matching search items, but is NOT suitable for reading and displaying human-readable information such as search result extracts).<br>For the purposes of standard search, _Content_ fields are automatically tokenized by the analyzer of the used search index.                                         |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Searchable         | If selected, the field is stored separately within indexes and its content can be searched using expressions in format:<br>_:_<br>See [Smart search syntax](https://docs.kentico.com/13/configuring-xperience/setting-up-search-on-your-website/using-locally-stored-search-indexes/smart-search-syntax.md) for more information about field searches.<br>Fields must be set as _Searchable_ to be usable in search result filtering or ordering conditions[.](http://preview/Documentation/devguide/smart_search_filter.htm)                                              |
| Tokenized          | Relevant for **Searchable** fields. Indicates if the content of the field is processed by the analyzer when indexing. This allows the search to find results that match individual tokens (subsets) of the field's value. If disabled, the search only returns items if the full value of the field exactly matches the search expression.<br>If a field has both the _Content_ and _Searchable_ options enabled, the _Tokenized_ option only affects the content used for field searches (content is always automatically tokenized for the purposes of standard search). |
| Custom search name | Relevant for **Searchable** fields. The specified value is used as a substitute for the field code name in _:_ search expressions.<br>**Note**: If you enter a Custom search name value, the original field name cannot be used.                                                                                                                                                                                                                                                                                                                                           |

> **Note:** After you **Save** changes of the field settings, you need to **Rebuild** all indexes that include the given custom table.

When running searches using custom table indexes, the system returns results according to the field search settings of individual tables. The field search settings are shared by all custom table indexes in the system.