# Review server capacity for multiple WordPress sites Compare current resource use and workload patterns before assigning colocated sites. CPU, RAM, disk and key user journeys remain acceptable under representative load. Canonical: https://xcloud.host/use-cases/solutions/review-server-capacity-for-multiple-wordpress-sites/ 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: Compare current resource use and workload patterns before assigning colocated sites. 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 agency puts several WordPress sites on one server. 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: Shared resource spikes can affect unrelated clients. 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, not a customer case study: An agency puts several WordPress sites on one server. CPU, RAM, disk and key user journeys remain acceptable under representative load. ## Choose the approach - Choose capacity based on peak overlap and actual resource trends. 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/) - 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 sites, traffic windows and critical tasks **Where:** xCloud team/site resource read and planning sheet **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** List sites, traffic windows and critical tasks; exact site identity, named approver and controlled sample data. **Action:** List sites sharing the server, each site's busy period, disk growth and the most important user transaction. **Expected result:** Capacity review has workload context. **Verify:** Capacity review has workload context. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a site is missing from inventory, correct the server/site map. Capability: Confirm requirements and inspect resources 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) ### 2. Inspect server resource and disk history **Where:** xCloud team/site resource read and planning sheet **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Inspect server resource and disk history; exact site identity, named approver and controlled sample data. **Action:** Read xCloud CPU, RAM, disk and PHP worker history for peak periods; record the measurement window and any alerts. **Expected result:** Resource patterns are visible, not guessed. **Verify:** Resource patterns are visible, not guessed. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If metrics are unavailable, mark uncertainty and gather measurements. Capability: Confirm requirements and inspect resources 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) ### 3. Estimate combined peak and growth headroom **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Estimate combined peak and growth headroom; exact site identity, named approver and controlled sample data. **Action:** Estimate combined peak overlap and remaining headroom; compare WordPress background tasks and backup windows. **Expected result:** The agency has a concrete capacity hypothesis. **Verify:** The agency has a concrete capacity hypothesis. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If peaks coincide, avoid adding another site before evaluating scale options. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ### 4. Run representative traffic tests without harming live users **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Run representative traffic tests without harming live users; exact site identity, named approver and controlled sample data. **Action:** Run a safe representative traffic test on non-production or use observed production trends, checking business path latency and error rate. **Expected result:** The chosen evidence reflects user impact. **Verify:** The chosen evidence reflects user impact. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a test would harm live customers, use a controlled test environment. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ### 5. Set thresholds, owner and migration trigger **Where:** xCloud team/site resource read and planning sheet **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Set thresholds, owner and migration trigger; exact site identity, named approver and controlled sample data. **Action:** Set a measured threshold and owner for resizing or moving a site, with a separate approved change plan. **Expected result:** Growth has a trigger, not a vague promise. **Verify:** Growth has a trigger, not a vague promise. Record the observed site, account or transaction and time in the release sheet. **If it fails:** Do not resize resources based on one transient spike alone. Capability: Confirm requirements and inspect resources 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) ## 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: CPU, RAM, disk and key user journeys remain acceptable under representative load. 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 review does not change production settings. Keep the original measurements and configuration, then write a separately approved experiment and rollback criterion before any cache, PHP or capacity change. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## 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 review server capacity for multiple wordpress sites for the exact site and team I name. Use permitted reads and ask for application evidence you cannot observe. Work through: List sites sharing the server, each site's busy period, disk growth and the most important user transaction.; Read xCloud CPU, RAM, disk and PHP worker history for peak periods; record the measurement window and any alerts.; Estimate combined peak overlap and remaining headroom; compare WordPress background tasks and backup windows.; Run a safe representative traffic test on non-production or use observed production trends, checking business path latency and error rate.; Set a measured threshold and owner for resizing or moving a site, with a separate approved change plan. 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): CPU, RAM, disk and key user journeys remain acceptable under representative load. Steps: phase-4 - **recovery** (covered): Shared resource spikes can affect unrelated clients. 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 - [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 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/generate-an-agency-wordpress-maintenance-report/) - [Hand over WordPress maintenance and client reporting](https://xcloud.host/use-cases/playbooks/agency-wordpress-maintenance-handover/)