Why Won't My Published Site Show Updates?

If you've published changes to your website but aren't seeing them appear, the most common cause is caching. This article explains why this happens and how to see your latest changes.

Understanding Site Caching

When you publish your website, Zipper caches (temporarily stores) your site content for up to 5 minutes. This caching helps your site load faster for visitors, but it means changes won't appear instantly after publishing.

How to See Your Latest Changes

Step 1: Wait 5 Minutes

After clicking Publish in the site editor, allow up to 5 minutes for the cache to refresh. Your changes will automatically appear once the cache expires.

Step 2: Try a New Browser or Incognito Window

Your web browser also caches pages you've visited. To bypass your browser's cache:

Open an incognito/private window:
- Chrome: Press Ctrl + Shift + N (Windows/Linux) or Cmd + Shift + N (Mac)
- Firefox: Press Ctrl + Shift + P (Windows/Linux) or Cmd + Shift + P (Mac)
- Safari: Press Cmd + Shift + N
- Edge: Press Ctrl + Shift + N
Navigate to your site URL in the incognito window
Check if your changes appear

Step 3: Hard Refresh (Alternative)

If you prefer not to open a new window, try a hard refresh:

Windows/Linux: Press Ctrl + Shift + R or Ctrl + F5
Mac: Press Cmd + Shift + R

Tips

Changes to images may take slightly longer to appear due to additional image caching
If you're testing on mobile, close and reopen your browser app completely
Share your site link with a friend or colleague—they'll likely see the latest version since they won't have cached data

Troubleshooting

Problem: Changes still don't appear after 5 minutes and trying incognito
Solution: Verify that you clicked Publish after making your edits. Changes saved in the editor are not live until you publish them.

Problem: Only some changes appear
Solution: Make sure you saved all pages you edited before publishing. Each page needs to be saved individually.

Problem: Changes appear on desktop but not mobile (or vice versa)
Solution: Mobile devices cache aggressively. Force close your mobile browser and reopen it, or wait up to 10 minutes for mobile caches to refresh.