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 has approved a design fix on staging while live orders continue.
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: A full database push may overwrite orders and users.
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: An agency has approved a design fix on staging while live orders continue. Production reflects the fix and post-test orders remain intact.
Choose the approach
Push only the selected files or tables needed by the change. 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 Security PRO setup and eligibility
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
Record exact changed files, tables and live-data delta
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Record exact changed files, tables and live-data delta; exact site identity, named approver and controlled sample data.
- Action
- Compare staging change log with production files, tables and orders created since last pull. Mark exactly what must move.
- Expected result
- The promotion scope is smaller than an unexamined full copy.
- Verify
- The promotion scope is smaller than an unexamined full copy. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If live-data delta is unknown, stop before push.
Sources: WordPress roles and capabilities · Create a staging environment in xCloud · WooCommerce testing orders
Step 2 of 5
Take fresh production backup and confirm restore point
- Where
- xCloud Site Backup dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Take fresh production backup and confirm restore point; exact site identity, named approver and controlled sample data.
- Action
- Confirm a fresh production files-and-database backup and access to its restore point.
- Expected result
- The live site has a pre-release recovery point.
- Verify
- The live site has a pre-release recovery point. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If backup fails, hold the push.
Sources: Site backups in xCloud · xCloud agent capability boundaries · Create a staging environment in xCloud · WooCommerce testing orders
Step 3 of 5
Review staging push scope with store owner
- Where
- xCloud Staging Management dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Review staging push scope with store owner; exact site identity, named approver and controlled sample data.
- Action
- In Staging Management select only approved files or tables and review overwrite behavior with the store owner before pressing Push to Production.
- Expected result
- The dashboard shows the intended scope.
- Verify
- The dashboard shows the intended scope. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the selected scope includes new order tables, cancel and redesign it.
Sources: Create a staging environment in xCloud · xCloud agent capability boundaries · WooCommerce testing orders
Step 4 of 5
Push approved scope in xcloud staging management
- Where
- xCloud Staging Management dashboard
- Permissions
- Named xCloud team/site administrator; confirm target and scope.
- Inputs
- Push approved scope in xcloud staging management; exact site identity, named approver and controlled sample data.
- Action
- Run the approved dashboard push, wait for logs to finish and record the operation; do not infer completion from MCP reads.
- Expected result
- The selected change reaches production.
- Verify
- The selected change reaches production. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If the job errors, inspect deployment log before retrying or restoring.
Sources: Create a staging environment in xCloud · xCloud agent capability boundaries · WooCommerce testing orders
Step 5 of 5
Check order continuity, page rendering and indexability
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Check order continuity, page rendering and indexability; exact site identity, named approver and controlled sample data.
- Action
- Check live design, checkout, newest order and production indexing; compare with pre-push order identifiers.
- Expected result
- The fix is live without losing orders.
- Verify
- The fix is live without losing orders. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If order continuity fails, preserve current data and begin an owner-led recovery decision.
Sources: WordPress roles and capabilities · Create a staging environment in xCloud · WooCommerce testing orders
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: Production reflects the fix and post-test orders remain intact. 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. A full database push may overwrite orders and users. 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.
- Configure native WordPress backup and restore dashboard · manual
Native schedule, retention and destination changes and all restores are dashboard-only.
Checkpoint: Use Site → Site Backup. Before restoring, confirm backup, target, scope and treatment of newer records.
- Create and synchronize WordPress staging dashboard · manual
WordPress staging requires an eligible paid plan. The API staging-create operation is for Git sites.
Checkpoint: Use Site overview → Add Staging and staging Site → Manage Staging. Inspect push/pull scope before overwriting data.
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: In Staging Management select only approved files or tables and review overwrite behavior with the store owner before pressing Push to Production.
- The business owner compares the controlled sample with this observable result: The selected change reaches production.
- 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): Production reflects the fix and post-test orders remain intact. Push approved scope in xcloud staging management
- recovery (covered): A full database push may overwrite orders and users. Check order continuity, page rendering and indexability
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
- Site Security PRO setup and eligibility
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- WooCommerce testing orders