From 858d505e7e0b813e3b3bbdc389e4f4771ed92cb5 Mon Sep 17 00:00:00 2001 From: Josh Date: Fri, 26 Jun 2026 21:02:17 -0700 Subject: [PATCH] docs(how-to): add 'Clear your site's cache' guide Customer-facing troubleshooting for stale content: hard refresh (browser cache) first, then purge LiteSpeed Cache via the WP plugin Toolbox for Optimized Webserver sites, with a note that logged-in views are never cached. Cross-linked from the Optimized Webserver add-on page. Co-Authored-By: Claude Opus 4.8 (1M context) --- .../docs/whp/add-ons/optimized-webserver.mdx | 1 + .../docs/whp/how-to/clear-your-cache.mdx | 71 +++++++++++++++++++ 2 files changed, 72 insertions(+) create mode 100644 src/content/docs/whp/how-to/clear-your-cache.mdx diff --git a/src/content/docs/whp/add-ons/optimized-webserver.mdx b/src/content/docs/whp/add-ons/optimized-webserver.mdx index d7b7d11..68e7bfb 100644 --- a/src/content/docs/whp/add-ons/optimized-webserver.mdx +++ b/src/content/docs/whp/add-ons/optimized-webserver.mdx @@ -83,6 +83,7 @@ For the site-switching steps, see [Switching a site's backend](/whp/how-to/switc ## Related +- [Clear your site's cache](/whp/how-to/clear-your-cache/) — what to do when a change doesn't show up right away. - [Add-ons overview](/whp/add-ons/overview/) - [Resource upgrades](/whp/add-ons/resource-upgrades/) — if you need more CPU or RAM rather than a faster cache layer. - [Site Monitoring](/whp/add-ons/monitoring/) — pair with Optimized Webserver to catch any cache-related issues early. diff --git a/src/content/docs/whp/how-to/clear-your-cache.mdx b/src/content/docs/whp/how-to/clear-your-cache.mdx new file mode 100644 index 0000000..402a219 --- /dev/null +++ b/src/content/docs/whp/how-to/clear-your-cache.mdx @@ -0,0 +1,71 @@ +--- +title: Clear your site's cache +description: Seeing an old version of a page after making a change? Here's how to clear cached content so your updates show up. +sidebar: + order: 7 +--- + +import { Steps, Aside } from '@astrojs/starlight/components'; +import Support from '~/content/partials/support-link.mdx'; + +If you've changed something on your site but still see the old version — an updated page, a new image, a price, a published post — it's almost always **caching**: a saved copy of the page is being shown to make your site fast. Clearing the cache tells the system to build a fresh copy. + +There are two places a saved copy can live: in **your browser**, and on the **server** (if your site uses our [Optimized Webserver](/whp/add-ons/optimized-webserver/) add-on with LiteSpeed Cache). Work through the steps below in order — the first one fixes most cases. + + + +## Start with a hard refresh + +A normal refresh often reloads the page from your browser's own saved copy. A *hard* refresh forces your browser to fetch everything fresh from the server. + + + +1. Open the page that looks out of date. + +2. Do a hard refresh: + - **Windows / Linux:** press `Ctrl` + `Shift` + `R` + - **Mac:** press `Cmd` + `Shift` + `R` + +3. Still seeing the old version? Open the same page in a **private / incognito window** (which ignores your browser cache entirely). If it looks correct there, the issue was just your browser — clear your browser cache and you're done. + + + +## Purge the server cache + +If your site is on the **Optimized Webserver** add-on, pages are also cached at the server by LiteSpeed Cache. Most of the time this clears itself automatically — publishing a post, updating a page, or completing an order purges the right pages for you. Occasionally (after a large change, a theme edit, or a bulk update) you may want to clear it by hand. + +For WordPress sites, you do this from the free **LiteSpeed Cache** plugin: + + + +1. Sign in to your site's **WordPress admin** (`yourdomain.com/wp-admin`). + +2. In the left menu, go to **LiteSpeed Cache → Toolbox**. + +3. On the **Purge** tab, click **Purge All**. This drops every cached page; the next visitor to each page gets a freshly built copy. + + + + + + + +## If that didn't fix it + +- **Your site isn't WordPress**, or you don't have the LiteSpeed Cache plugin — there's nothing for you to purge directly. Contact us and we'll clear the server-side cache for you. +- **You purged everything and still see the old version** — give it a moment and try a hard refresh again. If it persists, it may not be a cache issue at all (for example, a change that didn't actually save, or a content/plugin problem). Reach out and we'll take a look. + +## Related + +- [Optimized Webserver (OpenLiteSpeed + LSCache)](/whp/add-ons/optimized-webserver/) — what the server-level cache is and how to enable it. +- [Switching a site's backend](/whp/how-to/switching-site-backend/) + +## Still stuck? + +