HTTP caching stores responses for later reuse. MDN describes a browser cache as a private cache tied to a particular client, which differs from a shared cache serving multiple users. Whether a stored response can be reused depends on the caching rules, rather than simply whether the visitor has opened the page before. Source: MDN: HTTP caching

Check a first and a repeat visit

When reviewing a website update, test a fresh visit and a return to the page. Note which conditions you used and what appeared. This gives the website team a way to investigate a difference between the new content you expect and the version someone reports seeing.

Separate public and personal content

Ask the website team to review caching rules for public guides separately from pages containing booking or account details. Include those page types in the review because their information serves different audiences. Do not assume one setting is appropriate everywhere.

Written and updated by Travelgenix. Sources checked on 19 October 2026. Practical advice and examples are Travelgenix editorial guidance.