WordPress Multisite Network Setup: Turnkey Solution

Managing a network of 50 sites requires a unified system. With separate installations for each site, administration takes 3–5 times longer: 50 core updates, 50 copies of plugins, 50 databases. WordPress Multisite (WPMS) lets you run an unlimited number of sites from a single installation with a single database. It's not just "multiple sites on one server" — it's a complete separation of infrastructure with a single core. Suitable for media networks, multi-regional projects, SaaS platforms on WordPress, educational portals. Basic setup of a network of 3–5 subsites takes 2–3 days; customization for production with data isolation and custom plugins takes from 5 days. Over 8+ years, we have delivered 50+ Multisite projects, including networks with 100+ subsites. Many face issues with user synchronization, updates, and content — Multisite solves them with one solution. Each project undergoes load testing and Core Web Vitals optimization. Contact us for a detailed audit of your current architecture.

How to Enable Multisite?

Add the constant to wp-config.php before installation:

define('WP_ALLOW_MULTISITE', true);

After that, the "Network Setup" item appears in the "Tools" menu. According to WordPress Codex, the constant must be added before installation. Here is a step-by-step guide:

1. Open wp-config.php and insert the line above before the line /* That's all, stop editing! */.
2. Go to Admin > Tools > Network Setup.
3. Choose addressing type: subdomains or subfolders.
4. Copy the generated code and add it to wp-config.php and .htaccess (or nginx.conf).
5. Restart the server.

Comparison of Addressing Types

Wildcard SSL for *.example.com is obtained via Let's Encrypt with DNS-01 challenge. For example:

certbot certonly --manual --preferred-challenges dns \
  -d example.com -d '*.example.com'

Database Table Structure

Multisite creates tables with a prefix for each subsite. The main site uses wp_posts, the second uses wp_2_posts, the third uses wp_3_posts:

wp_blogs         -- registry of network sites
wp_blog_versions -- DB versions per site
wp_sitemeta      -- meta-data of the whole network
wp_site          -- root site
wp_users         -- shared users (single registry)
wp_usermeta      -- roles stored here per-site

-- Tables of the first site
wp_posts, wp_postmeta, wp_options, wp_terms...

-- Tables of the second site
wp_2_posts, wp_2_postmeta, wp_2_options, wp_2_terms...

Users are shared, but roles are different for each subsite. A user can be an editor on site2 and a subscriber on site3.

Programmatic Subsite Creation

$blog_id = wpmu_create_blog(
    'newsite.example.com',
    '/',
    'New Site',
    get_current_user_id(),
    ['public' => 1],
    1
);

if (is_wp_error($blog_id)) {
    error_log('Error: ' . $blog_id->get_error_message());
    return;
}

switch_to_blog($blog_id);
update_option('blogdescription', 'Description');
restore_current_blog();

How to Map a Custom Domain to a Subsite?

Domain mapping — attaching a third-party domain (client-site.ru) to a Multisite subsite. Natively with WordPress 4.5+, you can change siteurl and home via WP-CLI. Nginx adds a server block that directs requests to the same root directory. Here's an example configuration:

server {
    listen 443 ssl;
    server_name client-site.ru;
    root /var/www/html;
    ...
}

Don't forget to add a DNS record for client-site.ru pointing to the server IP.

Network Plugins and Themes

A plugin activated at the network level works on all subsites. Some plugins don't support Multisite due to hardcoded table prefixes. You can check if an installation is multisite using is_multisite().

How Multisite Solves Scaling Issues?

With 50–100 active subsites on one server, degradation may occur due to each site's wp_options table. Solutions: Redis Object Cache with key segregation by blog_id, Varnish, HyperDB for database distribution. The average budget savings when switching from separate installations to Multisite is 40–60%. Multisite is 3–5 times more cost-effective than separate installations in terms of hosting costs and administration time. Request a consultation to evaluate your project.

Limitations and Solutions

What's Included in the Work

• Requirements analysis and network architecture design
• Server setup (Nginx, SSL wildcard, Redis, certificates)
• WordPress Multisite installation and configuration
• Domain mapping for custom domains
• Connection of network plugins (caching, security, SEO)
• Development of a custom subsite registrar if needed
• Documentation, access transfer, team training
• 30-day warranty period after project delivery

