Cleanly separating multiple business units on one domain

How do you separate business units on a single domain without losing their shared strength?

Each business unit receives a clear entry point, defined page types, and recognizable local navigation. Common themes remain and are linked contextually from within the units.

Common Core

• Common Core – Brand, organization, and overarching principles share a central source to which all units clearly refer.

• Dedicated Entry Point – A hub explains the offering, target group, and substructure of the area without re-creating shared content as a copy.

• Clear Overlap – For each shared topic, it is defined whether it remains central or requires a separate, subject-specific area-specific version.

Dedicated Entry Point

1. Central entities and content are initially inventoried separately from area-specific offerings, tasks, and target groups.

2. A hub, permissible page types, and rules for navigation, naming, and shared content are created for each area.

3. Cross-functional user paths are then checked to ensure that transitions remain clear and that no competing pages serve the same need.

Clear Overlap

• Content-wise competing pages from different areas with the same purpose or largely the same message.

• User journeys between areas where the origin, next step, or relationship to the shared brand remains unclear.

Duplicate foundations

• Duplicate foundations – Each area publishes similar explanations, which later persist with differing statements and update levels.

• Invisible boundary – Navigation and naming change midway through the user journey without clarifying the origin or relationship of the new area.

• Organizational chart as structure – Internal departments determine the website, even though offerings and user inquiries span multiple areas of responsibility.

Case Study: "Duplicate Foundations"

Two service areas share a central methodology page but have their own offering hubs with different tasks. Both hubs link the common foundation within their respective contexts; therefore, changes to the process only need to be approved in one place.

How "Organizing Business Units on a Domain" relates to other topics

An in-depth question answered Change URL structures without disrupting the content logic.How to Change URL Paths Without Losing Relationships, Rankings, or User Entry Points?

Further Perspectives Structuring an Editorial System for Multiple Brands or Domains.

If you want to practically implement "Organizing Business Units on a Domain," you can refer to Robust Website Systems This article focuses on "Page Types and Content Model" and "Common Core."

Conclusion: Organizing Business Units on a Domain

Units are separated by clearly defined tasks and connected via shared entities. A domain gains strength when overlaps are consciously modeled rather than duplicated.

Sources and Further Information

The following official documentation and standards provide the technical classification.

• Organize and group GOV.UK contentThe official GOV.UK guidance describes user-related content groups, naming conventions, and hierarchies, rather than organization-driven filing.

• Learning about users and their needs – GOV.UK Service ManualThe guideline justifies observed tasks and needs as the starting point for structural decisions. ...2: The primary sources define the professional framework for "Creating a binding content map."