Skip to content
Cloud docs

The site shows the wrong content or an old version

Almost always caching. Work through the layers from the outside in.

Updated 20 September 20261 min readBeginner

You published a change and the site still shows the old one. Test in this order; each step rules out one layer.

  1. Open a private window

    Still old? Your browser was not the problem.

  2. Purge the page

    Sites → Cache → Purge URL with the exact address.

  3. Check for a second proxy

    Your own Cloudflare account has its own cache and its own purge.

  4. Flush the object cache

    Settings that refuse to change are usually a cached option row.

  5. Confirm you edited the live site

    More common than it sounds: the change was made on staging, or on the old host whose DNS has not fully switched.

terminal
# which server answered, and was it cached
curl -sI https://example.com | grep -i 'server\|cache\|age'
If only some visitors see the old version

That is DNS, not cache. Part of the internet is still resolving to the old host. Wait for the TTL to expire.

Was this article helpful?

Related articles