---
title: Settings - Content
---
> 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).
| Page not found | |
| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Page not found for non-published documents | If checked, documents that are not published return a Page not found error (404) if they are viewed on the live site. |
| Page not found URL | Specifies a custom page that will be displayed to users who encounter a _Page not found_ error (404 HTTP status code). It can either be a physical aspx file in the web project or a dedicated document created in the site's content tree.
In both cases, you need to enter the URL of the page, for example:
_\~/SpecialPages/PageNotFound.aspx_
This value could be used to specify the URL of a physical page file placed in the given location, or select a document with an alias path equal to _/SpecialPages/PageNotFound_.
The advantage of using a document for this purpose is that you can leverage all features of the portal engine. For instance, you can translate the page not found document on a multilingual website and the system will automatically display the appropriate culture version according to the currently selected language. |
| Log page not found exception | If enabled, the system logs Page not found (404) http errors in the **Event log** application. You can recognize the errors by the "PAGENOTFOUND" event code. |
| Multilingual | |
| Default content culture | Used to select which culture should be the default language option of the website's content. |
| Combine with default culture | Indicates if the default culture version of documents should be offered for documents that are not available in the currently selected language. |
| Combine files with default culture | Indicates if the default culture version of files should be used for untranslated file documents. |
| Web site content | |
| Default alias path | Alias path of the website's default page. |
| Metadata | |
| Page key words prefix | Specifies a prefix for all page keywords on the website. |
| Page description prefix | Specifies a prefix for all page description on the website. |
| Page title format | Specifies the page title format.
Example: _{%prefix%} - {%pagetitle\_orelse\_name%}_ |
| Page title prefix | Page title prefix used for all pages. Replaces the {% prefix %} macro in the page title format. |
| Control element | Specifies the element that should be used instead of the standard element. Currently, the only options are span or div. |
Related pages
- [Multilingual websites](https://docs.kentico.com/k8/multilingual-websites.md)
- [Creating custom error handling pages](https://docs.kentico.com/k8/securing-websites/developing-secure-websites/handling-error-messages-securely/creating-custom-error-handling-pages.md)