Last updated: Feb 23 2018

Area: Episerver CMS Applies to versions: Latest

Page tree and routing

This topic introduces the concept of content structure and routing in Episerver. Website URLs carry information from the browser to the server requiring it to enact a desired action, and URLs in their original format are often difficult to interpret. Routing rewrites a URL to make it more user-friendly, which is also useful in search-engine optimization (SEO).

In this topic

Content structure

Content such as pages, folders, blocks, images and documents in Episerver, are stored in one big hierarchy. You can see this in the admin view when setting access rights for content. Views filter out different types of content, and display it for example as Pages in the Navigation pane, and folders, images and documents under Media in the Assets pane.

Each content item has a unique name and numerical ID. For a page, the page name and ID number together with the page type upon which the page is based, are displayed when hovering over it in the page tree structure.

Similarly for an image, the image name and ID number are displayed, together with the media type upon which the image is based, when hovering over an image in the media folder structure.

Content routing

Routing is automatically handled based on content type. For pages for example, the text in the build-in property Name in URL (named URLSegment code) builds the full URL path for that page. Episerver adds its owns routes, finds the content in the database using the URL, loads the content, and resolves which rendering template to use. 

Routing in Episerver CMS is based on ASP.NET built-in routing. Several routes are registered by default, see Routing. One of them, used to handle pages, looks like this: 


The segments are used as follows:

  • {language}. Optional, states the language for multi-language sites, uses valid ISO culture codes.
  • {node}. Matches the content structure, sets the page reference from the URL.
  • {partial}. Optional, used if there is a registered partial router, for example for items in a Commerce catalog.
  • {action}. Optional, corresponds to an action method name in the controller, if this exists.

Example: The URL for the "A sub-page" page in the page tree structure above will resolve to ".../en/second-page/a-sub-page", where "A sub-page" is the page name.


Simple address

This option provides a unique URL that can be added to frequently requested pages, letting visitors locate the page simply by typing the simple address name directly after the main URL of the website. 

Example: Adding the simple address "airbaloon" for the "A sub-page" page, will resolve to ".../airbaloon", ignoring the  Name in URL and content structure path.

A simple address is culture specific, and remains even if a page is moved in the page structure.

Sorting and moving pages

You can organize the pages in the page tree by modifying the sort order. By default pages are listed by creation date, with the most recent one on the top. The sort index lets you control the exact display order. This can be changed through drag-and-drop, or by updating it on each page. Moving a page within the same page node, will not affect the URL as the hiearchical path to the page remains the same.

Moving pages between different page nodes will change the URL. This will not break any internal links, as these are based on the page ID which the system keeps track of. However, any incoming links to the page with the "old" URL will break.

See Structuring the website in the Episerver User Guide.

Related topics