Our experience: 8+ years working with WordPress, 50+ successful Multisite projects, 100+ subsites in individual projects. Contact us to evaluate your project. Order a turnkey WordPress Multisite setup — we will offer the optimal solution.

WordPress Development: Custom Themes, Plugins, and WooCommerce

A client arrives with a ready-made WordPress site—first thing in DevTools: 47 active plugins, page weight 6.8 MB, TTFB 2.4 s, five conflicting jQuery versions in the console. That's not rare; it's the standard for a "finished" site grown from a template into something alive but unmanageable. We solve such problems end-to-end—from audit to deployment. Get in touch—we evaluate your project in one business day.

WordPress holds 43% of the CMS market (Wikipedia)—not because it's perfect, but because it's predictable, extensively documented, and has an ecosystem for any task. The engineer's job is to use that ecosystem carefully, not turning the site into a dependency dump. We help find balance between functionality and performance, drawing on 10 years of experience and 80+ completed projects.

What are common architectural problems in WordPress?

Render-blocking from plugins

Plugin A loads jQuery 3.6, Plugin B loads jQuery 1.12, the theme has its own jQuery Migrate. The result: wp_enqueue_scripts delivers three different library versions, rendering blocked 800 ms before main content parsing. Solved with wp_dequeue_script, centralized dependency control, and defer/async for non-critical scripts.

N+1 queries and their solution

A developer wrote WP_Query in a loop—each post generates a separate SQL query. On a page with 20 posts, that's 21+ database queries. MySQL lags, server heats. Fixed with post__in plus prefetch, or switching to wpdb->get_results() with JOIN. Query Monitor is the first diagnostic tool.

WooCommerce under load

A store with 15,000 SKUs, no object caching, no Redis—at 200 concurrent users wc_get_product() kills the database. WordPress transients don't help: they write to DB, increasing load. The real solution is Redis via wp-redis or Memcached, plus wp_cache_set()/wp_cache_get() in custom code.

How to choose architecture: headless or monolithic?

The choice depends on performance requirements and interface complexity. Headless (REST API / WPGraphQL + Next.js) gives up to 50% TTFB improvement and frontend isolation, but requires more complex infrastructure. Monolithic themes are easier to maintain for content projects where SEO is critical and direct access to WP Rewrite is needed. We help determine the optimal option during audit. Switching to headless improves LCP by 2.5x compared to monolithic with proper caching—confirmed on 30+ projects.

How do we push LCP under 2.5s for production WordPress sites?

Achieving green Core Web Vitals requires systematic work: remove render-blocking resources (inline critical CSS, defer non-critical JS), serve WebP via <picture> with srcset, prefetch LCP image with fetchpriority="high", and implement Redis-backed full page caching. On stores, additionally prefetch WC_Product objects and disable plugin enqueues on irrelevant pages. Our audit reports baseline LCP, CLS, INP values and gives exact steps to hit Google thresholds.

Stack and approaches in WordPress development

Theme development. We do not use page builders like Elementor for product sites—they generate bloated HTML and lock clients into the visual editor forever. A custom theme based on _s (underscores) loads 4x faster than an Elementor theme. Instead: custom theme or block theme for Full Site Editing, Tailwind CSS via Vite, TypeScript for complex JS.

Gutenberg and block development. Since WordPress 5.0, Gutenberg is not just an editor—it's a platform. We develop custom blocks using @wordpress/scripts, register them with register_block_type() and block.json. Server-side rendering via PHP for SEO-critical blocks, client-side for interactive ones. Inner Blocks for composite components.

REST API and headless. WordPress as headless CMS via WP REST API v2 or WPGraphQL. Typical setup: WordPress on subdomain cms.example.com, Next.js frontend on main domain. ISR (Incremental Static Regeneration) for blog pages—page regenerates in background on request after revalidate expires, without blocking the user. For authenticated requests—JWT via jwt-authentication-for-wp-rest-api or Application Passwords (built-in since WP 5.6). More about REST API—Wikipedia.

