Requirements and responsibilities
Have the real estate agencies owner approve public copy, required staff roles and the exact sample journey. A property agency publishes listings that become unavailable quickly.
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: Stale inventory or duplicate leads creates client confusion.
Illustrative situation
Illustrative scenario: a property agency changes listings often. Its manually maintained sample listing moves to sold, the public index reflects that state, and inquiries reach the assigned agent.
Choose the approach
Choose a listing data source and update owner before designing filters. 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
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
Define listing states, fields, feed rights and agent ownership
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Define listing states, fields, feed rights and agent ownership; named administrator and a harmless representative sample.
- Action
- Define listing states—draft, active, under offer, sold—and the agent or feed that owns each change. Record photo rights and required location fields.
- Expected result
- One source of truth exists for inventory.
- Verify
- One source of truth exists for inventory. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If agents and an import feed can both overwrite status, settle precedence before publishing.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Build manual listing index and inquiry route
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Build wordpress listing templates and inquiry destinations; named administrator and a harmless representative sample.
- Action
- Create a manual sample listing index in WordPress with approved status, price and location fields. Use a feed or faceted-filter plugin only after its owner verifies current license, documentation and field mapping.
- Expected result
- Visitors can find the sample listing and read its current state; any promised automated filter has a documented selected implementation.
- Verify
- Visitors can find the sample listing and read its current state; any promised automated filter has a documented selected implementation. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If filters show an unavailable unit as active, fix the data mapping before launch.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 3 of 5
Enter a rights-cleared sample listing
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Import or enter sample listings using documented tool; named administrator and a harmless representative sample.
- Action
- Enter one rights-cleared listing manually and assign its inquiry mailbox to the responsible agent. Treat a licensed feed as a separate documented integration decision, then compare imported fields before publishing.
- Expected result
- The sample has correct status, media rights and agent contact; no automatic feed synchronization is assumed.
- Verify
- The sample has correct status, media rights and agent contact; no automatic feed synchronization is assumed. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If a feed lacks current rights or update frequency, leave those records unpublished.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 4 of 5
Test sold state and assigned agent routing
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Test filters, sold status and inquiry routing; named administrator and a harmless representative sample.
- Action
- Mark the manual sample as sold, inspect its direct URL and index, then submit a synthetic inquiry to the assigned agent. If a selected feed is later added, repeat after its next update cycle.
- Expected result
- The public state and agent routing agree with the source inventory.
- Verify
- The public state and agent routing agree with the source inventory. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If the listing remains in active search, correct cache or feed synchronization.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 5 of 5
Plan feed-failure checks, backup and access review
- Where
- WordPress or selected application administrator and owner handoff
- Permissions
- Named WordPress/application administrator and business owner; inspect backup separately if recovery is in scope.
- Inputs
- Plan feed-failure checks, backup and access review; named administrator and a harmless representative sample.
- Action
- Review feed failures and stale listings daily during active sales; protect leads and media in backup scope.
- Expected result
- An agent can correct inventory without developer access.
- Verify
- An agent can correct inventory without developer access. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If recovery would revive sold listings, refresh from the source before reopening search.
Sources: Site backups in xCloud · xCloud agent capability boundaries · WordPress roles and capabilities
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: A sold sample listing is removed or marked accurately in public search. 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. Stale inventory or duplicate leads creates client confusion. 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 WordPress content, users and selected plugins app · manual
Requires a named WordPress administrator or suitable editor. Plugin behavior, commercial license, payment, email and external integration are verified in the chosen vendor documentation and application; xCloud hosting or MCP reads do not configure them.
Checkpoint: Open the actual WordPress or selected plugin interface, record the version and role, and have the business owner accept a real user journey.
WordPress roles and capabilities · WordPress plugin administration
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Enter one rights-cleared listing manually and assign its inquiry mailbox to the responsible agent. Treat a licensed feed as a separate documented integration decision, then compare imported fields before publishing.
- The business owner compares the controlled sample with this observable result: The public state and agent routing agree with the source inventory.
- 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): A sold sample listing is removed or marked accurately in public search. Test sold state and assigned agent routing
- recovery (covered): Stale inventory or duplicate leads creates client confusion. Plan feed-failure checks, backup and access review