Start with a visible version marker
When a change seems missing, compare the expected content with the deployed file. A small release note or a known sentence can help identify which version is being served. Confirm the hostname: a preview deployment and a production address may intentionally show different releases.
Do not begin by clearing every cache you can find. That can hide the source of the problem and disrupt unrelated work. First establish whether the correct build was produced and uploaded to the correct project.
Freshness and validation are different
HTTP caching allows responses to be reused under defined conditions. A response may be reused while fresh, or a client may ask whether an existing copy is still valid. Directives such as no-cache and no-store have different meanings; no-cache does not simply mean “never keep a copy.”
The browser is not always the only cache involved. A shared intermediary or content delivery network may also serve a response. Inspect the relevant response headers and the hosting documentation before changing cache rules.
Choose a fix that matches the layer
If the deployed HTML is old, publish the correct build. If an asset changed under an aggressively cached filename, use a versioned filename and update references. If a rule is unsuitable, adjust that rule deliberately rather than repeatedly purging content.
After the fix, test a normal visit and a direct link to an inner page. Keep HTML and assets compatible during deployment transitions. A reliable publishing process should not require every visitor to know a special refresh shortcut.
Further reading
Original sources and related references. These links lead to independent websites; inclusion does not imply a partnership or endorsement.
- MDN Web Docs — HTTP caching ↗
A detailed explanation of freshness, validation, and cache directives. Useful when a website appears to show an older version.
- Cloudflare Developers — Pages Direct Upload ↗
The deployment method used by Zeorgo. Explains how prebuilt files become a hosted Pages site and the limits of this project type.