
WordPress Multisite is one of the most underused features in the WordPress core. For UAE businesses running multiple branches, multi-language sites, or a portfolio of brands, it can save weeks of admin work and thousands of dirhams in license fees. A hotel group with properties in Dubai, Abu Dhabi, and Ras Al Khaimah, a free zone consultancy with separate Arabic and English sites, a retailer with one storefront for the UAE and another for Saudi Arabia, all of these are textbook Multisite scenarios.
This guide walks through Multisite from the ground up, what it is, how the network admin dashboard actually works, the choice between subdomains, subdirectories, and custom domains, the wp-config.php and .htaccess code you need, and how to map a real .ae or .com domain to a subsite. We cover the hosting requirements for serious UAE Multisite networks, SSL setup for both wildcard and multi-domain configurations, bilingual Arabic and English setups, and what PDPL compliance means when one network handles multiple sites.
WordPress Multisite is a built-in feature, available since WordPress 3.0, that lets a single WordPress installation power a network of separate websites. You install WordPress once, activate Multisite, and from there you can create as many sub-sites as your hosting can handle. All sub-sites share the same WordPress core files, themes, and plugins, but each one has its own content, its own users, its own URL, and its own database tables.
To understand the architecture, picture a single WordPress installation on your server. Without Multisite, that installation runs one website. With Multisite enabled, the same installation becomes a “network” that runs multiple sites simultaneously. Two new admin layers appear, the Super Admin who manages the entire network, and the Site Admin who manages an individual sub-site.
| Layer | What Is Shared | What Is Separate |
|---|---|---|
| WordPress core files | One copy of wp-admin, wp-includes, all core PHP files | Nothing, every sub-site uses the same core |
| Themes | Installed in /wp-content/themes/, shared across the network | Each sub-site activates its own theme independently |
| Plugins | Installed in /wp-content/plugins/, shared | Each sub-site activates its own plugins (unless network-activated) |
| Media uploads | Same /wp-content/uploads/ folder | Each sub-site has its own subfolder, e.g. /uploads/sites/2/, /uploads/sites/3/ |
| Database | One database, one set of network-wide tables (wp_users, wp_blogs, wp_site) | Each sub-site has its own set of tables (wp_2_posts, wp_3_posts, etc.) |
| Users | User accounts are network-wide | Each sub-site assigns roles independently to those users |
| Content | Nothing | Posts, pages, settings, menus, categories, all separate per sub-site |
This shared architecture is what makes Multisite efficient. When WordPress, a theme, or a plugin needs an update, you do it once and all sub-sites benefit. The trade-off is that all sub-sites share the same server resources and the same database, so traffic spikes on one sub-site can affect performance on the others, and a security breach in one sub-site can spread.
Once Multisite is activated, your WordPress dashboard gains two new modes, the regular site dashboard you already know, and the Network Admin dashboard for managing the whole network. You switch between them through the My Sites menu in the top admin bar.
The top-left menu, My Sites, lists every sub-site you have access to. Clicking any sub-site name takes you to that sub-site’s regular admin dashboard, where you write posts, manage pages, configure widgets, just like a normal single-site WordPress installation. Inside My Sites there is also a Network Admin link. That opens a separate dashboard with network-wide controls.
| Network Admin Section | What You Do Here |
|---|---|
| Dashboard | Overview widgets, quick-add new sites and users |
| Sites | List of every sub-site, add new ones, edit settings, view dashboard, delete sites |
| Users | Manage all user accounts across the network, assign Super Admin rights |
| Themes | Install themes for the network, choose which sub-sites can use which themes |
| Plugins | Install plugins, network-activate (force enabled on all sub-sites) or leave optional |
| Settings | Network-wide config: name, default email, registration policy, language, file upload limits |
| Updates | One-click update WordPress core, themes, plugins across the entire network |
The day-to-day pattern looks like this. You log in once. As Super Admin, you see all sub-sites in the My Sites dropdown. Pick the one you want to edit, click into it, work on it like any other WordPress site. When you need to add a new sub-site or update plugins network-wide, jump to Network Admin from the same menu. No more logging out and logging into different installations.
Multisite makes sense when you have a portfolio of websites that share a parent organisation and would benefit from centralised maintenance. Here are the patterns that come up most often for UAE businesses.
A real estate firm with offices in Dubai, Abu Dhabi, Sharjah, and RAK. Each branch needs its own listing pages, contact details, regional content, but the same brand identity, same property database structure, and same legal pages. Multisite lets each branch run as a sub-site with the same theme, while content stays separate. Updates to the master theme reach every branch instantly.
The UAE is a bilingual market. Many businesses run mybrand.ae for Arabic-speaking customers and mybrand.com for English-speaking ones (or use language-specific subdomains like ar.mybrand.com and en.mybrand.com). Multisite handles this elegantly, each language is a sub-site with its own translated content, RTL theme settings, and locale, while shared assets like product images are managed once. We cover the bilingual setup pattern in more depth later in this guide.
A UAE hotel group with properties across the Emirates. The corporate site sits at jumeirahgroup.example, individual properties at burjalarab.example, almadinat.example, and so on. Multisite lets each property maintain its own room photography, restaurant menus, and booking content, while the parent organisation enforces brand standards through shared themes and plugins.
Universities like the American University in Dubai or Khalifa University often have one website for the institution and separate sites per faculty, department, or student group. Multisite is the standard solution worldwide for this pattern. Each department gets its own URL and editorial control, while the IT team maintains a single backend.
A holding company that owns three coffee shops, two restaurants, and a delivery service. Each brand has a distinct identity but shares back-office operations. Multisite consolidates web management without forcing brand consolidation, each sub-site looks completely different to customers but lives in one technical home.
A UAE business with both a free zone entity (often serving international customers) and a mainland licence (serving the UAE market). The two operations may need to look distinct because their target customers, pricing, and legal context differ. Multisite supports this cleanly with separate sub-sites under one administration.
If you run an agency and have a few clients within the same group of companies (a holding company with multiple subsidiaries), Multisite saves time. Important caveat: if your clients are unrelated and one might leave for another agency, Multisite makes that exit messy because the database is shared. For unrelated clients, separate WordPress installations are safer.
A UAE business that wants region-specific sites for the UAE, Saudi Arabia, Qatar, and Bahrain, each in local language and currency, can run a four-sub-site Multisite network. Combined with proper hreflang tags, this also handles SEO for cross-Gulf targeting.
Multisite is wrong for several common scenarios. Choosing it for the wrong reasons creates pain that grows over time.
| Scenario | Why Multisite Fails Here | Better Alternative |
|---|---|---|
| Unrelated agency clients | Shared database, hard to migrate one client out cleanly | Separate WordPress installations on the same server |
| Sites with very different traffic profiles | High-traffic site slows down low-traffic sites on the same network | Separate VPS instances per site |
| Sites needing very different security profiles | Compromise of one sub-site can spread to the network | Isolated installations on different servers |
| Plugin compatibility unknown | Some plugins do not support Multisite, some require costly Multisite licenses | Single-site installations where plugin compatibility is verified |
| One site that may need to be sold separately | Extracting one sub-site to a standalone installation is complex and error-prone | Single-site, easier to package and transfer ownership |
| Sites with regulated data (PDPL-sensitive) | Shared database mixes data subject records, complicates breach notification scope | Isolated installations with separate databases per regulated context |
| Need for individual site backups and restores | Multisite backs up the whole network as a unit, single-site restore is non-trivial | Single-site installations where each backs up independently |
One of the most important architectural decisions in Multisite is how sub-sites are addressed. WordPress offers three approaches, and the choice affects URL structure, SEO, server configuration, and DNS setup.
| Approach | URL Pattern | SEO Effect | Setup Complexity |
|---|---|---|---|
| Subdirectories | mybrand.ae/dubai, mybrand.ae/abudhabi | All sub-sites share the parent domain authority | Easiest, no DNS changes required |
| Subdomains | dubai.mybrand.ae, abudhabi.mybrand.ae | Each subdomain treated as somewhat separate by Google | Medium, wildcard DNS record needed |
| Custom Domains (Domain Mapping) | mydubaisite.ae, myabudhabisite.ae (any domain) | Each domain is fully separate in Google’s eyes | Highest, separate domain registration plus DNS plus SSL per site |
Subdirectories are the simplest option and the right choice for: bilingual sites where one language is primary, university or company sites where each department is clearly part of the parent organisation, or any situation where consolidated SEO authority matters more than independent identities. Setup requires no DNS configuration, you just enable Multisite and choose subdirectories during the wizard.
Subdomains work best for: multi-brand groups where each sub-site needs visual independence, regional targeting (uk.mybrand.com, ae.mybrand.com), and customer-facing portals (clients.mybrand.ae, partners.mybrand.ae). They require a wildcard DNS record (more on that in the setup section) and slightly more server configuration.
Custom domain mapping is for: separate brands that should not appear connected, country-specific operations (mybrand.ae and mybrand.sa), or franchise networks where each location wants its own branded URL. Setup involves registering each domain separately, configuring DNS per domain, mapping each to its sub-site, and managing SSL certificates per domain. This is the most powerful but also the most administratively demanding configuration.
Multisite shares server resources across all sub-sites. Whatever each individual site would consume on shared hosting, Multisite multiplies. A two-site Multisite needs roughly twice the resources of a single site, a ten-site network needs ten times. This makes hosting choice critical.
| Hosting Type | Multisite Suitability | UAE Recommendation |
|---|---|---|
| Cheap shared hosting | Not recommended beyond 2-3 small sub-sites | Avoid for serious Multisite networks |
| Standard cPanel hosting | Acceptable for low-traffic networks of up to 5-10 small sites | AEserver Linux Hosting with cPanel for testing or small networks |
| Managed WordPress hosting | Good for traffic-heavy networks, optimised stack | Managed WordPress Hosting Dubai for production networks |
| Cloud VPS | Best for medium and growing networks, full root control, scalable resources | AEserver Cloud VPS in Dubai for serious deployments |
| Dedicated server | For very large networks (50+ active sites or high-traffic enterprise) | Dedicated Servers in Dubai |
For UAE-targeted networks specifically, hosting in Dubai matters. Page-load latency to Gulf users from a Dubai datacentre is a fraction of latency from European or US servers, and the gap shows up in Core Web Vitals, conversion rates, and search rankings. We cover this in detail in our local vs overseas hosting comparison and the 10 Benefits of VPS Hosting for UAE Businesses guide.
Activating Multisite changes how WordPress writes to the database and rewrites URLs at the server level. Skipping the preparation steps is the fastest route to a broken installation. Run through this checklist in order.
Back up both the database and the WordPress files. Use Acronis Backup for full-server snapshots, or a backup plugin like UpdraftPlus, BackWPup, or Duplicator for application-level backups. Verify the backup before continuing, an untested backup is no backup at all. See our WordPress backup guide for plugin-level options.
Go to Settings, Permalinks and confirm anything other than “Plain”. Post Name is the standard. Click “Save Changes” even if you change nothing, this rewrites the .htaccess rules. Test that your existing posts and pages load correctly.
Go to Plugins, Installed Plugins, select all, choose “Deactivate” from the bulk action dropdown, click Apply. You will reactivate them after Multisite is configured. Active plugins during the Multisite wizard can corrupt the network setup process.
WP Rocket, W3 Total Cache, LiteSpeed Cache, Cloudflare APO, all of these need to be disabled during setup. Cached pages and rewrite rules will conflict with the new Multisite URL structure. Re-enable after the network is fully working.
This is the irreversible architectural choice mentioned earlier. If you choose subdomains, you must also configure wildcard DNS before completing the wizard (covered in the next section). Choose subdirectories if you want the simplest setup with no DNS work, choose subdomains if you need each sub-site to feel separate or if you plan to map custom domains later.
Most modern UAE hosting platforms support Multisite, but some shared hosting plans block the necessary mod_rewrite rules or limit database table counts. If you are on AEserver, every Linux hosting plan supports Multisite. If you are on a third-party host, check their documentation or open a support ticket before starting.
For a subdomain network, you need a wildcard DNS A record pointing to your server’s IP. Go to your domain DNS panel, add a record like:
Type: A Host: * Value: 185.x.x.x (your server IP) TTL: 3600
This tells DNS that any subdomain of yourbrand.ae (mail.yourbrand.ae, dubai.yourbrand.ae, anything.yourbrand.ae) should route to your server. Without this record, sub-sites will not resolve. Allow DNS propagation up to 24 hours, though most TLDs propagate within 1-2 hours.
Once preparation is complete, the actual activation is fast. Allow 30 minutes for the full process including testing. The procedure follows the official WordPress Multisite Network Creation guide with UAE-specific commentary.
Connect to your server via cPanel File Manager, FTP, or SSH. Edit wp-config.php in the WordPress root directory. Find the line that says /* That's all, stop editing! Happy publishing. */ and add this block ABOVE it:
/* Multisite */ define( 'WP_ALLOW_MULTISITE', true );
Save the file. This single flag tells WordPress to expose the Multisite setup tools in the admin dashboard. Nothing else changes yet, your site is still a normal single-site WordPress installation.
Refresh your WordPress admin dashboard. Go to Tools, Network Setup (this menu item only appears after you saved the constant in step 1). You will see the “Create a Network of WordPress Sites” page.
This is the irreversible architectural choice. Reference the comparison table from earlier. If you chose subdomains, you should already have wildcard DNS in place (from the pre-setup checklist). The wizard may show a warning about wildcard subdomains, ignore it if you have already configured DNS.
The wizard auto-populates these from your existing settings, but verify each:
Click Install.
The wizard now shows two code blocks. The first goes into wp-config.php, just below the WP_ALLOW_MULTISITE line you added in Step 1. It will look like this for a subdirectory installation:
define( 'MULTISITE', true ); define( 'SUBDOMAIN_INSTALL', false ); define( 'DOMAIN_CURRENT_SITE', 'mybrand.ae' ); define( 'PATH_CURRENT_SITE', '/' ); define( 'SITE_ID_CURRENT_SITE', 1 ); define( 'BLOG_ID_CURRENT_SITE', 1 );
For a subdomain network, SUBDOMAIN_INSTALL would be true instead of false. Copy the exact block the wizard generates for your installation, do not paste a template, the values are specific to your domain and site IDs.
The wizard also shows a second code block for .htaccess in the WordPress root. Replace any existing WordPress rewrite rules with these new ones. If your site has no .htaccess yet, create the file. For a subdirectory installation:
RewriteEngine On
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /
RewriteRule ^index\.php$ - [L]
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-(content|admin|includes).*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*\.php)$ $2 [L]
RewriteRule . index.php [L]
For a subdomain installation, the rules are slightly different (the wizard generates the right block for your case). Save .htaccess.
The wizard logs you out automatically once it confirms the configuration. Clear your browser cache or open a private window if you have caching issues. Log back in with your existing credentials. You should now see “My Sites” and “Network Admin” in your top admin bar.
Once the network is live, adding sub-sites takes seconds. From the Network Admin dashboard:
Go to My Sites, Network Admin, Sites. You see a list of all sub-sites in your network (initially just the main site, ID 1). Click Add New.
Three fields:
dubai creates dubai.mybrand.ae). For subdirectory networks, this is the path (e.g. dubai creates mybrand.ae/dubai).Click Add Site.
WordPress creates the sub-site, generates 10 new database tables (e.g. wp_2_posts, wp_2_options for site ID 2), and creates an upload folder at /wp-content/uploads/sites/2/. Click into the new sub-site from My Sites to access its dashboard. Activate themes and plugins (you can only choose from those network-installed). Configure settings, write content.
By default, the Super Admin (you) is the only admin of the new sub-site. To give a colleague or client admin rights for that single sub-site without making them Super Admin, add them as a user from Network Admin, Users first, then go into the sub-site’s Users, Add New Existing User and assign them the Administrator role for that sub-site only.
The most powerful Multisite feature for UAE businesses with multiple brands is custom domain mapping. Instead of dubai.mybrand.ae, you can have mydubaibrand.ae as a fully separate domain that resolves to a sub-site in your network. As of WordPress 4.5, this is a built-in feature, no plugin required.
Register the new domain through AEserver’s .ae registration for UAE-specific brands or any other relevant TLD. If you already own the domain elsewhere, you can either transfer it to AEserver or just point its DNS to your network’s server.
In the new domain’s DNS panel, add an A record pointing to your network’s server IP:
Type: A Host: @ Value: 185.x.x.x (your server IP) TTL: 3600 Type: A Host: www Value: 185.x.x.x TTL: 3600
Allow DNS to propagate. You can verify with dig mydubaibrand.ae or online tools.
If you are on cPanel hosting, go to Domains, Aliases (or Aliases in older panels) and add the new domain so cPanel knows to serve it from your WordPress installation. Without this step, the server returns a 404 even if DNS is correct.
In WordPress, go to Network Admin, Sites, hover over the sub-site you want to remap, click Edit. In the “Site Address (URL)” field, replace the existing subdomain or path with the new full domain:
https://mydubaibrand.ae
Save changes. From this point, visitors who type mydubaibrand.ae reach the sub-site as if it were a standalone WordPress installation. The sub-site’s posts, settings, and admin still live in your main network.
SSL is mandatory for any production Multisite network. Browsers mark non-HTTPS sites as “Not Secure”, Google ranks them lower, and UAE business credibility takes an immediate hit. Multisite has three SSL approaches depending on your URL architecture.
| Network URL Pattern | SSL Certificate Type | Coverage |
|---|---|---|
| Subdirectories only (mybrand.ae/dubai) | Standard single-domain SSL on mybrand.ae | Covers all subdirectories automatically |
| Subdomains (dubai.mybrand.ae) | Wildcard SSL (*.mybrand.ae) | Covers main domain plus all first-level subdomains |
| Mapped custom domains (mydubaibrand.ae, myabudhabibrand.ae) | Multi-Domain SAN/UCC certificate, or separate certs per domain | Each mapped domain needs its own SSL coverage |
| Mixed (subdomains + mapped domains) | Wildcard for subdomains plus per-domain certs for mapped sites | Combination, install separately |
For UAE businesses, AEserver offers all three certificate types via the SSL Certificates store, and free Let’s Encrypt SSL ships with most hosting plans. Wildcard certificates require domain validation through DNS (a TXT record), so plan ahead before launch.
Once SSL is installed, force HTTPS network-wide. The simplest way is to install the Really Simple SSL plugin and network-activate it from Network Admin, Plugins. The plugin redirects all HTTP traffic to HTTPS and fixes mixed-content warnings across every sub-site. For a deeper background on SSL, see SSL Certificate Guide for UAE Businesses.
Theme and plugin management changes meaningfully under Multisite. Only the Super Admin can install or update them, Site Admins can only activate or deactivate what is already installed.
Go to Network Admin, Themes. You see installed themes with three actions:
Site Admins activate from the themes their sub-site has been granted. To force a default theme for newly created sub-sites, add this to wp-config.php:
define( 'WP_DEFAULT_THEME', 'your-theme-slug' );
Go to Network Admin, Plugins. Each plugin shows two activation options:
To enable Site Admins to activate per-sub-site plugins themselves, go to Network Admin, Settings, Network Settings and check Enable administration menus, Plugins. Otherwise, the plugins menu is hidden from Site Admins and only Super Admin controls activation.
The UAE is officially bilingual, and many businesses run separate Arabic and English sites. Multisite is one of three approaches to multilingual WordPress, and it has specific advantages and drawbacks compared to plugins like WPML or Polylang.
| Approach | Pros | Cons |
|---|---|---|
| WPML or Polylang plugin | Single dashboard, content linked across languages, easier translation workflows | Plugin license cost, performance overhead, compatibility issues with some themes |
| Multisite (one sub-site per language) | Clean separation, RTL theme per site, no plugin license, native WordPress feature | Manual content sync, no built-in translation links between sites |
| MultilingualPress (Multisite + plugin) | Multisite advantages plus translation links between sub-sites | Adds plugin complexity, requires careful sub-site planning |
For typical UAE bilingual deployments, the Multisite approach works well when content is managed independently per language, or with MultilingualPress for translation linking. Each sub-site gets its own locale (Arabic for one, English for the other), its own RTL-enabled theme variant, and its own URL strategy (yourbrand.ae for Arabic primary, en.yourbrand.ae or yourbrand.com for English). Read our full guide on multilingual WordPress sites for the full comparison and implementation steps.
Even careful setups hit predictable issues. Here are the most common problems UAE webmasters encounter, and the fixes that work.
The cookie domain in wp-config.php is conflicting with the new network. Add this line to wp-config.php:
define( 'COOKIE_DOMAIN', '' );
Save, clear cookies in your browser, log back in.
Wildcard DNS is not configured or has not yet propagated. Verify the wildcard A record exists in DNS, run dig anything.yourbrand.ae to confirm propagation. If you are on shared hosting, also confirm the wildcard subdomain is added in your hosting panel (cPanel: Domains, Aliases or Subdomains).
Multisite emails go through the same WordPress sender as a single site, so if your site was already failing to send emails, Multisite will fail too. Install an SMTP plugin (WP Mail SMTP is the standard), connect it to a transactional email service or your AEserver Business Email SMTP, and emails will deliver reliably. Domain authentication via SPF, DKIM, and DMARC also matters, see our email spam protection guide for the deliverability setup.
Multisite updates run across every sub-site sequentially, on a network of 10+ sites this can exceed PHP’s max execution time. Increase memory and execution time in wp-config.php:
define( 'WP_MEMORY_LIMIT', '512M' ); @ini_set( 'max_execution_time', 300 );
If you still hit limits on shared hosting, that is a strong signal you have outgrown shared hosting and need a Cloud VPS for your network.
Either the domain alias is not set in your hosting panel, or the Site Address (URL) in Network Admin, Sites, Edit was not updated to the new domain. Check both, fix whichever is wrong, then clear browser cache and any caching plugins.
Some image URLs, CSS, or JS files still load over HTTP. Network-activate Really Simple SSL or use a Search and Replace plugin to update database URLs from http://yourbrand.ae to https://yourbrand.ae across all sub-sites. Check theme files for hardcoded HTTP URLs.
Two common causes. First, that sub-site has a heavier plugin set or a poorly optimised theme, audit per-site activations. Second, that sub-site receives more traffic and is consuming network resources, that is the “noisy neighbour” effect within your own network. Solutions: caching at the network level (LiteSpeed Cache or Redis Object Cache), or moving the high-traffic sub-site to its own VPS as a standalone installation.
The UAE Personal Data Protection Law (PDPL), Federal Decree-Law No. 45 of 2021, applies to any business processing personal data of UAE residents. Multisite networks introduce a few specific compliance considerations because data from multiple sub-sites lives in one shared database.
| PDPL Concept | Multisite Implication |
|---|---|
| Data minimisation | Each sub-site should only collect data needed for its own purpose, not aggregate across the network unnecessarily |
| Lawful basis for processing | Lawful basis (consent, contract, legitimate interest) is per data controller relationship, document who is the controller for which sub-site |
| Right of access and erasure | When a data subject requests deletion, you must locate their data across every sub-site they interacted with, plan for cross-network search |
| Breach notification | A breach of one sub-site that exposes the shared network database is a breach affecting ALL sub-sites, broaden your notification scope accordingly |
| Cross-border data transfers | Hosting location of the network applies to all sub-sites, hosting in Dubai keeps data within the UAE for all of them simultaneously |
| Privacy notice | Each sub-site needs its own privacy notice tailored to what that sub-site collects, not a single network-wide notice |
For full PDPL compliance guidance, see our Complete UAE PDPL Guide for Businesses. The short version, document each sub-site’s data flows separately, hold breach drills for the whole network not just individual sites, and keep hosting in the UAE so cross-border transfer obligations stay simple.
Multisite backups require more thought than single-site backups because the database is shared. A standard backup captures everything, but restoring just one sub-site is non-trivial.
Acronis Cyber Backup takes server-level snapshots that capture the entire WordPress network plus the underlying OS and configurations. Restoration brings the whole network back. This is the most reliable approach, especially for critical UAE business networks where downtime is expensive.
UpdraftPlus Premium, BackupBuddy, or Duplicator Pro all support Multisite and can back up the entire WordPress installation including all sub-site database tables and shared media. Schedule daily backups to an offsite destination (S3, Google Drive, Dropbox, or your own cloud storage).
For granular recovery, dump each sub-site’s database tables (wp_2_*, wp_3_*, etc.) separately on a schedule. The Prime Mover plugin supports per-sub-site exports that can be restored to a different installation. This is the only reliable way to “rescue” a single sub-site if you ever need to migrate it out of the network.
One compromised sub-site can affect the entire network, so security on Multisite is unforgiving. Attackers know this and target Multisite installations with specific techniques covered in our breakdown of 18 real WordPress attacks and how to stop them. The following hardening checklist is essential.
define( 'DISALLOW_FILE_EDIT', true );For the broader website security framework, follow our 17-step website security guide.
Yes, but with a critical caveat, your existing site becomes the “main site” of the new network (site ID 1), and its URL structure stays unchanged. New sub-sites go alongside, not over, the existing one. Always back up before activating Multisite on an existing site.
Yes, WooCommerce supports Multisite. Each sub-site can have its own store with separate products, orders, and customer accounts. This is how some UAE retailers run UAE and KSA storefronts as separate sub-sites with shared admin. For UAE-specific WooCommerce setup, see our e-commerce security guide.
Technically, hundreds of thousands. Edublogs runs over five million sub-sites on a single Multisite installation. Practically, the limit is your hosting resources. A 2 vCPU / 4GB Cloud VPS handles 10-30 small business sub-sites comfortably, a dedicated server can handle hundreds.
No, all sub-sites share the same database, but each gets its own set of tables (wp_2_*, wp_3_*, and so on for each site ID). This is by design and cannot be changed without migrating to separate installations.
Not necessarily. Multilingual plugins (WPML, Polylang) handle most cases without Multisite. Use Multisite for multilingual when you want each language to feel like a fully independent site, with separate themes, separate URL structures, and clean editorial separation. For lighter setups, plugins are simpler. The Bilingual Setup section above covers the full comparison.
Use a plugin like Prime Mover or WP Migrate DB Pro Multisite Tools. The process exports that sub-site’s database tables and media, imports them into a fresh standalone WordPress installation, and rewrites URLs. It is fiddly, allow several hours and test thoroughly. This is why we recommend not using Multisite for unrelated client sites that may need to move.
One of three things, the plugin works only on the main site (silently ignores sub-sites), the plugin breaks across the network when network-activated, or the plugin works but stores data incorrectly across sub-sites. Always check plugin compatibility in the WordPress.org plugin description and test on a staging copy before live activation.
Yes. The Super Admin installs themes network-wide, and each Site Admin chooses which theme to activate for their sub-site. This is the basis of multi-brand Multisite networks where each brand has its own visual identity.
Subdirectory networks share domain authority across sub-sites, which usually helps SEO. Subdomain networks have each subdomain treated somewhat separately by Google. Mapped custom domains are fully separate in Google’s eyes, no shared authority. Pick the architecture based on your SEO goals as much as your technical needs.
Yes. All AEserver hosting plans, from Linux Hosting to Managed WordPress Hosting in Dubai to Cloud VPS, support WordPress Multisite without special configuration. Wildcard subdomains can be set up in the cPanel domain panel, custom domain mapping is straightforward, and free SSL is included on most plans. For larger networks, our dedicated resources scale Multisite up reliably.
Yes. There is one wp-admin folder, one wp-includes folder, one set of WordPress core PHP files. All sub-sites run on the same WordPress version. When you update WordPress core via Network Admin, every sub-site receives the update simultaneously. This is one of the main efficiency benefits of Multisite.
WordPress Multisite is one of the most powerful features in WordPress core, and one of the most underused by UAE businesses. For multi-emirate networks, bilingual sites, multi-brand groups, and Gulf-regional expansions, it can save hundreds of admin hours and thousands of dirhams in licensing fees per year. The trade-off is shared infrastructure, choose Multisite only when sub-sites belong together at the architectural level.
If you are ready to launch a Multisite network for your UAE business, the right starting point is hosting that can handle it. Managed WordPress Hosting in Dubai is the easiest path for most UAE businesses, with Multisite-friendly configuration, automated backups, and Dubai-based servers. For larger or more demanding networks, a Cloud VPS gives you the headroom to grow. And to register a domain for mapped custom sub-sites across .ae, .com, and the broader Gulf, AEserver handles the full registration lifecycle as the UAE’s official registrar since 2005.