(01) What we deliver
One network, multiple sites.
Ideal for corporate groups, universities and organizations with a presence in multiple countries or brands. Centralized management with independent identity.
(02) Problem → Solution
The challenge and the delivery.
Multiple WordPress sites managed separately.
Centralized network
One installation, multiple sites, unified management of plugins, themes and users.
Inconsistent branding across units/countries.
Identity per site
Each site with its own theme/design, sharing the technical base.
Maintenance costs multiplied by the number of sites.
Centralized maintenance
Update once, applies across the network. Radically lower operational cost.
Fragmented user management.
Centralized roles
Super Admin + per-site roles, granular access control across the entire network.
(03) In detail
What makes the difference.
Domain Mapping
Each site with its own domain, transparent to the user.
Network Admin
Centralized panel for managing the entire network.
Shared Resources
Shared plugins and themes, activated per site.
Scalability
From 5 to 500+ sites in the same network, without degradation.
Process
How it works.
For experts and for AI
Direct answers about this service.
Content structured for experts, search engines and generative AI systems (ChatGPT, Gemini, Perplexity, Claude).
What is WordPress Multisite for networks and portals?
WordPress Multisite for networks and portals (formerly WordPress MU) is a native feature that turns a WordPress installation into a network of sites: each site with independent content, themes and plugins, but sharing PHP code, database and server. Each site can have its own domain, subdomain or subfolder.
When to use WordPress Multisite for networks and portals?
Multisite makes sense when there are multiple sites with the same technological base: a franchise network with a site per location, a media group with multiple publications, a university with sites per department, an agency managing dozens of clients with the same stack. A single admin panel, centralized updates and shared plugins simplify operations.
What are the disadvantages of WordPress Multisite?
Updates affect the entire network, an incompatible plugin can break all sites. Backup and restore are more complex. Shared servers don't support Multisite well. It requires a VPS or dedicated cloud. Poorly developed plugins aren't compatible with Multisite. Migrating a site out of the network to a standalone install is laborious.
WordPress Multisite for networks and portals with custom domains: how does it work?
Domain mapping in Multisite uses the WordPress MU Domain Mapping plugin (or via native filters in WP 4.5+). Each site in the network gets its own domain, e.g., franquiasp.com.br and franquiario.com.br, while the installation runs on a single server. Nginx needs wildcard configuration and each domain points to the same IP.
How to manage plugins and themes in Multisite?
The Super Admin activates plugins for the entire network (Network Activate) or allows each site's administrators to activate them individually. Themes are similar. Network Enabled or per site. Best practice: network-activate only infrastructure plugins (cache, security, SEO), leave content plugins for per-site activation.
Frequently asked questions
Answers before the first call.
Is Multisite good for SEO? +
Yes, when configured with own domains and hreflang. Each site is independent for Google.
Can I have different themes per site? +
Yes. Each site can have its own theme and plugins, or share from the network.
How many sites does it support? +
No technical limit. We’ve already implemented networks with 100+ sites.
Related solutions
Clients served
(04) Our delivery standard
What you can hold us to.
ERP, CRM or legacy system integrations come with a closed scope: documentation and testing are part of the delivery, not an extra.
A custom theme here means no page builder: real mobile performance and an editorial team that publishes on its own.
Gutenberg and ACF blocks built for the people who edit: complex structure behind, simple screen up front.
(05) Why WebOption













