WordPress Multisite in 2026: complete guide — use cases, configuration, pitfalls, and migration

WordPress Multisite has been around since WordPress 3.0 — yet we still see projects launching three separate installations when a single multisite network would do the job with a quarter of the maintenance.

In 2026, the debate is no longer "should we go multisite?" but "does my project really need the constraints of multisite?" Because yes, multisite has constraints: specific hosting requirements, plugin compatibility, complex caching, a single database that grows fast.

This guide draws from 50+ multisite migrations completed at Volade between 2024 and 2026. We share what works, what breaks, and how to avoid spending three sleepless nights fixing a corrupted wp_blogs table.

What WordPress Multisite actually is

WordPress Multisite lets you manage multiple sites from a single WordPress installation. One core, one database (with additional tables), one wp-content folder, shared plugins and themes.

Each subsite can have:

• Its own domain name (or subdomain)
• Its own users and roles
• Its own themes and plugins (selectively activated)
• Its own content (pages, posts, media)
• Its own settings

Network architecture

---

When to use Multisite (and when to avoid it)

5 cases where Multisite is the right choice

1. Blog or editorial site network — universities, media, local governments
2. Agency managing 10+ client sites — centralized update maintenance
3. SaaS / multi-workspace platform — each client has their own subsite
4. Network of WooCommerce stores — centralized logistics, separate catalogs
5. Simplified internationalization — fr.site.com, en.site.com, de.site.com

5 cases where Multisite should be avoided

1. A single site — why complicate things?
2. Sites with radically different extension needs — guaranteed plugin conflicts
3. Single client with enormous volumes — single database = single point of failure
4. Team without technical skills — multisite requires a competent admin
5. Critical incompatible plugins — some major plugins don't support multisite

---

Subdomains or subdirectories?

This is the first decision to make when installing the network.

Subdomain setup: site1.your-network.com

Subdirectory setup: your-network.com/site1/

---

Step-by-step configuration

1Server prerequisites

Before touching any code:

• PHP: 8.1 minimum (8.3 recommended in 2026)
• MySQL: 8.0+ or MariaDB 10.5+
• PHP memory: 256 MB minimum, 512 MB recommended
• Server: VPS or dedicated cloud — no shared hosting
• SSL certificate: wildcard for subdomains, single for subdirectories
• Cache: Redis + multisite-compatible plugin (WP Rocket or Litespeed)

2Enable network mode in wp-config.php

Add to wp-config.php, before the / That's all, stop editing! / line:

define('WP_ALLOW_MULTISITE', true);

Reload the dashboard → a new Tools → Network menu item appears.

3Install the network

1. Go to Tools → Network Setup
2. Choose subdomains or subdirectories
3. Follow the instructions: copy rewrite rules to wp-config.php and .htaccess / nginx.conf
4. Your wp-config.php will gain constants like:

define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', true);
define('DOMAIN_CURRENT_SITE', 'your-network.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

1. Log out and log back in — the UI now shows a super admin interface

:::callout-warning

Do not run this migration on a production site without staging. Enabling multisite changes URL structures and permalinks — every internal link must be verified.

:::

4Create and manage subsites

Once the network is active:

• Go to Network Admin → Sites → Add New Site
• Fill in the address, title, and admin email
• The new site appears in the list — you can access it directly

5Install network plugins and themes

• Network plugins: activated in Network Admin → Plugins — available to all sites
• Site plugins: installed at network level, activated per site
• Network themes: activated in Network Admin → Themes — each site can enable them

---

Multisite-compatible plugins in 2026

Fully compatible

Known issues or incompatible

---

Common pitfalls and how to avoid them

Pitfall 1 — Single database saturation

In multisite, all sites share the same database. If one subsite has 50,000 post revisions, it slows everyone down.

Solution: regular cleanup of revisions, transients, and orphaned tables with tools like WP-Optimize (multisite-compatible).

Pitfall 2 — Duplicated media

Each subsite has its own uploads/sites/{id}/ folder. Without sharing, identical files (logos, icons) are stored N times.

Solution: shared media plugin or a single CDN for common assets.

Pitfall 3 — Cache problems

Standard page cache doesn't differentiate between subsites. A user on site1 might receive site2's page.

Solution: WP Rocket with multisite support, or Redis segmented by site.

Pitfall 4 — Single-site to multisite migration

This is the riskiest operation. GUIDs, permalinks, content IDs — everything changes.

Solution: use our single-site to multisite migration guide with WP-CLI export/import.

Pitfall 5 — Role confusion

A super admin has access to all sites. A site admin sees only their own site. Users can have different roles per subsite.

Solution: clearly document who has access to what — a malicious super admin or compromised account is catastrophic.

---

Single-site to Multisite migration

Recommended method: WP-CLI

# Export the source site
wp export --dir=./exports/

# Add an empty subsite to the network
wp site create --slug=new-site --title="My new site"

# Import the content
wp import ./exports/wordpress.xml --url=new-site.your-network.com

# Re-attach media
wp media regenerate --yes

Manual method (without WP-CLI)

1. Create the empty subsite on the network
2. Export content from the source site (Tools → Export)
3. Import into the subsite (Tools → Import)
4. Check permalinks, images, menus
5. Manually install necessary plugins

Post-migration checklist

• All permalinks work (no 404s)
• Images display correctly (uploads/sites/{id}/ path)
• Contact forms actually send
• SSL certificates cover all domains
• SEO sitemap is updated
• 301 redirects are in place for old URLs
• Users can log in without errors
• Cache is purged across the entire network

---

Multisite and WooCommerce: specific precautions

WooCommerce is multisite-compatible, but with caveats:

---

What we take away

WordPress Multisite is a powerful tool, but not a light decision.

Make the right choice if: you manage 5+ similar sites with the same plugins and themes, you have the necessary server expertise, and the sites don't have radically different extension needs.

Avoid Multisite if: you have a single site, incompatible plugins, a non-technical team, or extreme performance needs on one site.

Our field verdict: since 2024, we migrated 50+ sites to multisite at Volade. Our successes are on networks of 5 to 50 similar sites. Our failures are on projects where "it was easier to put everything together" — it never is.

---

Article updated July 9, 2026. Sources: WordPress Multisite documentation, Volade field feedback (50+ migrations), WordPress Codex.