Clear cache and check changes
Refresh cached pages after a website update and narrow down a slow or outdated page.
In this guide
When to clear the cache
Caching lets a website reuse prepared content instead of rebuilding every response. It can also mean a visitor sees an older copy just after you update a page, theme, or stylesheet. Clear the relevant cache after confirming that the change was actually saved on the live website.
First check the address and environment. A change saved only in staging, a draft that has not been published, or an edit to a different page will not be fixed by clearing cache.
Clear the website cache
- Open Websites in your Kiro client area and choose Manage website for the correct domain.
- On Overview or Settings, find Clear cache.
- Select it once and wait for the result. If the action fails, keep the error message for troubleshooting.
- Open the affected page in a new private browsing window and compare it with the version you expect.
Private browsing is a useful comparison, not a guarantee that every upstream cache has been bypassed. Test both a normal visitor view and any signed-in view involved in the problem.
If old content remains
- Confirm the page was published or updated successfully in WordPress.
- Refresh the browser and check whether the problem appears on another device or network.
- If you manage a separate caching plugin or external delivery service, review its documented purge controls too.
- Change one caching setting at a time so you can tell which layer affected the result.
If the site is slow
Separate a slow website from a slow hosting-dashboard refresh. Visit the public page directly and record whether the delay affects every page, only the editor, or a specific action such as a search. Note when the issue began and which plugin, theme, image, or external script changed around that time.
For support, include an affected URL, the approximate delay, device or browser, and whether you were signed in. Use staging to investigate plugin conflicts or heavier changes. Repeatedly purging a cache is not a substitute for finding the source of a persistent slowdown.