---
title: Creating content only page types
related:
  - https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/creating-page-types.md
  - https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/creating-container-page-types.md
  - https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/limiting-the-pages-users-can-create.md
  - https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/extending-the-page-type-listing-filter.md
  - https://docs.kentico.com/k11/developing-websites/loading-and-displaying-data-on-websites/writing-transformations/creating-transformations-for-pages.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).

Content only page types are suitable for pages [on MVC sites](https://docs.kentico.com/k11/developing-websites/developing-sites-using-asp-net-mvc.md) whose only task is to hold content, such as individual news articles. Unlike standard page types, they don't have a representation on the website. Unlike custom tables, you can still use them to create a hierarchical data structure that supports workflow and versioning. Content only pages:

- Are not based on [page templates](https://docs.kentico.com/k11/developing-websites/managing-page-templates.md).
- Do not provide configuration options related to the live site presentation (such as navigation and URL properties).
- Do not have a presentation URL by default. You can [specify a URL pattern](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/specifying-the-url-pattern-for-content-only-pages.md) for the page type to allow content editors to display pages in preview mode via the administration UI.

## Creating content only page types

1. Open the **Page types** application.
2. Click **New page type**. A **New page type** wizard opens.

### Step 1

1. Fill in the values:
   - **Page type display name** - the system displays this name to users in the administration interface
   - **Namespace**: namespace distinguishes your page types from the default system types that use the _cms_ namespace. For example, you can use your site name as the namespace.
   - **Name** - page type identifier appended to its namespace

     ![Creating a content only page type](https://docs.kentico.com/docsassets/k11/creating-content-only-page-types/creating_page_type.png "Creating a content only page type")
2. Click **Next**.

### Step 2

1. Enter a **Table name** for the database table that stores the page type data.
2. Enter a **Primary key name** for the table.
3. (Optional) Select if you want the page to to **Inherit fields from** **page type**.
4. Enable **Content only page type**. 

   ![Creating a table for the content only page type](https://docs.kentico.com/docsassets/k11/creating-content-only-page-types/creating_tables.png "Creating a table for the content only page type")
5. Click **Next**.

The wizard creates the database table.

### Step 3

1. Click **New field** to define individual [fields](https://docs.kentico.com/k11/custom-development/developing-form-controls/reference-field-editor.md) of the page type (columns of the table).
2. For each field, enter the values, click **Save** and repeat the procedure until you have defined all the listed fields.
3. Click **Next**.

> **Note:** You can also define system fields that will be displayed when editing pages of this type on the **Form** tab. You can do this using the **Field type** drop-down list when creating a new field. Select **Page field** and you can then choose from the following two groups of system fields:
>
> - **Page fields** - offers system fields of pages.
> - **Node fields** - offers system fields of content tree nodes.
>
> Page or node system fields will then be offered in the **Field name** drop-down list. If you leave the **Display field in the editing form** check-box turned on, the field will be visible on the page's **Form** tab.

### Step 4

1. Choose the field that will be used as the name for pages of this type. Pages of this type will use the value of the field in site navigation and in the **Page** application's content tree. Only **Required** 'text' fields are available in the drop-down list.

   ![Selecting a source field for the page type name](https://docs.kentico.com/docsassets/k11/creating-content-only-page-types/selecting_source_field.png "Selecting a source field for the page type name")
2. Click **Next**.

### Step 5

Select the page types that will be supported as parents for pages of this type in the **Page** application's content tree.

1. Click **Add page types** and select a specific page type.
2. Click **OK**.
3. Click **Next**.

### Step 6

Assign the page type to all websites on which you want to use it.

1. Click **Add sites**.
2. Check the appropriate websites in the selection dialog.
3. Click **OK**.
4. Click **Next**.

### Step 7

The wizard has finished the configuration of the new page type. 

Click **Finish**. You have created a new page type. 

> **Tip:** Now, you may want to:
>
> - [Specify URL pattern for content only pages](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/specifying-the-url-pattern-for-content-only-pages.md) – to allow content editors to display content only pages on the live site and in the preview mode.
> - [Create transformations for the page type](https://docs.kentico.com/k11/developing-websites/loading-and-displaying-data-on-websites/writing-transformations/creating-transformations-for-pages.md) – to define how the page type's content is rendered on your pages.
> - [Create alternative forms for the page type](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/creating-alternative-forms-for-page-types.md) – to create alternative editing forms for the page type.
> - [Extend the page type's listing filter](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/extending-the-page-type-listing-filter.md) – editors use page listing to [perform multiple page (batch) operations](https://docs.kentico.com/k11/managing-website-content/working-with-pages/multiple-page-operations.md) in the **Pages** application.
> - [Limit the pages users can create](https://docs.kentico.com/k11/developing-websites/defining-website-content-structure/page-types/configuring-page-types/limiting-the-pages-users-can-create.md) – this way you can control where on the site users create new pages.

> **Info:** **How content in page types is stored**
>
> The new page type has its own database table for its specific fields. Each page is stored in three tables: _CMS\_TREE_ (tree structure), _CMS\_Document_ (page properties, metadata and content defined on the Page tab) and the custom table - for example, _CUSTOM\_Article._
>
> The system automatically ensures all operations are performed correctly on these tables. The advantage of this storage is that it is very fast and you can easily write standard SQL SELECT queries to retrieve data from the Microsoft SQL Server database.