How to Enable the Edge Full Page Cache in xCloud
Updated November 3, 2026 · 10 min read
Caching plays a crucial role in boosting website performance and delivering a faster, smoother browsing experience for users. At xCloud, we know that speed and performance are critical for a great user experience. That’s why we offer powerful Edge Caching, which saves your site’s page cache to a global network of data centers, delivering content from the location closest to each visitor. This can boost your website speed and performance. For an overview of what it does and which plans include it, see the edge caching feature page.
Along with edge caching, we implement heavy caching layers both at the server level and through Page Caching and Object Caching, ensuring lightning-fast load times. The edge cache keeps a page for as long as your site’s page cache allows. You can clear it at any time. Whether you’re deploying updates, copying your site, or simply editing a post, purging the right cache makes your changes appear within a few minutes.
At xCloud, edge caching is included with all plans at no extra cost. xCloud adds a small helper plugin to your site for you.
Note: It is recommended to maintain a full-page cache alongside the Edge Cache for optimal performance. You can continue using your existing full-page caching solutions, such as FastCGI (NGINX Cache), LiteSpeed Cache (LSCache), or WP Rocket, together with the Edge Cache.
If the site has an Active domain on the Cloudflare Enterprise add-on, this setting is not shown. The Caching page shows Managed by Cloudflare Enterprise with a Purge Cache button instead, because Cloudflare Enterprise handles edge caching for the site.
Edge Full Page Cache
Edge Full Page Cache is an optional layer of caching at the network level that improves your website’s performance. This feature caches the website’s HTML and stores it on Cloudflare’s CDN network, enhancing the Time to First Byte (TTFB) and latency for most websites.
How Does Edge Caching Work?
Edge caching operates by strategically distributing cached copies of website content across multiple servers at the edge of a content delivery network (CDN), closer to end-users. Here’s a detailed breakdown of how it works:
Request Routing: When a user/visitor requests content from a website, such as HTML files, images, videos, or other resources, their request is initially routed to the CDN’s edge servers, which are distributed worldwide.
Edge Server Selection: The CDN intelligently selects the edge server nearest to the user requesting the content. This selection is based on factors such as the user’s geographical location, network conditions, and server availability.
With over 300 edge server locations worldwide powered by Cloudflare, your content is delivered from the edge server nearest to the visitor. This reduces the need for requests to travel across continents to your origin server, minimizing latency and improving page load times significantly.
What You Need Before You Start
- Cloudflare SSL on the site. The Cloudflare Edge Cache switch stays disabled until the site uses Cloudflare SSL.
- A Cloudflare account connected to xCloud, with the site’s domain in that account. If the domain is not there, xCloud refuses to turn on the edge cache and asks you to add it to Cloudflare first.
Steps to Enable the Edge Full Page Cache in xCloud
Caching content at the network edge significantly improves website performance by reducing latency and load times for visitors. xCloud makes it easy to enable full-page caching using their Edge Caching feature, allowing for a faster and more responsive experience for your users. This guide will walk you through the process of enabling Edge Full Page Cache in xCloud step-by-step.
Step 1: Access the Site Dashboard
First, navigate to the dashboard of the site where you want to enable Edge Caching. Once logged in, locate and click on the ‘Caching’ option from the main menu.

Step 2: Enable Edge Caching
Turn on Cloudflare Edge Cache. A settings panel opens below the switch, with Advanced Settings and a Clear Edge Cache section. Nothing is applied yet: the edge cache only starts after you click Save Changes in Step 4. Open Advanced Settings.

Step 3: Configure Cache Exclusion Rules
In the Advanced Settings menu, you will find options to customize caching behavior:
-
Cache Exclusion HTTP URL Rules: Specify URL patterns you want to exclude from being cached.
-
Cache Exclusion Cookie Rules: Define cookie-based rules to prevent caching for certain sessions or users.
Set these rules according to your specific preferences or requirements.

Step 4: Save Changes, Then Purge Cache
Click Save Changes. xCloud shows a message that Cloudflare Edge Cache has been enabled, then creates the Cloudflare cache rule. Next, click Purge Cache under Clear Edge Cache. This clears all previously cached content from Cloudflare’s edge network, so visitors get pages that follow your new rules.

After that, if you go to your WordPress dashboard → Plugins → Must-Use, you will see the plugin ‘xCloud Cloudflare Edge Cache’ has been installed on your site. From here, if you go to the header menu, you will see a ‘Cache’ menu in the WordPress admin bar. Hover over it and click ‘Purge edge cache’ to purge the whole Cloudflare cache for your site.

