WordPress multisite on shared

WordPress multisite on shared hosting runs many sites from one WordPress install, one database, and one cPanel account. It suits related microsites for a single company that can share backups and limits. It is a weak choice when each site is a separate business that needs its own restore point and failure boundary.

What one network actually shares

On shared hosting you get cPanel, LiteSpeed, and a CloudLinux LVE cap with no root access. Multisite still uses one Unix user, so every site draws from the same CPU, memory, and disk pool. WordPress keeps network tables such as wp_blogs and wp_site, then per-site tables like wp_2_posts and wp_3_options. You have one wp-config.php, one set of AUTH keys, and one JetBackup of the whole network. A fatal plugin error at the network level can take every site down together. Customers who need their own backups and a smaller blast radius should use separate WordPress installs, which WP Toolkit can add as far as the account allows.

Pick subdirectory, subdomain, or mapped domains early

Subdirectory sites use paths such as example.com/site2 and depend on rewrite rules. Subdomain sites such as site2.example.com need DNS, either a wildcard A record or clear individual names, and they change how cookies work. Mapped customer domains need DNS at each registrar plus domain mapping inside WordPress. Choose that layout before you enable multisite on a live site. Switching later usually means a careful search-replace and a longer maintenance window.

Enabling multisite only to park many unrelated customer domains on one LVE is the common failure. One busy shop can starve the others because CloudLinux still sees a single user, not separate brands.

SSL, cron, and user roles

AutoSSL with Let’s Encrypt can cover the primary domain and subdomains that already resolve to the account. Mapped domains must point DNS here first or certificates will not issue cleanly. The network often shares one wp-cron run, so scheduled posts and jobs may not behave the way each site owner expects. A super admin can change the whole network; give day-to-day users roles that cannot install network plugins or themes.

Related microsites for one organization can stay simpler on multisite. Agency farms, resold “unlimited sites,” or shops that must not share a fatal error belong on separate installs. Match the blast radius to how the businesses actually operate, rather than flipping a constant in wp-config because it sounded advanced.