When a website update appears in one place but not another, the fastest approach is to identify which cache layer is serving the stale response.
Use a controlled test
Change one harmless piece of content, note the exact URL and test it in a private browser window. Do not keep republishing the same page while diagnosing the cache.
Separate CDN cache from WordPress/server cache
Hostinger notes that CDN Development mode affects the CDN layer only. Its CDN troubleshooting documentation recommends clearing remaining LiteSpeed/server and WordPress caches if the problem persists.
Temporarily isolate the CDN when necessary
If disabling the CDN makes the correct version appear, the CDN is part of the problem. If the stale content remains, focus on the application/server cache instead.
Check for overlapping CDN/proxy services
Running multiple proxy/CDN layers can complicate caching and redirects. Know which service is authoritative before changing DNS or redirect rules.
Related guides
For a full cache-layer sequence, see How to Clear WordPress and Hostinger Cache Properly. If the theme updated but the site did not, use our theme update checklist.
Cache-layer diagnosis matrix
Use the symptom as evidence. Change one variable at a time so you can tell which action actually fixes the problem.
| What you see | What it suggests | Best next check |
|---|---|---|
| Private window correct, normal browser stale | Browser cache | Hard refresh or clear only browser data for the site |
| Logged-in correct, logged-out stale | WordPress/page/server cache | Purge the active page cache and retest |
| CDN bypass correct, normal route stale | CDN edge cache | Purge/isolate the CDN layer |
| All routes stale | Origin/template/build issue | Verify the live WordPress content/theme before more purges |
What not to do
Do not repeatedly purge every cache and republish the page. Use one harmless test change and isolate browser, WordPress/server and CDN layers in order.
How to verify the fix
Retest the exact URL logged out, in a private window and—if relevant—through the normal CDN route. All views should show the same current content.
When to escalate
If the problem persists after the evidence-based checks, preserve screenshots, timestamps, the exact affected URL and any relevant error/log entry before contacting hosting or plugin support. That gives support a reproducible case instead of a generic “site not working” report.