And that’s it. This is how easily you can enable Edge Full Page Cache in xCloud and enhance your site’s performance and user experience. By carefully setting exclusion rules and purging outdated cache, you ensure that your visitors receive the most up-to-date and optimized content.
Things to Know Before Enabling Edge Caching
Here are some important considerations to keep in mind when using Edge Caching with xCloud.
Geolocation Variations
Edge Caching does not support narrow-scope geolocation variations, such as caching based on city, state, or border proximity. Sites relying heavily on localized content variations may need to consider alternative caching strategies.
Geo-blocking and IP Blocking
Geo-blocking and IP Deny rules are enforced at the server level (Nginx). Since Edge Caching happens on Cloudflare’s network, visitors from blocked IPs or regions could still access cached versions of your site. Additionally, visits from these blocked IPs will still appear in your site’s analytics data.
Set-Cookie Header Conflicts
Pages that send a Set-Cookie header by default are not cached at the edge. To prevent caching visitor-specific data, Cloudflare automatically removes the Set-Cookie header from cached responses for all new sites. This ensures the cache remains consistent and secure.
Cloudflare APO
If your Cloudflare account uses Automatic Platform Optimization (APO), the two can conflict. We recommend turning APO off first.
General Behavior and Compatibility
It’s important to note that after clearing the Edge Cache, you should allow 2 to 5 minutes for the purge to fully propagate across all Cloudflare data centers, as the process isn’t instantaneous.
Where Edge Caching Can Be Used
Edge Caching works on any WordPress site that has its own domain in your connected Cloudflare account and uses Cloudflare SSL, including a staging environment on your own domain. It is not available on demo sites or staging environments that use an xCloud staging domain. To use it there, move the site to your own domain with Cloudflare SSL first.
Content Served by Edge Caching
Edge Caching only caches and serves the page cache of your site, which refers to the HTML output, static assets such as images, JavaScript files, or CSS files.
WordPress Compatibility
Edge Caching is fully compatible with standard WordPress setups as well as popular plugins and frameworks like BuddyPress, WooCommerce, and Easy Digital Downloads. Pages that need to bypass caching, such as the WordPress Admin and the standard Cart, Checkout, and My Account pages, are automatically excluded from Edge Caching. If you renamed those pages, add them under Advanced Settings. Running a store? See the WooCommerce cloud hosting page.
For highly customized WordPress installations, additional custom caching rules may be necessary. The xCloud Support team is available to assist with creating these custom configurations if needed.
Cache Clearing Automation
The standard Edge Cache is not purged automatically when you update pages, themes, plugins or page-builder designs in WordPress. After a change, click Purge Cache on your site’s Caching page in xCloud, which clears the Site Cache and, when Edge Full Page Cache is on, the Edge Cache too. You can also use the Purge Cache button under Clear Edge Cache, or Cache → Purge edge cache in the WordPress admin bar, which purges the whole Cloudflare cache for the site. Sites on the Cloudflare Enterprise add-on are purged automatically when a post is saved.
Cloudflare Edge Cache File Size Limit
When using Cloudflare with xCloud, it’s important to understand that there are limitations on how large a file can be cached at the network edge. According to Cloudflare’s official guidelines, the maximum size for any single file cached on the edge is 512 MB for users on Free, Pro, and Business plans. This limit increases to 5 GB for Enterprise customers.
And files that exceed this size threshold won’t be cached at Cloudflare’s edge. Instead, those requests will bypass the edge and be delivered straight from your origin server — potentially resulting in slower performance for large files such as video content or software downloads.
If your site serves large files, consider these alternatives:
- Cloudflare R2: An object storage solution that lets you deliver large files efficiently without incurring egress costs.
- Disabling Cloudflare Proxy Temporarily: You can set the DNS proxy (orange cloud icon) to “off” to allow large files to be delivered directly from your server without passing through Cloudflare.
Edge Full Page Cache respects the cache-control headers configured by your page caching solution. For example, xCloud installs the FastCGI Cache plugin for NGINX servers, the LiteSpeed Cache plugin for OpenLiteSpeed (OLS) servers, or popular caching plugins like WP Rocket, depending on your server environment.
The bulk page cache purge in the xCloud Public API and MCP clears the page cache on your server only. It does not clear the Edge Full Page Cache.
Troubleshooting Edge Caching
If Edge Caching doesn’t seem to be working properly on your xCloud site, there are a few steps you can take to diagnose and fix the issue.
Check for Excluded URL Patterns or Cookies
Another potential cause is exclusion based on URL patterns or cookies. Specific sections of your site, like /cart or /checkout, might be configured to bypass caching automatically. Similarly, pages that depend on custom cookies, such as login sessions or shopping carts, might also be excluded. If you expect a page to be cached but notice that it isn’t, it’s a good idea to contact xCloud Support. They can help verify whether certain pages or cookies have been intentionally excluded from caching or whether any additional custom caching rules are influencing this behavior.
Password Protection and Edge Caching
If your site has Password Protection (Basic Authentication) enabled, Edge Caching cannot function. Password protection must be disabled for Edge Caching to work successfully. Make sure to check this setting if Edge Caching appears inactive after other troubleshooting steps.
Conflict with Cloudflare APO
If your Cloudflare account uses Automatic Platform Optimization (APO), the two can conflict. We recommend turning APO off first.
Geo-blocking and IP Blocking Considerations
Since Edge Caching operates at Cloudflare’s network level, it does not respect geo-blocking rules that are configured at the server (Nginx) level. This means visitors from regions that you intended to block might still receive cached content. Similarly, IP addresses that have been blocked via xCloud’s IP Deny tool may still be able to access cached pages through Cloudflare’s edge network. If maintaining strict geo- or IP-based access control is critical for your site, you may want to reconsider enabling Edge Caching.
Still stuck? Contact our support team for any of your queries.