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: A WordPress site is lost and the team must rebuild from available backups.
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: Wrong backup scope can omit uploads or database content.
Before any database copy or restore starts, the authorized operator restricts the target and quarantines outbound mail, payment, fulfillment and other provider effects. Restored settings may overwrite plugin suppression; reapply sandbox credentials and verify isolation before testing.
Create a staging environment in xCloud · Site backups in xCloud
Illustrative situation
Illustrative scenario, not a customer case study: A WordPress site is lost and the team must rebuild from available backups. The replacement serves the correct content and administration works.
Choose the approach
Choose a compatible target and a recovery point before recreation. 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 · Site backups 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
Inventory available files, database and dns controls
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Inventory available files, database and dns controls; exact site identity, named approver and controlled sample data.
- Action
- Inventory available backup files, database point, intended hostname and current DNS owner; list newest business records that might be absent.
- Expected result
- The reconstruction plan names data gaps.
- Verify
- The reconstruction plan names data gaps. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If no restorable point exists, investigate alternate exports before changing routing.
Sources: WordPress roles and capabilities · xCloud recreate WordPress from backups · Site backups in xCloud
Step 2 of 5
Select the recreate destination
- Where
- xCloud Add New Site → Recreate Site From Backup
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Create a compatible target wordpress environment; exact site identity, named approver and controlled sample data.
- Action
- In xCloud Add New Site choose Recreate Site From Backup, then select the compatible server and destination/domain while keeping public DNS unchanged. Confirm the exact source backup and settings before starting.
- Expected result
- The dashboard presents the selected backup and destination for explicit review.
- Verify
- The dashboard presents the selected backup and destination for explicit review. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If server/PHP stack differs, verify plugin compatibility first.
Sources: xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · xCloud recreate WordPress from backups · Site backups in xCloud
Step 3 of 5
Start recreation from backup
- Where
- xCloud Recreate Site From Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Follow xcloud recreate-from-backup dashboard procedure; exact site identity, named approver and controlled sample data.
- Action
- After the owner confirms the displayed source, destination and settings, choose Start in the xCloud recreation flow. Wait for the operation to finish and preserve its status and logs.
- Expected result
- The recreated site loads backup files and database at the approved destination.
- Verify
- The recreated site loads backup files and database at the approved destination. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If restore reports missing files or schema issues, stop cutover and inspect another point.
Sources: Site backups in xCloud · xCloud restore backup to another site · xCloud agent capability boundaries · xCloud recreate WordPress from backups
Step 4 of 5
Check site url, media, users and representative transactions
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Check site url, media, users and representative transactions; exact site identity, named approver and controlled sample data.
- Action
- Inspect WordPress login, media, internal links, forms and representative transactions on the new target.
- Expected result
- Business owner can accept the reconstructed copy.
- Verify
- Business owner can accept the reconstructed copy. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If newer orders or submissions are absent, reconcile them before traffic switch.
Sources: WordPress roles and capabilities · xCloud recreate WordPress from backups · Site backups in xCloud
Step 5 of 5
Switch traffic only after owner signs recovery record
- Where
- Authorized DNS provider and public browser
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Switch traffic only after owner signs recovery record; exact site identity, named approver and controlled sample data.
- Action
- With domain owner's approval update routing to the verified target and check HTTPS, canonical host and application flows.
- Expected result
- Visitors reach the recovered site.
- Verify
- Visitors reach the recovered site. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If DNS routes inconsistently, keep old evidence and follow the rollback plan.
Sources: xCloud WordPress migration guide · Enable HTTPS and configure SSL certificates in xCloud · xCloud recreate WordPress from backups · Site backups in xCloud
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 replacement serves the correct content and administration works. 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. Wrong backup scope can omit uploads or database content. 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.
- Create a WordPress site mcp · write
Requires a compatible Nginx or OpenLiteSpeed server; Docker and single-site agentic servers cannot host a new WordPress site.
Checkpoint: Approve the exact server, domain, capacity, cost and creation inputs before provisioning. Verify completion and HTTPS.
Operation identifiers and scopes to discover
servers.sites.wordpress.create
Scopes: write:sites
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles
- Restore a backup dashboard · manual
Native and Docker restore operations are dashboard-only. An in-place Docker restore replaces current data.
Checkpoint: Use Site → Site Backup → Previous Backups → Restore Backup (or Restore to Another Site where offered). Confirm exact target and recovery point before proceeding.
xCloud agent capability boundaries · Back up and restore Docker apps
- Change domain DNS and verify routing app · manual
DNS changes belong to the domain provider or authorized DNS integration; reading an xCloud site does not establish public propagation or certificate validity.
Checkpoint: Approve exact hostname and record values; check authoritative DNS and live HTTPS from an independent session.
xCloud WordPress migration guide · Enable HTTPS and configure SSL certificates in xCloud
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: After the owner confirms the displayed source, destination and settings, choose Start in the xCloud recreation flow. Wait for the operation to finish and preserve its status and logs.
- The business owner compares the controlled sample with this observable result: Business owner can accept the reconstructed copy.
- 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 replacement serves the correct content and administration works. Check site url, media, users and representative transactions
- recovery (covered): Wrong backup scope can omit uploads or database content. Switch traffic only after owner signs recovery record
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- Create a staging environment in xCloud
- xCloud MCP documentation and connection profiles
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- xCloud recreate WordPress from backups
- xCloud restore backup to another site
- xCloud WordPress migration guide
- Enable HTTPS and configure SSL certificates in xCloud
- Back up and restore Docker apps