---
title: Content governance considerations for commerce pages
---

> 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 governance considerations

When you configure your [content item selectors](https://docs.kentico.com/documentation/developers-and-admins/customization/extend-the-administration-interface/ui-form-components/reference-admin-ui-form-components.md#combined-content-selector), limit the allowed content types to only the content types that should be referenced. For your _Product page_, configure the _Product_ selector to accept only _Product_ content types (or specific product variants). This prevents editors from accidentally selecting the wrong content type.

For example, the following image shows that Kbank's editors can select only product-specific content types, such as _Loan_, _Account_, _Card_, or _Insurance_, into the _Product_ page thanks to the selector's configuration.

![Product content item selector on Kbank demo site](https://docs.kentico.com/docsassets/modules/model-commerce-pages-governance-considerations/kbank_product_content_item_selector_product_page.png "Product content item selector on Kbank demo site")

> **Info:** **Pattern takeaway:** Prevent invalid relationships at authoring time by defining constraints on the content item selector.

### Provide clear guidance for editors

Use descriptive field captions, like _Select product_, rather than just _Product_. Add helpful descriptions below the selector, such as _Choose the reusable product this page will showcase_. Include explanations about the content and its format to guide proper usage in all other fields.

The following image shows the product selector on the Kbank demo site. The page selector's additional description tells editors to _Select reusable Product item (Account, Loan, or Card) to display on your website._, leaving little room for doubt.

![Guidance below a selector in the Kbank's product page](https://docs.kentico.com/docsassets/modules/model-commerce-pages-governance-considerations/kbank_account_page_selector_editor_guidance.png "Guidance below a selector in the Kbank's product page")

> **Info:** **Pattern takeaway:** Strong field captions and helper text improve editorial consistency and reduce training overhead.

> **Tip:** You can use the Xperience [Content modeling MCP server](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-mcp.md) to generate clear, editor-friendly labels and descriptions that your UX team can iterate over and improve.

### Establish ownership and [workflows](https://docs.kentico.com/guides/digital-marketing/work-with-workflows/workflows.md) before you start building content

Decide who manages the reusable _Product_ content items. Typically, this is a _product team_ or _merchandising team_ that owns the core product information, or _data entry specialists_ who work closely with the _product team_. Decide who manages _product wrapper pages_. This is usually your _marketing team_ or _web content editors_ who control channel presentation and SEO.

The following image shows a product page approval workflow with three steps. Different stakeholders, such as content editors, product managers, and administrators, need to approve the page content before it's published to the live site.

![Demo workflow created on Kbank website](https://docs.kentico.com/docsassets/modules/model-commerce-pages-governance-considerations/kbank_product_page_workflow.png "Demo workflow created on Kbank website")

> **Info:** **Pattern takeaway:** You can separate ownership and approval workflows for reusable product data versus wrapper pages to reduce publishing risk.

### Plan your permissions and access structure

Use [workspaces](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/workspaces.md) to organize content by team or business unit. For example, you can configure role permissions for each content type so the _product team_ can edit _Products_ but only view _website pages_, and the marketing team can edit _wrapper pages_ but only view _Products_. To manage access to website pages, use the [page level permissions](https://docs.kentico.com/documentation/developers-and-admins/configuration/users/role-management/page-permission-management.md).

As shown in the following image, editors on the _Business Banking_ team can work only with content items that target their customer persona: _B2B representatives_. All products, product components, and articles filtered in the _Content hub_ view fall under their business domain.

![Business Banking workspace on Kbank demo site](https://docs.kentico.com/docsassets/modules/model-commerce-pages-governance-considerations/kbank_workspace_config_business_items.png "Business Banking workspace on Kbank demo site")

> **Info:** **Pattern takeaway:** Use workspaces and role-scoped access to align content ownership with business domains and editorial responsibilities.

> **Tip:** Test your permissions structure early by having team members from different roles create sample content items. This helps you identify permission gaps or workflow issues before you roll out the model to your full content team.

### Understand publishing dependencies

When you publish a wrapper page that references an unpublished _Product_, you may need [cascade publishing](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md#cascade-publishing) to publish all items together. When you update a reusable _Product_, remember that the changes will appear on every wrapper page that references it. Establish a [notification process](https://docs.kentico.com/guides/digital-marketing/work-with-email/notifications-basics.md) so teams know when shared content changes.

The following image shows a product page with all the unpublished content items this page references. Xperience [cascade publishing](https://docs.kentico.com/documentation/business-users/content-hub/content-items.md#publish-content-items) allows publishing of all related content at once.

![Kbank product page with linked items shows publishing cascade](https://docs.kentico.com/docsassets/modules/model-commerce-pages-governance-considerations/kbank_publish_cascade_product_page.png "Kbank product page with linked items shows publishing cascade")

## Multilingual considerations

When working with multilingual content, you need to decide what to translate and what to keep language-neutral. You can use [AIRA translations](https://docs.kentico.com/guides/digital-marketing/work-with-multilingual/optimize-aira-translation-prompts.md) to prepare content in different languages and then hand off different parts of the _wrapper page_ to different editor teams via [workflows](https://docs.kentico.com/guides/digital-marketing/work-with-workflows/workflows.md).

One editor team might need to validate SEO metadata (_title_ and _description_) for each language to ensure search results display correctly across markets. Social media managers might need to review translated Open Graph metadata to ensure social sharing displays properly in each language. Editors might need to customize the translation of language-specific CTAs and promotional text that appear only on that channel. Additionally, a product team might want to verify the translated _product data_ in the _Content hub_.

Some content typically stays language-neutral. Core product data may or may not require translation depending on your markets and products. Product specifications often remain universal across languages. Product SKUs, prices, and technical specifications usually don't need translation unless you have market-specific products.

Use Xperience's [language fallback](https://docs.kentico.com/documentation/developers-and-admins/configuration/languages.md#language-fallbacks) feature appropriately. When a linked content item doesn't have a translation in the target language, Xperience shows a yellow border warning in the editing interface. Decide whether to use the fallback language for untranslated linked items or require full translation before publishing in each language.