---
title: Verify your product model with stakeholders
---

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

## Verify your product model with stakeholders

If your content modeling team includes specialist outsiders, you might want to create visual documentation that communicates your design decisions to all stakeholders. Use the [content modeling MCP server](https://docs.kentico.com/guides/architecture/content-modeling/content-modeling-mcp.md) to generate diagrams that visually represent your content model, making it easier for stakeholders to understand.

Develop content type diagrams that show _the structure of your product content type_, including fields, data types, and reusable field schemas used. Your team will need to see _relationship diagrams_ that illustrate how products connect to manufacturers, categories, variants, and other related content types. These visual maps help non-technical stakeholders understand the content architecture. Include diagrams that _document content creation flow_, explaining how editors will use the content model to build product pages, especially in complex scenarios, such as variant selection or multi-step product configuration.

The diagrams serve as essential references and help ensure everyone shares a common understanding of how the product catalog will function.

Collaborate with key teams across your organization to review the product model documentation, gather feedback, and validate that it aligns with business requirements.

- Developers need to verify technical feasibility, understand integration points with e-commerce platforms or inventory systems, and confirm they can build the necessary functionality.
- Commerce managers should validate that the model supports their merchandising strategies, pricing flexibility, and promotional capabilities.
- Marketing teams must ensure the model captures all content they need for campaigns, SEO, and customer engagement across channels.
- SEO/AEO/GEO specialists need to confirm that the required metadata, structured data, and content organization support search visibility and rich snippets.

Early reviews help identify potential issues before development begins and help reduce cost and effort of making changes later.

## Validate your content model and data fields

After designing your product content model, validate that it produces correctly structured data that search engines and external systems can understand.

Tools like Google's [Rich Results Test](https://search.google.com/test/rich-results) help ensure your [product data](https://developers.google.com/search/docs/appearance/structured-data/product) is correctly structured for optimal search engine display. [Schema.org's validator](https://validator.schema.org/) checks whether your structured data follows the correct format and includes required properties, helping you catch errors before implementation.

Review Schema.org's [JSON examples](https://schema.org/Product#eg-0010)
for products and test your system's output using the [JSON-LD playground](https://json-ld.org/playground/) to understand how properties combine in real-world scenarios.