Preserve evidence about which response is old before you purge the whole stack.
Confirm the change exists at the origin
Start with the exact published URL, not only an editor preview. Confirm the update was saved and published, and check that you are viewing the correct language, domain and page variant. On staging, use a short unique sentence as a marker. This separates a publishing mistake from a caching problem before you touch infrastructure.
Classify the old item
Is the HTML showing the previous sentence, or is fresh text displayed with an old layout? Use browser network tools to inspect the document and stylesheet requests separately. HTTP caching stores responses for reuse, and different resources can have different freshness rules. Keep the request URL and the observed response beside the expected result.
Compare independent visitors
Check a fresh browser profile and a normal returning session. Then compare a signed-in view if your system treats it differently. Record the combinations that are stale. Do not assume that a hard reload purges a managed CDN or host cache; follow the documented controls for the layer you are investigating.
Change one layer at a time
Write down the current cache status headers if your provider exposes them. Purge the relevant managed layer, repeat the same request and note whether the marker changes. If the document is fresh but a resource remains old, investigate that resource's URL and deployment process. Ask a developer whether asset versioning is configured correctly rather than editing headers blindly.
Close the loop with a publishing check
Once you find the cause, add the verified action to your team's publishing routine. Include a public-page check and the responsible person's name. If the cause remains unclear, give support the request time, URL, session state and headers. A precise report is more useful than saying you cleared the cache many times.
Put it into practice
- Verify the saved and published content.
- Separate document and static-resource requests.
- Compare independent browser sessions.
- Record headers before the relevant purge.
- Retest the exact URL and document the cause.
AI-assisted educational content prepared for the Velonic resource library. How these guides are prepared.