# Review dynamic pages before caching Identify cart, account, form, and booking paths that require application-specific cache review. Separate sessions show correct carts, prices and account details. Canonical: https://xcloud.host/use-cases/solutions/review-dynamic-pages-before-caching/ Published: 2026-09-30 · Updated: 2026-09-30 · Technical review: 2026-09-30 Evidence: Source reviewed; no production deployment test claimed Editorial owner: xCloud editorial Intent: Identify cart, account, form, and booking paths that require application-specific cache review. For: business-owner, operator ## 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 WooCommerce site has product pages and personalized cart and account paths. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress roles and capabilities](https://wordpress.org/documentation/article/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. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) - Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: Page cache leakage can expose or stale personalized content. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) ## Illustrative situation Illustrative scenario, not a customer case study: A WooCommerce site has product pages and personalized cart and account paths. Separate sessions show correct carts, prices and account details. ## Choose the approach - Map cacheability per URL and user state before changing settings. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [WordPress roles and capabilities](https://wordpress.org/documentation/article/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. Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) ## Dashboard and application procedure ### 1. List product, cart, checkout and account url patterns **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** List product, cart, checkout and account url patterns; exact site identity, named approver and controlled sample data. **Action:** List product, cart, checkout, account and booking paths and whether each response is public or personalized. **Expected result:** The cache review has a URL-state matrix. **Verify:** The cache review has a URL-state matrix. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a route's data ownership is unknown, treat it as dynamic until tested. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud WordPress caching overview](https://xcloud.host/docs/how-caching-works-in-xcloud/); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ### 2. Inspect current xcloud and plugin cache rules **Where:** xCloud team/site resource read and planning sheet **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Inspect current xcloud and plugin cache rules; exact site identity, named approver and controlled sample data. **Action:** Inspect xCloud and plugin cache settings using permitted reads or dashboard view; identify the layer responsible for page exclusions. **Expected result:** The reviewer knows which control governs each path. **Verify:** The reviewer knows which control governs each path. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If OpenLiteSpeed exclusions live in a plugin, do not claim xCloud MCP can change them. Capability: Confirm requirements and inspect resources Sources: [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md); [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud WordPress caching overview](https://xcloud.host/docs/how-caching-works-in-xcloud/); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ### 3. Specify bypass or exclusion rules in responsible interface **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Specify bypass or exclusion rules in responsible interface; exact site identity, named approver and controlled sample data. **Action:** Propose bypass rules for cookies, logged-in accounts and dynamic paths using the selected cache tool's own docs, without applying them in this review. **Expected result:** An administrator has a testable configuration proposal. **Verify:** An administrator has a testable configuration proposal. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If a rule could bypass too much public cache, narrow it before approval. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud WordPress caching overview](https://xcloud.host/docs/how-caching-works-in-xcloud/); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ### 4. Test anonymous and two logged-in sessions **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Test anonymous and two logged-in sessions; exact site identity, named approver and controlled sample data. **Action:** In two separate sessions inspect cart contents, account details and price while reviewing current behavior. **Expected result:** No observed cross-session state is exposed. **Verify:** No observed cross-session state is exposed. Record the observed site, account or transaction and time in the release sheet. **If it fails:** If data leaks now, escalate immediately and disable risky cache through an authorized operator. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud WordPress caching overview](https://xcloud.host/docs/how-caching-works-in-xcloud/); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) ### 5. Record owner, purge procedure and regression cases **Where:** WordPress public/admin views and relevant provider evidence **Permissions:** Named WordPress/app administrator or business owner; use authorized test accounts. **Inputs:** Record owner, purge procedure and regression cases; exact site identity, named approver and controlled sample data. **Action:** Record proposed rules, purge procedure and a regression list for a separate approved change. **Expected result:** The implementation owner can verify the later edit. **Verify:** The implementation owner can verify the later edit. Record the observed site, account or transaction and time in the release sheet. **If it fails:** Do not infer safety from a single anonymous speed test. Capability: Review a WordPress business journey Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/); [xCloud WordPress caching overview](https://xcloud.host/docs/how-caching-works-in-xcloud/); [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/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: Separate sessions show correct carts, prices and account details. A chat prompt is not a scheduled task. Sources: [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/); [Vulnerability Checker in xCloud](https://xcloud.host/docs/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. Sources: [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## Recovery decisions - This review does not change production settings. Keep the original measurements and configuration, then write a separately approved experiment and rollback criterion before any cache, PHP or capacity change. Sources: [xCloud WordPress caching overview](https://xcloud.host/docs/how-caching-works-in-xcloud/); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) ## 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 to discover: teams.index, servers.show, sites.show. Scopes: read:servers, read:sites. Sources: [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs); [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) - **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. Sources: [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) ### Copyable agent brief ```text Review review dynamic pages before caching for the exact site and team I name. Use permitted reads and ask for application evidence you cannot observe. Work through: List product, cart, checkout, account and booking paths and whether each response is public or personalized.; Inspect xCloud and plugin cache settings using permitted reads or dashboard view; identify the layer responsible for page exclusions.; Propose bypass rules for cookies, logged-in accounts and dynamic paths using the selected cache tool's own docs, without applying them in this review.; In two separate sessions inspect cart contents, account details and price while reviewing current behavior.; Record proposed rules, purge procedure and a regression list for a separate approved change. Return observations, uncertainties, a decision and a separately approvable operator checklist. Do not create, restore, configure, publish or update anything in this review. ``` ### 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): Separate sessions show correct carts, prices and account details. Steps: phase-4 - **recovery** (covered): Page cache leakage can expose or stale personalized content. Steps: phase-5 ## Sources - [xCloud agent capability boundaries](https://github.com/xCloudDev/xcloud-agent-skills/blob/main/plugins/xcloud/reference/capability-map.md) — reviewed 2026-09-30; v4.4.2 package; xCloud v2.8.8 capability review - [WordPress roles and capabilities](https://wordpress.org/documentation/article/roles-and-capabilities/) — reviewed 2026-09-30 - [WordPress plugin administration](https://wordpress.org/documentation/article/manage-plugins/) — reviewed 2026-09-30 - [Site backups in xCloud](https://xcloud.host/docs/site-backups-in-xcloud/) — reviewed 2026-09-30 - [WordPress hardening handbook](https://developer.wordpress.org/advanced-administration/security/hardening/) — reviewed 2026-09-30 - [xCloud MCP documentation and connection profiles](https://app.xcloud.host/mcp/docs) — reviewed 2026-09-30 - [Manage WordPress updates with Updates Manager](https://xcloud.host/docs/manage-wordpress-updates-with-updates-manager/) — reviewed 2026-09-30 - [Vulnerability Checker in xCloud](https://xcloud.host/docs/vulnerability-checker-in-xcloud/) — reviewed 2026-09-30 - [xCloud WordPress caching overview](https://xcloud.host/docs/how-caching-works-in-xcloud/) — reviewed 2026-09-30 - [WooCommerce testing orders](https://woocommerce.com/document/managing-orders/testing-orders/) — reviewed 2026-09-30 ## Continue [Explore the next WordPress workflow](https://xcloud.host/use-cases/solutions/plan-php-compatibility-checks-for-wordpress/) - [Check WooCommerce checkout before launch](https://xcloud.host/use-cases/solutions/woocommerce-checkout-launch-readiness/)