> 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/system-fields.md).

# System Fields in Content Indexes

A list of the system fields included in all content indexes

The following fields are explicitly indexed for all content.

| Field name          | Indexed as       | Notes                                                                        |
| ------------------- | ---------------- | ---------------------------------------------------------------------------- |
| `Umb_ContentTypeId` | `Keyword`        | The ID (key) of the content type.                                            |
| `Umb_CreateDate`    | `DateTimeOffset` | The creation date of the content.                                            |
| `Umb_Id`            | `Keyword`        | The content ID (key).                                                        |
| `Umb_Level`         | `Integer`        | The content level in the tree.                                               |
| `Umb_Name`          | `Text`           | The name of the content. Indexed as highest relevance text.                  |
| `Umb_ObjectType`    | `Keyword`        | The content object type (for example "Document").                            |
| `Umb_ParentId`      | `Keyword`        | The ID (key) of the parent (if any).                                         |
| `Umb_PathIds`       | `Keyword`        | The IDs (keys) of all ancestors and the content itself.                      |
| `Umb_SortOrder`     | `Integer`        | The sort order of the content.                                               |
| `Umb_Tags`          | `Keyword`        | Accumulated collection of tags from all properties contained in the content. |
| `Umb_UpdateDate`    | `DateTimeOffset` | The last update date of the content.                                         |

System fields can be used like any other fields for searching. The system field names are defined in [`Constants.Search.FieldNames`](https://github.com/umbraco/Umbraco-CMS/blob/main/src/Umbraco.Core/Constants-Search.cs).

{% code title="MySearchService.cs" %}

```csharp
using Umbraco.Cms.Core;
using Umbraco.Cms.Core.Search;
using Umbraco.Cms.Core.Search.Querying;
using Umbraco.Cms.Core.Search.Querying.Filtering;

namespace My.Site.Services;

public class MySearchService(ISearcher searcher)
{
    public async Task<SearchResult> FilterByNameAsync()
    {
        return await searcher.SearchAsync(
            indexAlias: Constants.Search.IndexAliases.PublishedContent,
            filters:
            [
                new TextFilter(
                    FieldName: Constants.Search.FieldNames.Name,
                    Values: ["pink"],
                    Negate: false
                )
            ]
        );
    }
}
```

{% endcode %}


---

# 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/system-fields.md?ask=<question>&goal=<user_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.