---
title: Defining content structure on MVC sites
related:
  - https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/advanced-content-modeling.md
  - https://docs.kentico.com/k11/developing-websites/defining-website-content-structure.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).

The content displayed on MVC sites is represented by [content only pages](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/creating-content-only-page-types.md). Ideally, developers (or administrators) set up a page structure and limit where content editors create pages. Content editors then create and [model](https://docs.kentico.com/k11/managing-website-content/working-with-pages/modeling-content-by-reusing-pages.md) content.

> **Info:** **Page type restrictions**
>
> When defining content structure of your site, we recommend creating pages that are based on [content only page types](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/creating-content-only-page-types.md). Pages based on regular [page types](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types.md) are not supported on MVC sites.

## Defining content structure

The structure of pages in Kentico doesn't represent how the content is displayed on the live site. Developers fully control how content is displayed.

We recommend structuring pages in Kentico so that each page type has its own section. This makes both working with the content in the MVC application and managing and reusing the content simpler. For example:

- Root  
  - Articles
    - Article page
    - Article page
    - ...
  - Store
    - Product page
    - Product page
    - ...
  - ...

Make sure you set up the page structure to take performance limitations into consideration. Each item (page) in the content tree shouldn't exceed 1000 direct child pages. See [general information](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure.md) on structuring content in Kentico.

You can also set up Kentico pages for [advanced content modeling.](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/advanced-content-modeling.md)

## Limiting where content editors can create pages

You can use the following approaches to limit where in the content tree can content editors create particular content only pages.

- [Allowed page type restrictions](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/limiting-the-pages-users-can-create.md#allowing-users-to-place-certain-pages-under-a-page-type) - by defining which page types content editors can place under the current page type.
- [Page scope restrictions](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/limiting-the-pages-users-can-create.md#specifying-which-pages-users-can-create-under-certain-paths) - by specifying which page types content editors can use when creating new pages under specified paths.

Using these approaches, you can set up a content structure in which each content only page type will have its own section.