Running multiple websites should not feel like spinning plates on a windy day. Yet for many organisations, that is exactly what it becomes. Different content teams, different hosting setups, different design systems, and often different agencies wrestling with slightly different versions of the same problem.
A well-planned multi-site configuration in Umbraco, version 10 and above, changes that entirely. Instead of running several separate websites, you run a single digital ecosystem, with all your sites managed through one secure, central platform.
This guide is written for marketing directors, digital leads, and product owners who want to understand how multi-site infrastructure works in Umbraco, why organisations use it, and what it takes to keep it running smoothly.
Let us break it down clearly and sensibly, without the technical noise.
What a Multisite Architecture Actually Is
A multisite architecture means running several independent websites from a single Umbraco installation. Each site has its own content tree, its own domain, and its own identity, but everything sits inside one codebase.
It feels like running multiple sites.
It behaves like running multiple sites.
But behind the scenes, you only maintain one platform.
You get one user login, one hosting environment, one update cycle, and one shared design system. It is efficient, cost effective, and far easier to govern than juggling multiple standalone CMS installations.
Who Actually Needs a Multisite Setup?
Many people assume multisite is only for organisations with multiple languages. That is one use case, but it is only the tip of the iceberg. Here are the scenarios where multisite becomes not just useful, but transformative.
1. Businesses with multiple regions or countries
If you operate in the UK, France, Germany, or other regions, you probably want:
- separate content
- separate editors
- separate marketing activity
- separate regulatory requirements
But still one consistent brand.
A multisite setup lets each region manage its own site without stepping on each other’s toes.
2. Organisations with several brands under one parent
If your organisation manages multiple brands, you do not need five CMS platforms. You need one well structured system that supports shared components, shared hosting, and shared governance, while still giving each brand room to breathe.
Multisite is ideal for brand groups, content-heavy sites, holding companies, and organisations with sub brands or group sites.
3. Businesses with different products or divisions
Sometimes a single website tries to say too much. If you have a B2B product, a B2C SaaS platform, and a partner programme, they probably deserve separate digital homes.
Multisite allows each to have its own identity without multiplying your technology overhead or needing to rework your content structure design.
4. Franchises, groups, and federated organisations
Franchise networks, churches, membership organisations, professional bodies, and charities often have dozens of local branches. Each branch needs autonomy, but head office needs consistency. Multisite provides both.
5. Marketing teams launching repeated microsites
Campaigns, competitions, seasonal events, product launches, corporate reports. These all benefit from dedicated landing sites. Multisite turns these from a technical project into a quick configuration job using familiar content types and document types.
6. Organisations with strict governance requirements
If your industry demands careful access control, especially where content has regulatory implications, multisite lets you assign permissions precisely. Each team can see only the site or media they own. This also makes user permissions much easier to manage across the organisation
7. Companies planning for growth
Even if you only have one site today, if you expect new brands, new regions, or new product lines in the next three years, starting with multisite in mind saves significant effort later.
Why Multisite Matters: The Real Strategic Benefits
Multisite is not just about convenience. It solves real operational problems.
One update works everywhere
Security patch? Do it once.
Umbraco upgrade? Do it once.
New design component? Build it once.
Suddenly your CMS is not five times the cost. It is one cost, shared efficiently.
Consistent design and shared components
A shared design system means you never have to rebuild the same hero banner, the same card component, or the same form multiple times. It also means every site stays naturally on brand.
Launch a new brand?
Launch a new region?
Launch a new microsite?
Everything is already in the system.
One login, clean governance
Umbraco’s permissions system lets you tailor access for each team.
If an editor logs in for the France site, we configure their Start Nodes so that they see only the France content section and only the media folders that belong to them. They cannot browse or edit content for the UK site because from their perspective it does not exist.
It is clean, safe, and significantly easier to train.
Faster time to market
If marketing wants a new microsite, you do not create a new CMS, new hosting environment, or new templates. You right click the content tree, choose a homepage, set a theme, and map a domain. You can even reuse elements like page navigation, a template name, and meta fields to speed things along.
A microsite that used to take three weeks now takes a couple of hours.
Lower hosting and maintenance costs
Several independent CMS platforms cost more to host, more to secure, and more to maintain. With multisite, you share infrastructure and resources, which almost always lowers cost and reduces overall resource usage.
How Multisite Works in Umbraco (Non Technical Explanation)
You do not need to know the technical details, but understanding the basic structure helps you plan effectively.
Root nodes
Each website lives under its own root node in the content tree. For example:
- Corporate Site
- France Site
- Germany Site
- Summer Campaign
- Careers Site
Each of these behaves as a completely separate front-end website.
Domains
Each root node is mapped to one or more website domains, such as:
- yourbrand.co.uk
- yourbrand.fr
- careers.yourbrand.com
- summer.yourbrand.com
Umbraco routes the right domain to the right content tree.
Shared components and templates
We build a library of reusable components used across all sites. If you want separate brand styling for certain sites, we can apply theme specific styling without fragmenting the codebase. Reuse of content pickers, block grids, and block types keeps things flexible but efficient.
Shared codebase
The entire ecosystem runs from one codebase, structured so that if one brand needs extra functionality, it does not affect the others. This is especially valuable for bespoke development work or when dealing with different business units.
Best Practice: How to Run a Multisite Setup Without Chaos
A multisite environment is powerful, but it can get messy without good habits. Here is how to keep it clean.
Use Start Nodes for content and media
This keeps editors focused on the areas they own and prevents mistakes.
Maintain a clean media library
Mirror your content structure:
- Global Shared Assets
- Corporate Media
- Regional Media
- Campaign Media
This keeps things tidy and prevents accidental use of region specific imagery across the wrong site.
Keep global and local content separate
Global content, such as footers and legal text, should live in a dedicated Global Data folder. Update it once and every site updates instantly.
Local content, such as blogs or events, stays within the individual content tree.
Keep naming conventions consistent
Clear naming across document types, components, and media ensures the system stays manageable long term.
Only share components that truly are universal
If something is unique to one brand, do not make it global. This avoids conflicts down the line.
When Multisite Might Not Be the Right Choice
Multisite is powerful, but not always the answer. It might not suit you if:
- Your brands are completely unrelated
- Each site needs a totally distinct system or design builder
- You need physical hosting separation for compliance
- Your existing CMS setup is heavily damaged by technical debt
In those situations, separate installations may be safer.
Common Mistakes Organisations Make
We have seen the same pitfalls many times:
- Allowing the media library to become a dumping ground
- Not defining clear user permissions
- Putting brand specific components in the shared library
- Mixing global content into local site trees
- Rushing the initial content modelling or content hierarchy
- Not thinking about scalability from day one
Avoid these and your multisite setup will stay clean and future proof.
Summary Table: Traditional vs Multisite
|
Feature |
Traditional Setup |
Multisite Setup |
|
Login |
One per site |
One central login |
|
Hosting |
Multiple servers |
One shared environment |
|
Upgrades |
Per site |
Single update |
|
Content Sharing |
Manual |
Native and instant |
|
New Site Launch |
Weeks |
Hours |
|
Governance |
Inconsistent |
Clean and controlled |
Ready to Explore Multisite in Umbraco?
If you are juggling multiple disconnected websites, brand inconsistencies, duplicated content, or slow campaign launches, a multisite setup could transform how your team works.
We can help you:
- Assess your current digital estate and digital evolution
- Plan a clean multisite architecture
- Build reusable components and structured content systems
- Train your editors on governance and best practice
If you want a simple, scalable, and future proof setup, let us take a look.