Good fit: schools and universities
Department, faculty and event sites under one domain and one IT team.
WordPress Multisite is a core feature that runs a network of many sites from one WordPress installation, sharing core files, plugins, themes and user accounts while each site keeps its own content and settings. It suits schools, chains and multilingual brands under one team; unrelated client sites are safer on separate installs.
For site owners, IT teams and agencies deciding whether one WordPress network or several separate installs suits their group of sites.
Last editorial update: 14 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
WordPress Multisite is a feature built into WordPress core that turns one installation into a network of many sites, all sharing the same core files, plugins, themes and user accounts while each site keeps its own content, media and settings. It ships switched off; an administrator enables it in wp-config.php and then runs Network Setup.
Think of it as one building with many flats. The structure, wiring and front desk are shared; each flat is furnished separately. A school can run a site per department, or a retail chain a site per outlet, and update WordPress once for all of them.
Multisite keeps every site in one database: network-wide tables hold users and the site list, while each site gets its own set of content tables numbered by site ID. Uploads follow the same pattern, so files for site 3 live under wp-content/uploads/sites/3/.
| Scope | Tables | What they hold |
|---|---|---|
| Network-wide | wp_users, wp_usermeta | One account list for every site |
| Network-wide | wp_blogs, wp_site, wp_sitemeta | The list of sites and network settings |
| Network-wide | wp_signups, wp_registration_log | New user and site registrations |
| Main site | wp_posts, wp_options and the rest | Content of site 1 |
| Each extra site | wp_2_posts, wp_2_options, wp_3_posts… | Content and settings of that site only |
Because everything shares one database, one backup captures the whole network — and one corrupted table or failed restore affects it all. The WordPress database guide explains the standard tables in more detail.
A Multisite network uses either subdomains (shop.example.in) or subdirectories (example.in/shop/) for its sites, chosen once during Network Setup, and any site can additionally be mapped to its own full domain. Changing between subdomain and subdirectory later is effectively a migration.
/blog/ prefix to avoid clashes, and WordPress offers only subdomains on an install older than about a month.*.example.in) and an SSL certificate that covers every subdomain.The subdomain vs subdirectory guide covers the SEO side of that choice.
The Super Admin controls the whole network — creating sites, installing plugins and themes, managing all users — while a Site Admin manages only the content and users of one site. A single user account can hold different roles on different sites in the same network.
| Action | Super Admin | Site Admin |
|---|---|---|
| Create or delete sites | Yes | No |
| Install plugins and themes | Yes | No |
| Network-activate a plugin | Yes | No |
| Activate an installed plugin on own site | Yes | Only if the plugins menu is enabled in Network Settings |
| Choose a theme | Enables themes for the network | Picks from the enabled set |
| Edit posts, pages and media | On any site | On own site |
Network-activated plugins run on every site, so keep that set to essentials such as security, cache and backup. One incompatible plugin activated network-wide breaks every site at once.
Use Multisite when many sites share one owner, one team and one set of rules; avoid it when sites belong to different owners or need independent backups, scaling or a clean exit.
Department, faculty and event sites under one domain and one IT team.
A site per outlet or city with identical branding and centrally approved plugins.
Hindi and English versions run as sibling sites; see multilingual WordPress in Hindi.
One client's plugin, breach or traffic spike reaches every other client, and extracting a leaving client is laborious.
Separate WooCommerce shops need separate backups, payment settings and resource limits.
For agencies, separate installs managed with automation usually cost a little more effort and far less risk; a reseller hosting account gives each client its own cPanel.
A Multisite network needs hosting that allows several domains or wildcard subdomains on one account, enough PHP memory and database capacity for all sites combined, and an SSL setup covering every address.
*.example.in. Let's Encrypt can issue one through DNS validation, or a Sectigo Positive SSL Wildcard costs ₹7,500 a year at WebJi®.Plans and limits are on WordPress hosting. The click-by-click enablement, including the WP_ALLOW_MULTISITE constant and Network Setup, is in how to set up WordPress Multisite; try it on a staging copy first.
Yes, but it takes work. You export that site's content, copy its uploads folder, recreate users and settings in a new install and rewrite URLs. Migration plugins with multisite support can automate part of it. Plan the exit before the network grows.
Not inherently, since each request loads one site. Problems appear when the combined traffic of every site exceeds the shared PHP workers or database, or a heavy plugin is network-activated. Object caching and adequate server resources keep a large network responsive.
Yes. WooCommerce can be activated per site, and each site keeps its own products, orders and payment settings. Products and carts are not shared between sites by default; sharing them needs extra plugins.
Only cleanly if the network still has just the main site. Once extra sites exist, you must move or delete them, then remove the multisite constants from wp-config.php and the rewrite rules from .htaccess. Keep a full backup before trying.
Last editorial update: 14 November 2026. Prices follow the dated sources on this page; checkout confirms current charges.
Join 12,000+ businesses across India and overseas. INR pricing, 18% GST shown before payment and 24/7 email support in Hindi and English — average first reply under 60 minutes.