--- title: Reusing existing page content related: - https://docs.kentico.com/13/developing-websites/defining-website-content-structure/managing-page-types/creating-page-types.md - https://docs.kentico.com/13/developing-websites/retrieving-content/displaying-reusable-content-and-related-pages.md - https://docs.kentico.com/13/managing-website-content/working-with-pages/reusing-other-pages-when-editing-content.md --- > 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). Xperience allows you to build [page types](https://docs.kentico.com/13/developing-websites/defining-website-content-structure/managing-page-types.md) with fields that reference other pages. Such fields use the **Pages** data type and [form control](https://docs.kentico.com/13/custom-development/extending-the-administration-interface/developing-form-controls.md). Content editors can then select existing pages within the given fields on the **Content** tab of the Pages application, and thus reuse content when modeling pages. Reused pages support [workflow](https://docs.kentico.com/13/configuring-xperience/configuring-the-environment-for-content-editors/configuring-workflows.md), [localization](https://docs.kentico.com/13/multilingual-websites/editing-the-content-of-multilingual-websites.md), and [page-level permissions](https://docs.kentico.com/13/managing-users/configuring-permissions/configuring-page-permissions/page-level-permissions-acls.md). For example, you can create an _Article_ page type that consists of standard fields, such as _Header_, _Text_, and _Image,_ as well as an additional _Pages_ field. An article page could then reuse content from other pages, such as an _Interesting fact_ page and an _Author_ page. In this scenario, both _Interesting fact_ and _Author_ are separate pages in the content tree that editors can use to model the content of the article. The purpose and appearance of the reused content always depends on the website's implementation, and needs to be handled by the website's developers. See [Displaying reusable content and related pages](https://docs.kentico.com/13/developing-websites/retrieving-content/displaying-reusable-content-and-related-pages.md). > **Info:** **Note** > > - Reusing pages via this approach serves mainly for modeling of content by editors. If you need to create named, two-sided page relationships between pages, use [standard page relationships](https://docs.kentico.com/13/managing-website-content/working-with-pages/working-with-page-relationships.md). > - Changing related pages in fields with the _Pages_ data type is not a versioned operation – pages under [workflow](https://docs.kentico.com/13/configuring-xperience/configuring-the-environment-for-content-editors/configuring-workflows.md) immediately reflect such changes in their published version. Individual pages that editors add using the _Pages_ data type can still be affected by workflow. > - On [multilingual websites](https://docs.kentico.com/13/multilingual-websites.md), related pages are shared between all culture versions. For example, if you add pages to a field in an English version of a page, the same pages are also added for all other culture versions. > - [Copying pages](https://docs.kentico.com/13/managing-website-content/working-with-pages/copying-and-moving-pages-creating-linked-pages.md) does not transfer the pages configured within _Pages_ fields. The new copy is considered as a separate page from the original, and editors can define any required relationships manually. ## Setting up page types to reuse pages To allow editors to reuse pages, add the **Pages** form control to a page type: 1. In the **Page types** application, **Edit** () a page type. 2. On the **Fields** tab, add a **New field**: - Data type: Pages - Form control: Pages > **Note:** **Note** > > We do not support usage of the **Pages** data type field in [alternative forms](https://docs.kentico.com/13/developing-websites/defining-website-content-structure/managing-page-types/creating-alternative-forms-for-page-types.md) for page types. 3. Use the **Field caption**, **Field description** and **Explanation text** fields to inform content editors about the intended use of the selected pages. For example: - Field caption: Interesting Fact and Author > **Tip:** In the advanced **Editing control settings** section, you can set additional optional settings for the form control. For example: > > - Select a **Starting path**. This allows you to specify the section of the site from which content editors can select pages. > - Choose a **Limit of related pages** to restrict the number of pages that editors can add to the field. 4. **Save** the changes. 5. Ensure that the website's developers [retrieve the reusable content](https://docs.kentico.com/13/developing-websites/retrieving-content/displaying-reusable-content-and-related-pages.md) and display it as required on the live site (in the code of the site's MVC application). Editors can now [use this advanced content modeling technique](https://docs.kentico.com/13/managing-website-content/working-with-pages/reusing-other-pages-when-editing-content.md) to reuse content. ## Reusing content through linked pages In addition to page type fields of the _Pages_ type, Xperience websites also provide another alternative way of reusing content – [Linked pages](https://docs.kentico.com/13/managing-website-content/working-with-pages/copying-and-moving-pages-creating-linked-pages.md). Linked pages represent a reference pointing to another page in the content tree. Such links exist as separate items in the content tree, but do not store any content by themselves. The content is linked to the original page – changes of the original are also reflected in the related linked pages. The following table compares both approaches: | | Pages fields | Linked pages | | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Editing interface | Managed through specific page fields on the **Content** tab in the **Pages** application. | Every linked page is a separate item in the site's content tree, displayed in the **Pages** application.
This helps editors and administrators keep a good overview of how and where content is reused on the website. | | Page URLs | Each reused page only exists once in the content tree, so only has one URL assigned by the system. In many cases, the URL of the reused page is not important and not even part of the utilized content (depends how the content reuse is implemented by the site's developers). | The original page and all linked pages can have different URLs, for example based on their location in the content tree (when using [content tree-based routing](https://docs.kentico.com/13/developing-websites/implementing-routing/content-tree-based-routing.md)).
To mitigate duplicate content issues (SEO), we strongly recommend adding [Canonical link elements](https://en.wikipedia.org/wiki/Canonical_link_element) to pages – see [Providing canonical URLs for pages](https://docs.kentico.com/13/developing-websites/implementing-routing/enabling-alternative-urls-for-pages.md#providing-canonical-urls-for-pages). | | Permissions | [Page-level permissions (ACLs)](https://docs.kentico.com/13/managing-users/configuring-permissions/configuring-page-permissions/page-level-permissions-acls.md) can be applied individually to the pages that reuse the content.
Depending on the site's implementation, the logic that loads the reused pages may or may not check their permissions. | Every linked page can have its own configuration of [page-level permissions (ACLs)](https://docs.kentico.com/13/managing-users/configuring-permissions/configuring-page-permissions/page-level-permissions-acls.md). | | Multilingual support | The selection of related/reused pages is shared between all [culture versions](https://docs.kentico.com/13/multilingual-websites/editing-the-content-of-multilingual-websites.md) of the page. | Linked pages are available in the same [culture versions](https://docs.kentico.com/13/multilingual-websites/editing-the-content-of-multilingual-websites.md) as the original page. | | Recommended usage | Modeling scenarios where a page type's structured fields include snippets of content from other pages.
Any scenarios where different URLs are not desirable for occurrences of reused pages.
**Examples**:
Displaying related articles with a content snippet on an articles page.
Modeling the pages included in a [secondary navigation menu](https://docs.kentico.com/13/developing-websites/building-website-navigation.md) (e.g. a sidebar or website footer menu). | Particularly suitable for [page taxonomy](https://docs.kentico.com/13/managing-website-content/working-with-pages/categorizing-pages.md) (placing pages or products into multiple different categories).
General content reusing scenarios where the entire original page is only a content snippet without its own representation on the live site.
**Example**: Adding a product page under multiple different sections of an e-commerce website. | | Content editor resources | For detailed information about editing pages with fields that reuse content, see:
[Reusing other pages when editing content](https://docs.kentico.com/13/managing-website-content/working-with-pages/reusing-other-pages-when-editing-content.md) | For detailed information about creating linked pages, see:
[Copying and moving pages, creating linked pages](https://docs.kentico.com/13/managing-website-content/working-with-pages/copying-and-moving-pages-creating-linked-pages.md) | | Developer resources | To learn how to load and display reusable content from page fields in your site's code implementation, see:
[Displaying reusable content and related pages](https://docs.kentico.com/13/developing-websites/retrieving-content/displaying-reusable-content-and-related-pages.md) | To work with linked pages in your site's code, use the same approach as when loading general pages. See:
[Displaying page content](https://docs.kentico.com/13/developing-websites/retrieving-content/displaying-page-content.md)
You can filter out linked pages from the loaded data by adding the **FilterDuplicates** [DocumentQuery method](https://docs.kentico.com/13/custom-development/working-with-pages-in-the-api/reference-documentquery-methods.md). |