> 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/get-started/backoffice-essentials/sorting-pages.md).

# Sorting Pages

Learn how to change the sort order of pages within the content tree using the Sort function.

The pages in Umbraco are placed in the tree structure according to a predefined sort order. The most recently created page is placed at the bottom of the tree structure. You can change the order of the pages by using the **Sort** function.

## Opening the Sort children dialog

You can open the dialog in two ways.

### From the content tree

1. Go to **Content**.
2. Navigate to the parent node whose child nodes you wish to sort.
3. Click **...** next to the page you wish to sort.
4. Select **Sort children of**.

![Sort Menu](https://1282852327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbFfxUcTsPCzuMkpCkZsT%2Fuploads%2Fgit-blob-2b277efb6f2399022e3e8e2092ac228b9e52fda3%2Fsort-menu-18.png?alt=media)

### From the Actions menu

1. Go to **Content**.
2. Select the parent node whose child nodes you wish to sort.
3. Click **Actions** in the top-right corner of the screen.
4. Select **Sort children of** from the **Actions** drop-down menu.

![Actions Menu](https://1282852327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbFfxUcTsPCzuMkpCkZsT%2Fuploads%2Fgit-blob-b8c2f532238cd4415722dcb4641652e2460e57a1%2Factions-menu-18.png?alt=media)

## Sorting the child nodes

A window appears on the right-side of the screen with two tabs: **Sort individually** and **Sort by field**.

![Sort children dialog](https://1282852327-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbFfxUcTsPCzuMkpCkZsT%2Fuploads%2Fgit-blob-1bbd6f3feafcdbdb958f52507bd64bc7ca7be745%2Fsort-children.png?alt=media)

Choose the tab that matches the order you need, then click **Sort**. Click **Cancel** to close the window without changing the order.

### Sort individually

Use **Sort individually** when the order does not follow any field value. This is the option to choose when you want to hand-pick the order, such as placing a featured page at the top of a list.

1. Drag the child nodes up or down using the handle to the left of each row.
2. Click **Sort**.

You can also click the **Name** or **Created** column header to order the rows by that column. The dialog loads 50 child nodes at a time. Column headers become clickable once every child node is loaded, so click **Load more** until the full list is shown.

### Sort by field

Use **Sort by field** when the order follows a value on the pages themselves. This could be an alphabetical list or a news section with the newest article first. The sort runs on the server and covers every child node, including any not yet loaded into the window. This makes it the better option for parent nodes with many children.

1. Select a field to sort by: **Name**, **Created**, or **Last edited**.
2. Select a direction: **Ascending** or **Descending**.
3. Click **Sort**.

{% hint style="info" %}
Sorting by **Name** on a multilingual site also lets you select the language to sort by. The language selected in the backoffice is used by default.
{% 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/get-started/backoffice-essentials/sorting-pages.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.