<p>I begin content modeling with editor questions. Which facts change together? Which copy must remain unique? Which page needs a relation instead of another text field? Those answers determine whether I use a collection type, single type, component, or relation.</p><p>The <a href="https://docs.strapi.io/cms/features/content-type-builder">Strapi Content-type Builder documentation</a> describes Strapi collection types, single types, components, and six relation shapes. I use those tools to express editorial ownership, not to mirror every frontend component.</p>

<h2>Start with editorial decisions</h2>

<p>I list the choices an editor makes for a service, location, and article. A service owns its offer, audience, process, and limitations. A location owns verified geographic facts and local contact context. An article owns its argument, sources, and publication metadata.</p><p>If editors cannot explain who owns a value, a shared component may hide duplication rather than solve it. I assign one source of truth before adding a relation.</p>

<h2>Use components for repeated shapes</h2>

<p>Components work well for structures that repeat inside several content types, such as an SEO field group or a visible question-and-answer item. The fields travel together, but the component does not exist as an independent record.</p><p>I avoid one giant page component with dozens of optional fields. Editors have trouble understanding it, APIs return noisy shapes, and validation becomes weak.</p>

<h2>Use relations for independent records</h2>

<p>A service and a location can exist independently, so I connect them with a relation. The relationship says that a service is available in a location; it does not create useful local copy by itself. The location page still needs a distinct purpose and evidence.</p><p>Blog posts can relate to services for internal links, but I keep the article's link text and context editable. An automatic card grid is different from a contextual recommendation inside the article.</p>

<h2>Protect against thin generated pages</h2>

<p>I do not publish every service-location combination. A record needs a defined audience, unique main copy, verified local facts, and a reason to exist beside the parent service page. Templates can enforce structure, but they cannot supply evidence.</p><p>I add a publication validation rule or editorial checklist that catches empty differentiators, duplicate metadata, and missing internal links before the frontend indexes a route.</p>

<h2>Plan API queries with the model</h2>

<p>Relations require deliberate population in Strapi 5. I decide which related fields each page needs and avoid recursive population that returns an oversized graph. Public queries select published fields; preview queries use protected credentials and draft status.</p><p>I test the rendered Next.js page, not only the JSON response. A technically correct relation can still produce duplicate headings or broken canonicals.</p>

<h2>Review change cost</h2>

<p>Renaming a field can make prior data inaccessible through the admin interface until it is migrated. I treat schema edits as data migrations with backups, a mapping, and a rollback plan.</p><ul><li>Each fact has one owner.</li><li>Components represent repeated shapes.</li><li>Relations connect independent records.</li><li>Location pages require unique evidence.</li><li>API population stays bounded.</li></ul>

<h2>Need help with Strapi?</h2>

<p>Terry Hunt Dev designs content models through <a href="/services/strapi-development">Strapi development services</a>. If your CMS has duplicate service or location fields, send the current content types through the <a href="/contact">contact page</a> after removing private records.</p>

See how I approach Strapi content modeling for services, locations, blog posts, reusable components, relations, and safeguards against thin pages.

How I Model Services, Locations, and Blog Content in Strapi

Model services, locations, and articles in Strapi without duplicating facts or generating thin location pages.

SEO Resources & Benchmarks

How I Model Services, Locations, and Blog Content in Strapi

Need hands-on help with SEO?