How to manage a multisite network
On a WordPress multisite network, see caching across every site from one place — and understand why the panel does nothing on a single-site install.
A multisite network is many sites sharing one WordPress install, and checking each one’s cache separately gets tedious quickly. This panel aggregates them. On a single-site install it has nothing to aggregate, and says so plainly.
Where to find it
- In your WordPress admin, click xSpeed Cache in the left menu.
- In the xSpeed Cache sidebar, open the Settings group.
- Click the Multisite card.
Shortcut: open
wp-admin/admin.php?page=xspeed#/settings/multisitedirectly.⭐ This panel is part of xSpeed Pro.
- Install type — what the panel detected.
Settings at a glance
| Element | What it shows |
|---|---|
| Install type | Whether this is a multisite network or a single site. |
| Network view | On multisite, per-site caching status aggregated in one place. |
How it works
The panel detects your install type and adapts. On a single-site install it shows exactly what the screenshot above shows:
“This module only applies to WordPress multisite networks. On a single-site install there’s nothing to aggregate — use the regular dashboard.”
That’s the whole panel in that case, and it’s the right behaviour. Rather than presenting controls that would do nothing, it tells you where to go instead — the regular dashboard, where every other panel in this documentation lives.
On a multisite network, it becomes the network-level view: caching status across sites in one place, rather than switching into each site’s admin in turn.
💡 Seeing the single-site notice isn’t a fault. It means WordPress multisite isn’t enabled on this install — which is true of most WordPress sites. Nothing is misconfigured and there’s nothing to fix.
Is this multisite?
If you’re unsure, a multisite network has a Network Admin menu in the top-right admin bar and a My Sites menu. It’s enabled by adding define( 'WP_ALLOW_MULTISITE', true ) to wp-config.php and completing the network setup — a substantial architectural decision, not a setting you’d have switched on by accident.
Everything else in xSpeed works identically either way. This panel is the only one whose behaviour depends on it.