marketing
marketing.acme.com
Service Multisite
WordPress multisite that survives at network scale.
Network architecture, domain mapping, network plugins, object cache, backups. Built by a team that has run multisite networks at the 100+ site scale for over a decade.
WordPress agency since 2013, 100+ plugins shipped
Why multisite
Multisite is the right answer when one team runs many sites.
Franchise networks, agency client sites, multi-brand portfolios, university department sites, education networks, member intranets. One WordPress install, hundreds of sites, one admin team, one deployment pipeline. The architecture pays for itself the first time you push a security patch network-wide in five minutes instead of five days.
The catch is that multisite has sharp edges. Wrong topology choice locks you in for years. Cache misconfiguration burns the database. Plugin compatibility surprises break sites in production. We have hit those edges enough times to know how to avoid them.
A network at a glance
Twelve sites. One codebase. One deploy.
The network operations view we ship with every multisite engagement. Each tile is a sub-site with its WordPress version, current status, and 24-hour traffic. One site is mid-update. Scroll up and back down to replay the network sync.
store
store.acme.com
docs
docs.acme.com
support
help.acme.com
blog
blog.acme.com
events
events.acme.com
careers
careers.acme.com
press
press.acme.com
community
community.acme.com
partners
partners.acme.com
labs
labs.acme.com
app
app.acme.com
- Single codebase · `wp-cli site list` style operations across the whole network
- Domain mapping automated · SSL provisioned per-site at deploy
- 12+ multisite networks in production across the portfolio
What we build
Multisite networks that scale without surprises.
Network topology picked deliberately. Object cache configured properly. Plugins network-aware from the first install. Domain mapping automated. Backups tested. Operations scripted.
01
Network architecture done right
Subdomain, subdirectory, or mapped domains. We pick the topology in discovery based on SEO strategy, content sharing requirements, and tenant isolation needs. Wrong topology forces a painful migration later.
Network scales to hundreds of sites without rework.
02
Network plugins with proper context
Plugins that detect network activation correctly, namespace database tables per blog, and use switch_to_blog() safely. No memory leaks, no cross-site data bleeds, no admin notices that show on the wrong dashboard.
Plugins behave consistently across every site.
03
Object cache keyed per site
Redis or Memcached configured with per-blog cache key salts. No cache pollution between sites. switch_to_blog() flushes the right cache groups. Object cache hit rate stays above 95% network-wide.
Network performance holds at 100+ sites.
04
Per-site domain mapping
Customer-facing sites with their own domains, all served from one WordPress install. Cloudflare or LiteSpeed for SSL termination at scale. Wildcard DNS, automated cert provisioning, no per-site SSL tickets.
New customer sites go live in minutes, not days.
05
WP-CLI scripted operations
Network-wide operations through WP-CLI. Plugin updates rolled out staggered. Search-replace across all sites. User cleanup, transient cleanup, autoload audit. We script the operations, you run them on a schedule.
Network maintenance scales without proportional ops time.
06
Backup and restore strategy
Network-wide backups that work. Per-site restores that do not break the network. Database snapshots that include the right tables. Tested restore drills before go-live, documented runbook for the on-call person.
Disaster recovery actually works when needed.
100+
WordPress plugins shipped, including network-aware enterprise plugins
Multisite tested. Network activation handled correctly. Source on WordPress.org and GitHub.
Process
How a multisite engagement runs.
01
Discovery
One to two weeks. Topology decision (subdomain or subdirectory or mapped), plugin compatibility audit, performance baseline, backup strategy, SSL plan. Output is fixed price quote.
Architecture locked before code starts.
02
Build or migrate
Four to twelve weeks depending on whether you are starting fresh or migrating from separate installs. Performance tuned at every milestone. Staging network available within seven days.
No surprises at cutover.
03
Cutover and document
One to two weeks. DNS flip, SSL provisioned, monitoring active, runbook documented for ops team. We watch the network closely for thirty days.
Production starts stable.
Common questions
Frequently asked
-
When should we use multisite vs separate WordPress installs?
Multisite when sites share users, content, branding, or a centralized admin team. Separate installs when sites have totally different plugin stacks, different release cycles, or different security postures. Most multi-brand companies want multisite. Most reseller hosts want separate installs.
-
Subdomain or subdirectory?
Subdomain (sub.example.com) for clear tenant separation, easier migration to standalone later, and simpler SEO segmentation. Subdirectory (example.com/sub/) for SEO consolidation under one domain. We pick the topology in discovery based on the SEO strategy.
-
Can we map customer domains to network sites?
Yes. WordPress core supports domain mapping out of the box since 4.5. We configure wildcard DNS, set up Cloudflare or LiteSpeed for SSL termination, and automate cert provisioning so new customer sites go live without manual cert work.
-
Do plugins like WooCommerce, LearnDash, BuddyPress work on multisite?
Most do. WooCommerce supports network activation but is happiest with per-site activation. BuddyPress runs as a network-wide social layer or per-site community. LearnDash runs per-site. We test plugin compatibility in discovery and document the activation strategy.
-
How do we handle network-wide plugin updates?
Staggered rollout through WP-CLI scripts. Update on a canary site first, monitor for errors, then roll out network-wide. Same pattern for theme updates and core updates. We document the rollout procedure as part of handover.
-
What does it cost?
Multisite consultation and setup are scoped per project. Full multisite migrations from separate installs are scoped after discovery depending on site count and complexity. Network plugin development quoted separately. Discovery call is free.
Need multisite that scales?
Tell us what you want to build.
Discovery call is free. Fixed-price quote within 48 hours. Projects are scope-dependent.