> 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/13.latest/tutorials/editors-manual/getting-started-with-umbraco/finding-content.md).

# Finding Content

The Umbraco content tree view allows you to navigate web pages through a logical site hierarchy. You can find a page by navigating through the tree itself if you know where the page is stored.

## Searching in Umbraco

To search across all the content, files, or folders in Umbraco, click the Magnifier icon in the top-right of the screen. Alternatively, you can use the keyboard shortcut **CTRL + SPACE** to access the **Search** bar.

Using the search bar, you can enter a search term to search across most content and settings data in the backoffice. This includes:

* Document Types
* Data Types
* Members
* Member Types
* Dictionary Items
* Templates, and more.

The exact set of tabs depends on your version and installed packages, such as Umbraco Forms.

![search.jpg](https://3872888104-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgEH4FChbCn7eDDqREvdE%2Fuploads%2Fgit-blob-0cc1896219d66be0bee1a6596871ac2071592e39%2Fsearch-bar-v9.png?alt=media)

{% hint style="info" %}
By default, each word in your search matches anything it's the start of. For example, `test` also matches "Testing". Wrap your search in double quotes (for example, `"test"` or `"contact page"`) to match that exact word or phrase only, without the partial matches.
{% endhint %}


---

# 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/13.latest/tutorials/editors-manual/getting-started-with-umbraco/finding-content.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.