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 migrated WordPress site looks live but old URLs and media may be wrong.
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: Blanket redirects can mask missing pages and damage user journeys.
Illustrative situation
Illustrative scenario, not a customer case study: A migrated WordPress site looks live but old URLs and media may be wrong. Priority pages, images, forms and redirects resolve at the intended domain.
Choose the approach
Compare a sampled URL inventory and content against the source. 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 · xCloud WordPress migration guide
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
Export priority urls, templates, media and metadata
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Export priority urls, templates, media and metadata; exact site identity, named approver and controlled sample data.
- Action
- Export priority source URLs, titles, media references and canonical targets from the pre-migration site.
- Expected result
- The review has a finite sample and expected URLs.
- Verify
- The review has a finite sample and expected URLs. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If source URLs are unavailable, use sitemap or logs with that limit noted.
Sources: WordPress roles and capabilities · xCloud WordPress migration guide · WordPress content import
Step 2 of 5
Compare target pages and attachment references
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Compare target pages and attachment references; exact site identity, named approver and controlled sample data.
- Action
- Compare each sample with the target's page copy, image loading and internal links.
- Expected result
- The reviewer finds missing or changed content.
- Verify
- The reviewer finds missing or changed content. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a template hides text, record it for the migration operator.
Sources: WordPress roles and capabilities · xCloud WordPress migration guide · WordPress content import
Step 3 of 5
Propose exact URL repairs
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Repair domain-specific links and explicit redirects; exact site identity, named approver and controlled sample data.
- Action
- Propose source-to-destination redirects and content repairs for each broken sampled URL. Do not edit production in this review-only guide, and avoid blanket redirects that mask missing pages.
- Expected result
- The owner receives a prioritized repair list with evidence and exact intended destinations.
- Verify
- The owner receives a prioritized repair list with evidence and exact intended destinations. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- Avoid blanket redirects that mask missing pages.
Sources: WordPress roles and capabilities · xCloud WordPress migration guide · WordPress content import
Step 4 of 5
Test canonical, mobile, forms and search index settings
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Test canonical, mobile, forms and search index settings; exact site identity, named approver and controlled sample data.
- Action
- Test current canonical, mobile view, forms and search index settings with anonymous sessions.
- Expected result
- The review captures visitor and crawler-facing errors.
- Verify
- The review captures visitor and crawler-facing errors. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If production noindex appears, escalate its actual source rather than blaming staging sync.
Sources: WordPress roles and capabilities · xCloud WordPress migration guide · WordPress content import
Step 5 of 5
Monitor 404s and publish an owner-approved correction list
- Where
- WordPress public/admin views and relevant provider evidence
- Permissions
- Named WordPress/app administrator or business owner; use authorized test accounts.
- Inputs
- Monitor 404s and publish an owner-approved correction list; exact site identity, named approver and controlled sample data.
- Action
- Hand prioritized defects and acceptance checks to a separate change owner, then monitor 404s after fixes.
- Expected result
- The migration remains accountable until key paths pass.
- Verify
- The migration remains accountable until key paths pass. Record the observed site, account or transaction and time in the release sheet.
- If it fails
- If a new issue appears after backup time, preserve newer content before any recovery.
Sources: WordPress roles and capabilities · xCloud WordPress migration guide · WordPress content import
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: Priority pages, images, forms and redirects resolve at the intended domain. 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
This content review only records defects. Before a later repair or restore, preserve posts and form submissions made since the migration snapshot and recheck redirects and canonical URLs afterward.
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 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): Priority pages, images, forms and redirects resolve at the intended domain. Test canonical, mobile, forms and search index settings
- recovery (covered): Blanket redirects can mask missing pages and damage user journeys. Monitor 404s and publish an owner-approved correction list
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- xCloud MCP documentation and connection profiles
- xCloud WordPress migration guide
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- WordPress content import