Cache and performance
Understand why published changes can take time to appear and how to refresh saved copies of pages.
On this page
You'll check why a published change is missing and refresh saved copies if needed. A cache is a saved copy of a page or file. It helps your site load quickly. After you publish, an older saved copy may remain briefly while the site refreshes it.
First check the publicationLink to this section
- Reopen the page or post in the Admin and confirm that it is published. Saving a draft does not update the public site.
- Check that you edited the correct page and, on multilingual sites, the correct language.
- Open the public address in another tab and reload it. Compare it with your preview; a preview can show unpublished work.
If a published change still does not appear, use the refresh tools your role can access.
Refresh the site's pagesLink to this section
-
Open General Settings → Troubleshoot.
-
Select Revalidate all pages. The button changes to Click again to confirm.
-
Select it again. Wait for the success message, then reopen the public page.
This clears the site's saved page copies. Each page is rebuilt when it is next visited, so that first visit can take slightly longer. It does not publish drafts or change your content.
Cloudflare toolsLink to this section
Cloudflare can keep another saved copy in front of your site. Revalidate all pages does not clear that separate copy.
Open Cloudflare and review the Cache tab. Some controls require additional permission and may be unavailable to your role. Available settings apply as soon as you change them; this page does not require a separate save. Leave the Security and Speed settings to your agency unless they have explained the change you need.
| Field or control | What it does | Tip |
|---|---|---|
| Auto-purge on publish | Clears relevant Cloudflare copies when content is published, when configured. | Your agency can confirm which changes it covers. |
| Purge by URL / Purge URLs | Clears saved copies for specified public addresses. | Start with the affected address. |
| Purge entire cache | Clears Cloudflare's saved copies across the site. | Use sparingly; the next requests may be slower. |
| Development mode | Temporarily bypasses Cloudflare caching, normally for three hours. | Use with your agency when checking a persistent problem. |
| Apply recommended settings | Applies the site's recommended Cloudflare settings. | Ask your agency before changing unfamiliar performance settings. |
On sites showing cache buttons in the public Admin bar, Clear cache refreshes the current page and Clear all caches offers a wider refresh with confirmation. Their availability depends on your site and role.
The dashboard's Cache widget shows how much traffic Cloudflare served from its saved copies. A high cached share can be normal and helpful; it does not mean content is out of date.
Check afterwardsLink to this section
Reload the public page and check the specific change. If it is still missing, tell your agency the address, what changed, when you published, and which refresh tool you used. Images and social-sharing previews can also have their own saved copies.