One dashboard, fifty sites—when WordPress multisite pays off
The warehouse district in Portland still smells like coffee roasters and wet cardboard at seven in the morning. Laptop open on a steel table, you’re staring at a single dashboard that controls fifty separate domains—same core, same updates, one login. Multisite was supposed to simplify everything.
WordPress multisite promised one dashboard for fifty sites—here’s when it delivers
Network admin mode centralises updates, users, and themes across dozens of WordPress installations—but the trade-offs aren’t obvious until you’re three sites in.
WordPress multisite turns a single installation into a network of independent sites that share the same codebase, plugin library, and user database. You update a plugin once, it propagates to all fifty sites. You register a user once, they can access any site in the network with the same credentials. The network admin dashboard sits above individual site dashboards, giving you controls that don’t exist in standard WordPress: bulk theme management, network-wide plugin activation, and centralised user roles that span domains.
The setup makes sense if you’re running a franchise network, a university with departmental blogs, or a media company publishing regional editions. It collapses when you need per-site customisation that conflicts with network rules—different payment processors, unique plugin configurations, or hosting environments that treat subdomains and subdirectories differently. Multisite enforces shared plugins and themes by default; deviating from that model requires either custom code or accepting that some sites will stay locked to network settings. And if one site in the network gets compromised, the attacker often gains access to the entire installation, not just the vulnerable property.
The decision hinges on whether your sites share more DNA than they differ. If forty-eight of your fifty properties use identical plugins, the same checkout flow, and the same user base, network admin saves you hours every week. If each site needs its own tech stack, multisite becomes a constraint dressed up as convenience. The dashboard itself is efficient—it just doesn’t solve problems you don’t actually have.
INFRASTRUCTURE
CDN purges claim instant propagation—here’s the real timeline
You hit “purge cache” in Cloudflare or Fastly, and the dashboard confirms instant invalidation. But visitors still see the old version of your landing page for three more minutes. CDN purge requests propagate to edge nodes at different speeds depending on provider architecture, geographic distribution, and whether you’re purging by URL or by cache tag. Some platforms queue purges during high traffic; others prioritise certain node clusters over remote regions. If you’re coordinating a product launch or fixing a broken checkout flow, “instant” can mean anything from five seconds to five minutes depending on where your readers sit relative to the CDN’s backbone.
MONETISATION
Your revenue dashboard tracks transactions but misses conversion paths
Most monetisation dashboards show you total revenue, subscriber count, and maybe a churn percentage. What they don’t show: the three-week nurture sequence that preceded the sale, the affiliate click that happened four days before checkout, or the refunded customer who re-subscribed two months later at a higher tier. Transaction-focused dashboards treat every sale as a discrete event, which makes month-over-month comparisons easy but hides the multi-touch reality of how people actually convert. If you’re trying to optimise your funnel, the highest-value conversions—those influenced by multiple sources—are invisible in standard reporting. You need attribution tooling that connects dots across sessions, not just a list of completed purchases.
ANALYTICS
When your traffic report only counts ten per cent of visitors
Google Analytics and similar platforms sample data when your traffic exceeds certain thresholds—typically 500,000 sessions in the selected date range. Instead of processing every event, the platform analyses a subset and extrapolates. That works fine for broad trends, but it skews granular reports: conversion rates on low-volume landing pages, attribution for campaigns with fewer than a hundred clicks, and funnel drop-off calculations that rely on precise session counts. You won’t always know sampling is active unless you check the report settings or notice that your raw event count doesn’t match the dashboard total. High-traffic operators hit sampling limits faster than they expect, especially when segmenting by source, device, or geography.
Know someone who would like this? Forward today’s email—every operator we reach is one closer to running an online business with a little less friction.