Laddar

← Back to list

WordPress Multisite vs SiteAdmin: Managing Multiple Websites

Two ways to manage multiple websites from the same platform.

WordPress Multisite enables running multiple websites from a single WordPress network, while SiteAdmin offers a different approach: each website is independent, but multiple websites can be managed from a unified customer profile and admin panel.

When an organization, agency, or reseller needs to manage multiple websites, a unified administration emerges as a necessity. Logging into each site individually can become cumbersome.

WordPress offers a dedicated feature called Multisite, while SiteAdmin adopts a different architecture where websites are standalone but can be centrally managed from the same platform.

The end result may appear similar from the user’s perspective, but the underlying mechanics differ.

What Is WordPress Multisite?

WordPress Multisite allows creating multiple websites within a single WordPress network.

Instead of installing and managing each WordPress website as a separate system, multiple websites can reside under one installation and be managed via a shared network administration.

This is useful for organizations with numerous similar websites, schools, companies with multiple ventures, or networks requiring consistent technical foundations across many sites.

Multisite also enables centralized management of certain aspects, such as users, themes, and plugins, while each website retains its own content and configuration.

SiteAdmin Uses Separate Websites

SiteAdmin does not feature a Multisite setup. Instead, each website is a separate SiteAdmin website.

The core principle is simple:

    1 license = 1 website
  

A customer profile can, however, host multiple websites, all displayed in the My Websites section.

This means you can manage:

    Customer Profile
│
├── Company’s Website
├── Campaign Site
├── Subsidiary’s Website
└── Internal Website

Each website has its own content, design, menus, settings, and domain.

Separate Websites with Central Administration

The key difference from WordPress Multisite is clear: SiteAdmin does not merge multiple websites into a single installation. Instead, they are consolidated in the admin panel.

In the My Websites

section, users can view all accessible websites, including screenshots, status, and website information.

If a user has access to multiple customer profiles, they can switch between them and access the websites belonging to each profile.

This ensures that centralized administration does not require the websites to be technically linked.

Each SiteAdmin Website Is Independent

A SiteAdmin website does not automatically share content, design, or settings with other websites on the same customer profile.

This means, for example, that a menu change on one website does not affect another.

The same applies to content and design. Websites remain separate and can develop and modify independently.

This is beneficial when websites belong to different companies, brands, or customers and should not influence each other.

Separate Does Not Mean Isolated

While websites are separate, they do not have to remain completely disconnected.

Just as WordPress websites can integrate via APIs, SiteAdmin websites can communicate through the SiteAdmin API when such integration is built.

For example, a solution could retrieve data from one website or service and use it on another:

    SiteAdmin Website A
↓
SiteAdmin API
↓
SiteAdmin Website B

This is different from automatic content sharing. Separation remains, and integration requires building the data flow explicitly.

The SiteAdmin API is still under development, but the foundation exists and is already used within the Zethron platform. However, general content requests are not yet fully implemented.

Multiple Websites for Resellers

The model also suits resellers and agencies managing multiple customers’ websites.

A reseller can have their own websites and access their customers’ websites from the same platform.

For example:

    Reseller
│
├── Own Websites
│
├── Customer A
│ ├── Website 1
│ └── Website 2
│
├── Customer B
│ └── Website 3
│
└── Customer C
├── Website 4
└── Website 5

The websites displayed depend on the customer profiles and websites the user has access to.

This provides a centralized overview without requiring customers’ websites to be in the same technical installation.

WordPress Multisite vs Separate Websites?

Area WordPress Multisite SiteAdmin
Multiple Websites Yes, within the same network Yes, as separate websites
Technical Foundation Shared WordPress installation Separate SiteAdmin websites
Administration Shared Network Admin Shared platform administration
Content Between Websites Normally separate per website, but can be integrated Separated between websites
Design and Settings Managed at network level and per website Separate per website
Licensing Depends on WordPress installation and used services/plugins 1 license = 1 website
API Integrations Yes Yes, via SiteAdmin API where available
Resellers Can be built with various solutions Built-in handling of own and customers’ websites

Two Ways to Solve the Same Problem

WordPress Multisite is a powerful solution when multiple websites must belong to the same WordPress network. The shared technical foundation can be a significant advantage when many websites need consistent administration.

SiteAdmin, on the other hand, prefers to keep websites separate and consolidate the common aspects within the platform itself. You get centralized administration without automatically mixing content and configurations.

This also allows a customer to have multiple websites without needing to think of them as a single technical installation.

WordPress Multisite consolidates multiple websites into a single network. SiteAdmin consolidates separate websites into a unified administration.

Which model suits you best depends on your needs. If you want websites to share a technical foundation and be managed at a network level, WordPress Multisite is ideal. If you prefer separate websites with centralized management, SiteAdmin’s approach is another way to address the same overarching requirement.