WordPress Multisite Support

Cyclone Static supports WordPress Multisite networks on Business and Agency plans. Network activation sets up each site in the network independently — every site gets its own cache directory, its own .htaccess block, and its own queue. Sites on the same network cannot interfere with each other’s cache.

Personal plan licenses cover a single site and cannot be used on a Multisite network. If you activate Cyclone Static on a Multisite network with a Personal license, the plugin will display an upgrade notice and deactivate itself network-wide.

Multisite Network Types

WordPress supports two Multisite configurations:

• Subdomain networks — each site has its own subdomain: site2.example.com, site3.example.com
• Subdirectory networks — each site lives under a path: example.com/site2/, example.com/site3/

Cyclone Static handles both types correctly.

Network Activation

When you activate Cyclone Static network-wide (Network Admin → Plugins → Network Activate), Cyclone automatically:

1. Sets up a cache directory for each site in the network
2. Writes .htaccess rules for each site
3. Creates a queue table for each site (if needed)

Existing sites are fully configured at activation time. New sites added to the network after activation are also configured automatically — when a new site is created, Cyclone detects it and sets up the cache directory and .htaccess rules immediately.

Per-Site Cache Directories

Each site in a Multisite network gets a dedicated cache subdirectory:

• Main site: wp-content/cyclone-static/ (default)
• Subsites: wp-content/cyclone-static/sites/2/, wp-content/cyclone-static/sites/3/, etc.

The subsite number corresponds to WordPress’s internal blog ID. You can find a site’s blog ID in Network Admin → Sites — it appears in the URL when you click to edit a site (.../wp-admin/network/site-info.php?id=2).

This separation means a cached page at example.com/about/ and a cached page at site2.example.com/about/ (or example.com/site2/about/) are stored in completely different directories and can never overwrite each other.

Per-Site .htaccess Rules

Subdirectory Networks

On subdirectory networks, all sites share a single .htaccess file in the WordPress root. Cyclone writes a clearly marked block for each site:

# BEGIN Cyclone Static
... rules for the main site ...
# END Cyclone Static

# BEGIN Cyclone Static site-2
... rules for site 2 (example.com/site2/) ...
# END Cyclone Static site-2

Each block’s rules reference that site’s specific cache directory and URL path prefix, so requests for example.com/site2/about/ only match site 2’s cached files.

Subdomain Networks

On subdomain networks, each site typically has its own document root and its own .htaccess file. Cyclone writes a single block in each site’s .htaccess. Rules for subdomain subsites include a hostname condition:

RewriteCond %{HTTP_HOST} ^site2\.example\.com$ [NC]

This ensures requests for site3.example.com never match rules written for site2.example.com, even if the two sites share a .htaccess file due to server configuration.

Managing Individual Sites

Network administrators can manage the entire network from the Network Admin. Individual site administrators manage their own site through the normal WordPress admin at example.com/site2/wp-admin/.

Each site’s Cyclone Static Dashboard shows only that site’s stats — its own queue depth, cached page count, and cache size. Action buttons (Generate All, Discover from Sitemap, Clear All Cache) operate only on the current site.

Cyclone Static settings are per-site. Site 2 can use a different CDN provider than Site 3. Batch sizes and throttle delays are configured independently per site.

Removing a Site from the Network

When a site is deleted from the Multisite network, Cyclone automatically:

• Removes the .htaccess block for that site
• Removes the site’s cache directory (and all static files in it)
• Removes the site’s queue entries

This cleanup happens immediately when the site deletion is processed. No manual intervention is required.

Network Deactivation

Deactivating Cyclone Static network-wide removes all .htaccess blocks from all sites, stops all background processing, and leaves each site’s static files on disk in case you reactivate. Static files are not deleted on deactivation — only the .htaccess rules that serve them are removed, so all sites immediately fall through to live WordPress.

Upgrading Plans for Multisite

If you currently have a Personal plan and want to enable Multisite support, upgrade to the Business or Agency plan through your account on the Cyclone Static page. After upgrading, deactivate and reactivate the plugin on your network — Cyclone will detect the new license tier and complete the Multisite setup.