WooCommerce. Extend via hooks and filters—never modify core files. Custom product types via WC_Product extension. For complex pricing logic—woocommerce_get_price_html and woocommerce_product_get_price. Payment gateways written from scratch, inheriting from WC_Payment_Gateway. Integration with 1C via CommerceML or custom REST endpoint.

Performance. Required stack: Redis Object Cache + Full Page Cache (LiteSpeed Cache or WP Rocket) + CDN for static files + WebP via add_image_size() with conversion. Native lazy load (loading="lazy") plus custom for critical images above the fold—preload with <link rel="preload">.

Case study: WooCommerce store, LCP 9.2s → 1.8s

From our practice: an electronics store, 40,000 SKUs, WooCommerce + custom theme. PageSpeed Insights: LCP 9.2s, CLS 0.41, INP 680ms.

Diagnosis:

• Hero image 3.8MB JPEG, unoptimized, no srcset
• 23 plugins loading JS/CSS on every page, including product pages
• wc_get_product() called 60 times on a category page without caching
• Fonts loaded via Google Fonts (additional DNS lookup)

What we did:

• Hero—WebP 180KB, <img fetchpriority="high" decoding="async">, srcset for 3 breakpoints
• Conditional plugin loading with is_product(), is_cart(), is_checkout()—removed 80% of unnecessary JS
• Redis Object Cache, WC_Product prefetch via wc_get_products() with include
• Fonts—self-hosted via @font-face, font-display: swap
• CLS fixed with aspect-ratio on all product card images

Result: LCP 1.8s, CLS 0.04, INP 140ms. Core Web Vitals—green. Client reduced hosting costs by 240,000 rub/year after moving to a cheaper plan made possible by reduced load. Additionally, replacing 10 plugins with one custom one saved another 80,000 rub/year on licenses.

Work process

1. Audit and analytics. Analyze existing codebase, competitors, technical requirements. For new sites—semantic core, UX prototyping.
2. Architecture. Decide: monolithic or headless. Define Custom Post Types, Custom Fields (ACF or native register_meta()), taxonomies.
3. Development. Local environment: Docker (nginx + php-fpm + MariaDB). Git with pre-commit hooks for PHP CS Fixer and ESLint. Deployment via WP-CLI + SSH or Buddy.works CI/CD.
4. Testing. PHPUnit for custom plugins. Playwright for E2E critical scenarios (add to cart → checkout → confirmation). Lighthouse CI in pipeline—fail if Performance Score < 85.
5. Deploy and support. Staging via WP Stagecoach or manual clone. Monitoring—UptimeRobot + Sentry for PHP errors. Plugin updates—via WP-CLI in test environment first.

What you get as a result

• Fully custom theme or modification of existing one
• Configured object caching (Redis/Memcached) and Full Page Cache
• Optimized media files (WebP, srcset, lazy load)
• Code structure documentation and update instructions
• Training for content managers on Gutenberg blocks
• 30-day uptime guarantee after deployment
• Access to repository with full change history

Timeline benchmarks

Pricing is calculated individually after requirements audit. Contact us for a preliminary estimate.

Common mistakes in WordPress development

• Directly editing theme files—all changes lost on theme update. Use a child theme or fully custom theme.
• update_post_meta() in a loop—each call is a separate UPDATE. For bulk operations use $wpdb->update() or update_metadata_by_mid().
• Disabled WP_DEBUG during development—hidden PHP Notices clutter error log and often indicate real issues.
• Storing media in Git—wp-content/uploads in .gitignore, sync via WP-CLI media import or rsync.
• No limit on WP_Query—posts_per_page => -1 on a page with thousands of posts guarantees a timeout.

Why trust WordPress development to professionals?

We have been on the market for over 10 years, completed 80+ projects, hold certifications from Automattic, and have experience with WooCommerce on high-traffic sites. Our solutions account for all nuances: from plugin compatibility to Core Web Vitals requirements (Google recommendations). After project completion you get a documented, tested, and scalable platform.

For a consultation and evaluation of your project—contact us. We respond within one hour during business hours. Get a free preliminary audit today.