Why does my Cloudflare Pages custom domain still show the old site after a successful deployment?
Was this question useful?Community ranking
Answers
1 answer
A successful Pages deployment doesn't automatically mean the custom domain is serving that project yet. In the Pages project, check that the domain is actually attached under Custom domains, then verify its DNS points where Cloudflare expects—especially for an apex domain, which needs the domain managed as a Cloudflare zone with Cloudflare nameservers. If the domain is attached and DNS is right, look for custom Cache Rules on that hostname. Cloudflare says those can leave stale assets in front of a Pages deployment; try a Purge Everything once, then loosen or remove the rule that's caching HTML or redirects too aggressively.
Was this answer helpful?Community ranking
Your answer
Sign in to answer.
Keep exploring
Similar questions
Why is my Vercel production deployment still using an old environment variable value?1 answerWhy do my Cloudflare Pages Functions work on pages.dev but return 404 on my custom domain?1 answerWhy does my service worker still return an old response when it has Cache-Control: no-store?1 answerWhy does my PWA show the old version after a deploy and hard refresh while an incognito window is current?1 answer