# Plan a WordPress multisite decision Decide whether subdomain multisite fits related publications by comparing network ownership, plugins, domains and recovery scope with separate sites. Canonical: https://xcloud.host/use-cases/solutions/plan-a-wordpress-multisite-decision/ Published: 2026-09-30 · Updated: 2026-09-30 · Technical review: 2026-09-30 Evidence: Source reviewed; no production deployment test claimed Editorial owner: xCloud editorial Intent: Document network-level requirements and verify xCloud and plugin compatibility before selecting architecture. For: business-owner, operator ## Requirements and responsibilities - Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: An organization considers WordPress multisite for related publications. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) - Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) - Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: A shared network can broaden update and recovery impact. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) ## Illustrative situation Illustrative scenario: an organization is choosing between subdomain multisite and separate WordPress sites. The decision records ownership, plugin and recovery tradeoffs, plus a future pilot matrix. ## Choose the approach - Choose multisite only after reviewing shared administration and plugin constraints. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [WordPress multisite administration](https://developer.wordpress.org/advanced-administration/multisite/) - Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) ## Dashboard and application procedure ### 1. List shared versus independent sites and administrators **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** List shared versus independent sites and administrators; exact site identity, named approver and controlled sample data. **Action:** List proposed sites, domains, editors, plugins and whether content/data should be independent. **Expected result:** The decision has shared-versus-separate criteria. **Verify:** The decision has shared-versus-separate criteria. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If legal ownership differs, treat shared network administration as a risk. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [WordPress multisite administration](https://developer.wordpress.org/advanced-administration/multisite/) ### 2. Review WordPress multisite and xcloud support docs **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Review wordpress multisite and xcloud support docs; exact site identity, named approver and controlled sample data. **Action:** Read WordPress multisite and xCloud support docs for domain, plugin and network-administrator constraints. **Expected result:** The option reflects documented behavior. **Verify:** The option reflects documented behavior. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a required plugin lacks network support, do not assume it works. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [WordPress multisite administration](https://developer.wordpress.org/advanced-administration/multisite/); [xCloud WordPress multisite with subdomains](https://xcloud.host/docs/wordpress-multisite-with-subdomain/) ### 3. Compare network setup with separate-site option **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Compare network setup with separate-site option; exact site identity, named approver and controlled sample data. **Action:** Compare one multisite network with separate WordPress sites for update scope, access and restore isolation. **Expected result:** The owner sees the blast radius of each choice. **Verify:** The owner sees the blast radius of each choice. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a client needs independent recovery, weigh separate sites heavily. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [WordPress multisite administration](https://developer.wordpress.org/advanced-administration/multisite/); [xCloud WordPress multisite with subdomains](https://xcloud.host/docs/wordpress-multisite-with-subdomain/) ### 4. Design a subdomain pilot **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Pilot roles, domain and plugin behavior on test environment; exact site identity, named approver and controlled sample data. **Action:** Write a future pilot matrix for one subdomain, network administrator, site editor and required plugin. Note that xCloud’s current documented multisite setup is subdomain-based and verify eligibility before any build. **Expected result:** The proposed pilot has expected domain, role and plugin checks; no pilot is claimed complete. **Verify:** The proposed pilot has expected domain, role and plugin checks; no pilot is claimed complete. Record the exact account or record tested, result, and time with the responsible owner. **If it fails:** If no test owner exists, record the assumption as unresolved. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [WordPress multisite administration](https://developer.wordpress.org/advanced-administration/multisite/); [xCloud WordPress multisite with subdomains](https://xcloud.host/docs/wordpress-multisite-with-subdomain/) ### 5. Decide backup and incident blast radius before launch **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Decide backup and incident blast radius before launch; exact site identity, named approver and controlled sample data. **Action:** Recommend one path with required proof, backup granularity and client approval. Include an explicit test owner and unresolved domain assumptions. **Expected result:** The decision can guide a separate implementation. **Verify:** The decision can guide a separate implementation. Record the observed site, account or transaction and time in the release sheet. **If it fails:** Do not present multisite as a default cost or maintenance saving without evidence. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [WordPress multisite administration](https://developer.wordpress.org/advanced-administration/multisite/) ## Maintenance - Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: A pilot site has correct domain, editors and network ownership. A chat prompt is not a scheduled task. Sources: [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/); [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) - Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## Recovery decisions - This comparison makes no access or network change. If a required domain, plugin or isolation need is unsupported, revise the recommendation toward separate sites and seek a documented test before setup. Sources: [xCloud WordPress multisite with subdomains](https://xcloud.host/docs/wordpress-multisite-with-subdomain/); [WordPress multisite administration](https://developer.wordpress.org/advanced-administration/multisite/) ## AI handoff Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only. ### Supported scope - **Confirm requirements and inspect resources** (mcp; read): Discover the connected profile and operation schema first; only teams granted to the connection are visible. Checkpoint: Confirm exact team, server and site identity. Use dashboard\_url returned by the resource; do not invent a dashboard link. Operation identifiers to discover: teams.index, servers.show, sites.show. Scopes: read:servers, read:sites. Sources: [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - **Review a WordPress business journey** (app; manual): Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence. Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision. Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) ### Copyable agent brief ```text Review plan a wordpress multisite decision for the exact site and team I name. Use permitted reads and ask for application evidence you cannot observe. Work through: List proposed sites, domains, editors, plugins and whether content/data should be independent.; Read WordPress multisite and xCloud support docs for domain, plugin and network-administrator constraints.; Compare one multisite network with separate WordPress sites for update scope, access and restore isolation.; Write a future pilot matrix for one subdomain, network administrator, site editor and required plugin. Note that xCloud’s current documented multisite setup is subdomain-based and verify eligibility before any build.; Recommend one path with required proof, backup granularity and client approval. Include an explicit test owner and unresolved domain assumptions. Return observations, uncertainties, a decision and a separately approvable operator checklist. Do not create, restore, configure, publish or update anything in this review. ``` ### Manual checkpoints - The named site, business or provider owner supplies application evidence the connected hosting reads cannot observe. - A separately approved operator performs any later configuration, staging, update, restore or publication described in the decision sheet. - The owner accepts the review finding and proposed checks without treating the unexecuted change as completed. ## Feature coverage - **business-acceptance** (covered): A pilot site has correct domain, editors and network ownership. Steps: phase-4 - **recovery** (covered): A shared network can broaden update and recovery impact. Steps: phase-5 ## Sources - [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) — reviewed 2026-09-30; v4.4.2 package; xCloud v2.8.8 capability review - [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) — reviewed 2026-09-30 - [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) — reviewed 2026-09-30 - [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) — reviewed 2026-09-30 - [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) — reviewed 2026-09-30 - [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) — reviewed 2026-09-30 - [WordPress multisite administration](https://developer.wordpress.org/advanced-administration/multisite/) — reviewed 2026-09-30 - [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/) — reviewed 2026-09-30 - [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) — reviewed 2026-09-30 - [xCloud WordPress multisite with subdomains](https://xcloud.host/docs/wordpress-multisite-with-subdomain/) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/add-an-analytics-service-to-wordpress/) - [Hand over WordPress maintenance and client reporting](https://xcloud.host/use-cases/playbooks/agency-wordpress-maintenance-handover/)