---
title: Naming conventions and organization
---

> 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).

## Naming conventions and organization

### Organize your content tree thoughtfully

Place _wrapper pages_ in a logical site structure such as `/products/[category]/[product-name]`. Use folders to group related products. In the _Content hub_, organize products using [content folders](https://docs.kentico.com/documentation/business-users/content-hub/content-hub-folders.md), [smart folders](https://docs.kentico.com/guides/development/advanced-content/deliver-content-dynamically-with-smart-folders.md) that automatically organize items by criteria, or [workspaces](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/workspaces.md) to separate products by business unit or team.

### Establish consistent URL patterns

Use a predictable structure like `/products/[category]/[product-slug]` so visitors and search engines can understand your site hierarchy. Use the [alternative URLs](https://docs.kentico.com/documentation/business-users/website-content/manage-page-urls.md) feature to handle redirects when you reorganize content. Use the canonicalization feature to indicate the primary URL when the same product appears on multiple pages or channels.

### Follow clear naming conventions for content items

Establish clear naming patterns for the editor teams.

Editors need to name their products clearly and descriptively to help with discovery across the system, especially if different teams manage different presentation layers: _Business Checking Account_, _Striped Grey T-shirt_, and _Professional Dog Grooming Kit._

Name _product (wrapper) pages_ to match the product name or add channel context: _Business Checking Account - Website_, or just _Business Checking Account_. When you have product variants, include a distinguishing suffix in the content item name: _Striped Grey T-shirt - S_, _Striped Grey T-shirt - M_.