Client Portal
Knowledge Base

How do I clear my website's cache after a change?

A cache is a saved copy used to load a page or file faster. If visitors still see old content after a confirmed website change, clear the website's cache, then any separate content-delivery service and finally reload your browser. For a WordPress site using LiteSpeed Cache, open LiteSpeed Cache → Toolbox → Purge and choose Purge All - LSCache. Do not delete website files to clear a cache.

Confirm the change was saved

  • Open the affected page in your website editor and confirm the update was saved or published. Check that you changed the correct website, page and language version.
  • Test the public page in a private browser window. This helps separate a browser-specific issue from content served to visitors, though private browsing does not bypass a website or network cache.
  • If the site has an error or a change was not saved, clearing cache will not repair the underlying problem. Keep the error and check the relevant change first.

Clear the WordPress page cache

  • Sign in to that website's WordPress dashboard. For a site with the LiteSpeed Cache plugin, choose LiteSpeed Cache → Toolbox → Purge.
  • Choose Purge All - LSCache to clear its saved page copies, then wait for confirmation. Reopen the affected public page. The first visit after clearing may be slower while the copy is rebuilt.
  • Do not use Empty Entire Cache, database-cleaning tools or settings resets as a substitute for the page-cache action. Those are different operations with a wider effect.
  • If the site uses another caching plugin, use that plugin's documented cache-clear action. If you do not know which cache is active, ask your developer or Tech/Server with the website address and plugin name. Installing a second caching plugin is not a way to clear the first one.

Check a separate content-delivery service

  • A content-delivery network, often called a CDN, can keep another saved copy outside the hosting account. Clearing WordPress does not necessarily clear it.
  • If your website uses a CDN, open that service's dashboard and use its documented purge action for the affected address or files. Check the selected site before clearing a whole domain's cache.
  • Do not change DNS, switch off protection or disconnect the CDN simply to refresh an old image. If you do not manage that service, ask the person who does to clear the relevant copy.

Refresh your browser and test

  • After the website and CDN caches have been cleared, reload the page and test it in a private window again. If only your usual browser remains stale, use its settings to clear cached images and files for the site.
  • Avoid clearing saved passwords, cookies or all browsing data for this task. Clearing cookies can sign you out and remove browser-held cart information.
  • Test the changed page as a visitor. For shops, check cart and checkout without placing a paid order. Do not enable public caching for private account pages or checkout to make the result look faster.
  • If old content persists, send Tech/Server the exact page, what changed, when it changed and which caches you cleared. Do not repeatedly purge unrelated sites on the account.