Look & Settings
Why a change is not showing yet
Website caching, clearing it, and the other reasons an edit seems not to have worked.
Last updated September 2, 2026
Websites are cached so they load quickly. That means a change you have just saved may not appear on the public site straight away — which is the single most common "the website is broken" report.
Clearing the cache
The cache can be cleared automatically when content changes, or cleared on demand. Automatic clearing is right for most organisations; the manual option is there for when you need it now.
Work down this list
| Check | Why |
|---|---|
| Did you save? | More often than anyone admits. |
| Is the page published? | A draft page is not served. |
| Clear the website cache | The usual answer. |
| Hard-refresh your own browser | Your browser caches too, separately. |
| Try a private window | Rules out your own browser entirely. |
| Are you looking at a tribe version? | A customised local page does not inherit central changes. |
THE LAST ONE CATCHES EVERYONE
An edit made centrally will never appear on a page a tribe has customised. If one location is showing old content and the rest are fine, it is a local version, not a cache.