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 receives an outage report for a client's WordPress site.
xCloud agent capability boundaries · WordPress 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.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: An unplanned restore can erase fresh orders or leads.
Illustrative situation
Illustrative scenario, not a customer case study: An agency receives an outage report for a client's WordPress site. The incident log identifies timeline, owner, impact and verified restoration.
Choose the approach
Use severity and live-data preservation to select containment before recovery. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · Vulnerability Checker in xCloud
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.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Confirm site identity, symptom, time and customer impact
- Where
- xCloud team/site resource read and planning sheet
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Confirm site identity, symptom, time and customer impact; exact site identity, named approver and controlled sample data.
- Action
- Confirm exact client site, symptom onset, affected customer journey and incident owner.
- Expected result
- The response starts with impact and identity.
- Verify
- The response starts with impact and identity. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If multiple clients share a server, avoid assuming one site's symptom explains all.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Site backups in xCloud
Step 2 of 5
Preserve logs, recent data and current backup evidence
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Preserve logs, recent data and current backup evidence; exact site identity, named approver and controlled sample data.
- Action
- Preserve current logs, recent orders/leads and backup completion evidence before making changes.
- Expected result
- The team retains investigation and live-data options.
- Verify
- The team retains investigation and live-data options. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If data is still arriving, establish a controlled intake route.
Sources: WordPress roles and capabilities · Site backups in xCloud · xCloud agent capability boundaries
Step 3 of 5
Choose containment, forward fix or safe-target restore
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Choose containment, forward fix or safe-target restore; exact site identity, named approver and controlled sample data.
- Action
- Compare containment, forward fix and safe-target restore, including downtime and newer-data delta; ask client owner to approve exact action separately.
- Expected result
- The selected recovery path has explicit tradeoffs.
- Verify
- The selected recovery path has explicit tradeoffs. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- Do not launch in-place restore without backup/target and reconciliation decision.
Sources: WordPress roles and capabilities · Site backups in xCloud · xCloud agent capability boundaries
Step 4 of 5
Validate critical business flows with client owner
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Validate critical business flows with client owner; exact site identity, named approver and controlled sample data.
- Action
- After authorized repair, test the client's critical login, form, checkout or booking path with application evidence.
- Expected result
- The affected business journey works again.
- Verify
- The affected business journey works again. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If only the home page works, keep incident open.
Sources: WordPress roles and capabilities · Site backups in xCloud · xCloud agent capability boundaries
Step 5 of 5
Record root cause, access changes and follow-up tests
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Record root cause, access changes and follow-up tests; exact site identity, named approver and controlled sample data.
- Action
- Record timeline, cause evidence, access changes and follow-up checks; assign preventive work in a real task system.
- Expected result
- Client receives an actionable incident record.
- Verify
- Client receives an actionable incident record. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If root cause is uncertain, say so and schedule targeted investigation.
Sources: WordPress roles and capabilities · Site backups in xCloud · xCloud agent capability boundaries
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: The incident log identifies timeline, owner, impact and verified restoration. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · 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.
Recovery decisions
Before restoring, compare the chosen recovery point with newer business records. An unplanned restore can erase fresh orders or leads. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
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 and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- 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.
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Compare containment, forward fix and safe-target restore, including downtime and newer-data delta; ask client owner to approve exact action separately.
- The business owner compares the controlled sample with this observable result: The affected business journey works again.
- Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only.
Feature coverage
- business-acceptance (covered): The incident log identifies timeline, owner, impact and verified restoration. Validate critical business flows with client owner
- recovery (covered): An unplanned restore can erase fresh orders or leads. Record root cause, access changes and follow-up tests