---
title: Content inheritance
---

> Agent instructions:
> **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown.
>
> - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version.
> - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt).

Inheritance (page nesting) allows you to maintain a consistent design throughout the website and manage content shared by multiple pages in a single location. The portal engine implements inheritance by nesting subpages inside the content of ancestor pages on higher levels of the content tree.

> **Info:** **What are ancestor documents?**
>
> Ancestors include all documents under which a given document is stored, from the root of the site's content tree down to the document's direct parent.
>
> For example, the _**/Company/Offices/London Office**_ document has the following ancestors:
>
> - Website root document
> - /Company
> - /Company/Offices

### Website root (master page) without nested content

![Website root (master page) without nested content](https://docs.kentico.com/docsassets/k8tutorial/content-inheritance/Master_Page.png "Website root (master page) without nested content")

### Home page nested inside the master page

![Home page nested inside the master page](https://docs.kentico.com/docsassets/k8tutorial/content-inheritance/Home_Nested.png "Home page nested inside the master page")

### Page placeholder

Note how the pages are structured in the content tree: the root (master page) is the parent of the Home page, which is loaded inside the master page. You can perform nesting recursively at any level of the content tree. A necessary component for page nesting is the **Page placeholder** web part. This web part must be placed on the master page, and specifies where the system inserts the underlying pages. The Page placeholder on the Corporate Site root loads the sub-pages between the main menu and footer.

![Page placeholder web part on the Design tab of the master page](https://docs.kentico.com/docsassets/k8tutorial/content-inheritance/Page_Placeholder.png "Page placeholder web part on the Design tab of the master page")