> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cms/19.latest/develop-with-umbraco/search/built-in-property-editors.md). # Indexed Values of Built-in Property Editors A list of the built-in Umbraco property editors and their corresponding index value types in search The following list shows how the [built-in Umbraco property editors](https://docs.umbraco.com/umbraco-cms/fundamentals/backoffice/property-editors/built-in-umbraco-property-editors) are indexed for search. Some property editors are excluded because they generate more noise than value in the index. For example, color and media pickers have been omitted. | Property editor | Indexed as | Notes | | ----------------------------- | ---------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `Umbraco.BlockGrid` | (see below) | | | `Umbraco.BlockList` | (see below) | | | `Umbraco.CheckBoxList` | `Keyword` | | | `Umbraco.ContentPicker` | `Keyword` | Indexes the ID (key) of the picked content. | | `Umbraco.DateTime` | `DateTimeOffset` | | | `Umbraco.Decimal` | `Decimal` | | | `Umbraco.DropDown.Flexible` | `Keyword` | | | `Umbraco.Integer` | `Integer` | | | `Umbraco.Label` | (see below) | | | `Umbraco.MarkdownEditor` | `Text` | Same as `Umbraco.RichText` | | `Umbraco.MultiNodeTreePicker` | `Keyword` | Indexes the IDs (keys) of the picked content. Does not index values when configured to pick media or members. | | `Umbraco.MultipleTextstring` | `Text` | | | `Umbraco.MultiUrlPicker` | `Text` | Indexes the names (titles) of the picked links. | | `Umbraco.Plain.String` | `Text` | | | `Umbraco.Plain.Decimal` | `Decimal` | | | `Umbraco.Plain.Integer` | `Integer` | | | `Umbraco.Plain.DateTime` | `DateTimeOffset` | | | `Umbraco.RadioButtonList` | `Keyword` | | | `Umbraco.RichText` | `Text` | Headings (H1, H2, H3) are indexed with individual relevance, all other tags as lowest relevance text. If the property contains blocks, they are indexed in the same way as the block editors. | | `Umbraco.Slider` | `Decimal` | For range slides, both the lower and upper bounds are indexed. | | `Umbraco.Tags` | `Keyword` | In addition, all tags for all properties are accumulated into a dedicated system field (see [system fields](/umbraco-cms/19.latest/develop-with-umbraco/search/system-fields.md)). | | `Umbraco.TextArea` | `Text` | Indexed as lowest relevance text. | | `Umbraco.TextBox` | `Text` | Indexed as lowest relevance text. | | `Umbraco.TrueFalse` | `Integer` | Indexed as 1 for `true`, 0 for `false`. | ### Special case: `Umbraco.BlockGrid` and `Umbraco.BlockList` Block editors contain other property editors. These will iterate their contained properties and aggregate their index values. As such, a single block editor property value can potentially index as all value types. ### Special case: `Umbraco.Label` The label editor indexes as either `Integer`, `Decimal`, `DateTimeOffset` or `Text`, depending on the Data Type configuration (the property editor value type). --- # 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.umbraco.com/umbraco-cms/19.latest/develop-with-umbraco/search/built-in-property-editors.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.