Multisite Defined (One Core, Many Sites)
Multisite defined: enabling it turns one WordPress install into a network container. Key points:
- One set of core files (wp-admin, wp-includes) serves every site.
- One database holds all content — each site's rows share tables with a site-ID prefix (wp_2_posts for site 2, and so on).
- One admin hierarchy above all sites: the Network Admin (Super Admin), who creates sites, installs themes and plugins network-wide, and manages users.
- Each site behaves like a normal WordPress to its users — its own scoped dashboard, content, users, URL, and theme choice from the network-approved set.
The mental model: an apartment building — shared structure and utilities, individually furnished flats, one landlord above all.
Subdomains vs Subdirectories vs Domain Mapping
Subdomains and Subdirectories are not the same product. Subdomains is the option with less for you to operate. Subdirectories is the option with more control, and more that you have to look after. Choose by what happens when it breaks at night, and by the INR figure on this page. Email support@webji.services if you want that choice made against your actual site.
Super Admin vs Site Admin Powers
Two practical notes on network admin: it interacts directly with caching and database response, and misconfiguration is the most common cause of 'hosting is slow' tickets. WebJi® support checks it as part of standard migrations.
Plugins and Themes at the Network Level
Plugins and themes operate under network rules. Installation happens at the network level: the Super Admin installs; themes then appear in each site's Appearance menu, and plugins in Plugins > Add New, if enabled.
Activation has two flavours: network activation — live on EVERY site, right for security, SEO and caching essentials — versus per-site activation, where each site's admin opts in (right for optional tools). Consequences to understand: a plugin activated network-wide that conflicts with ONE site affects them ALL — the debugging multiplier. Per-site plugin settings are stored separately, so configuration work multiplies. Some plugins simply are not multisite-compatible — check compatibility before adopting.
The discipline that works: keep the network plugin set small and rock-solid (security, backups, cache), and let sites opt into the long tail individually.
When Multisite Shines (Schools, Brands, Chains)
When Multisite Shines (Schools, Brands, Chains). Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.
When to Avoid It (Unrelated Client Sites)
The agency question — should client sites share one multisite? Usually NO, for the risk-list reasons: clients need isolation (one client's plugin experiment must not affect another's checkout), individual backups and restores, independent resource scaling, and clean exits. A client leaving must take their site, trivially a standalone export, painfully a multisite extraction.
The modern better answer for agencies: separate installs per client, automated — staged, updated, backed up by tooling — higher overhead than one network, dramatically lower blast radius. Multisite fits agencies only when clients are tiny, unrelated risk is accepted, and the agency wants one admin plane more than isolation. On hosting: multisite needs a plan that allows wildcard subdomains and multiple domains — WebJi®'s hosting supports multisite deployments with those features.
heavier student bodies or franchise networks belong on VPS or cloud tiers where the shared install has real headroom.
Setup and Conversion Basics
Setup and Conversion Basics. Do the change this heading names on one site first, then check it in a private browser window or in the mail client, depending on the topic. Change one setting at a time, and undo it if the result is wrong before you try the next. If you want the Jaipur desk to look with you, email support@webji.services — that mailbox is staffed 24/7 in Hindi and English. Phone +91 141 4941811 is business hours only.
Frequently Asked Questions
What is WordPress multisite?
Multisite defined: enabling it turns one WordPress install into a network container. Key points:
Should I use multisite or separate installations?
For “Should I use multisite or separate installations”: The modern better answer for agencies: separate installs per client, automated — staged, updated, backed up by tooling — higher overhead than one network, dramatically lower blast radius. Multisite fits agencies only when clients are tiny, unrelated risk is accepted, and the agency wants one admin plane more than isolation.
How do I set up a multisite network?
Multisite defined: enabling it turns one WordPress install into a network container. Key points: The question here is: How do I set up a multisite network.
Can multisite sites have different domains?
For “Can multisite sites have different domains”: The agency question — should client sites share one multisite? Usually NO, for the risk-list reasons: clients need isolation (one client's plugin experiment must not affect another's checkout), individual backups and restores, independent resource scaling, and clean exits. A client leaving must take their site, trivially a standalone export, painfully a multisite extraction.
Do plugins work on all multisite sites?
For “Do plugins work on all multisite sites”: Activation has two flavours: network activation — live on EVERY site, right for security, SEO and caching essentials — versus per-site activation, where each site's admin opts in (right for optional tools). Consequences to understand: a plugin activated network-wide that conflicts with ONE site affects them ALL — the debugging multiplier.
Is multisite good for hosting client sites?
For “Is multisite good for hosting client sites”: The agency question — should client sites share one multisite? Usually NO, for the risk-list reasons: clients need isolation (one client's plugin experiment must not affect another's checkout), individual backups and restores, independent resource scaling, and clean exits. A client leaving must take their site, trivially a standalone export, painfully a multisite extraction.
Is WebJi® an Indian company?
Yes. WebJi® is headquartered in Jaipur, Rajasthan and has operated since 2005. Billing, support and governance all run from India.
Do you provide GST invoices?
Every purchase and renewal gets a GST invoice with our GSTIN, and hosting prices are quoted exclusive of 18% GST. Claim input credit as applicable.