You can do nothing.

It is in the browser. It depends how the user has set up the browser.

Normally (for performance reasons) the browser uses caching.

Normally the user will see the changes after a while without the need to refresh. After closing the browser and after a reset of the PC.

Hello:
I honestly don't know if these meta tags still work in all current browsers.

What you have to take into account is that: Without cache, browsers will not save anything on the user's PC, which means more time each time they enter your site.

<meta http-equiv="Expires" content="0">
<meta http-equiv="Last-Modified" content="0">
<meta http-equiv="Cache-Control" content="no-cache, mustrevalidate">
<meta http-equiv="Pragma" content="no-cache">

You enter them in STEP 1 - Statistics and Code - Code - before the closing HEAD tag

Try and comment if they work.
Greetings.

Whether or not they work is tricky, as most (if not all) browser developers think of "making life easier for the user" and can block these meta tags from the browser core. (Same as for automatic audio playback.) Pretending that your browser is faster, but what they do is allow the use of the cache automatically.

As Miguel says it can be tricky. And the "problem" is both tricky and a paradox.

I advice you not to fiddle with the browsers.

You could make a refresh on page load. But that would cause a new refresh ... and so on.

You could make a refresh of the page in an interval of time. But this will be very disturbing for your users - and I guess it is not the same page that will be changed in your project.

Another paradox is, that you cannot tell the user that the page has been changed at xxxxxx and he should therefore make a refresh - if he sees the message it is not needed - if he does not see it is needed. A bit like Nanny Mc Phee

If you will have many and constant changes to your project, I suggest you put a button in the header or the footer, together with a small text that says something about that the project is often changed and if the user will be sure always to see the newest version he should push the button.

The code could be something like: <input type="button" value="Refresh page" onclick="location.reload(true);" />

And another thing: It is not always caused by the clients browser. Your ISP can also use caching and then a refresh of the browser will have no effect.

x Ghimpu O., ... (It > En)...if you don't have a cache blocker on your server side that you need to know about,  ...normally there shouldn't be any cache persistence problems, as it happens for all pages on the net...
... since you have not posted your LINK and attached the reference STAMP with the differences found in order to be able to evaluate, everything remains random...

...however, some problems could arise "only" in case of use of replaced images but keeping the same name(*), or in case of objects controlled with JS code...

(*) - easily circumvented with use of "absolute" URL, (or use in IFRAME, or with EXTRA code)...

.

ciao

.