A customer messages you that the old price is still on your website. You open the page and the old price is there too, although you changed it an hour ago. Or you see the new price and your customer sees the old one. Nothing is broken, but it is unsettling, and it is easy to waste an afternoon on the wrong fix. This guide is for a business owner or office manager who edits their own website and wants to work out, in a few minutes and without technical help, why a change is not showing. It explains the three places an old copy usually hides, gives a short test sequence, shows how to tell a change that was never saved from one that is only cached, and says what to send support if you need help. Tools and hosts differ, so treat this as a method rather than a promise about any one setup.
Why one screen can show an old page, and the usual order of causes
When you open a web page, your browser asks a web server for several files: the page itself, its style files, scripts and images. To make pages load faster, copies of those files are kept at several points along the way. A saved copy kept for reuse is called a cache. A cache keeps showing its copy until the copy expires or is replaced. So the usual explanation is not that your edit failed. It is that you changed the original while a saved copy was still being shown.
There are three common places for that copy, and the order matters, because the nearest one is both the most likely and the quickest to rule out:
- 1. Your own browser. Browsers keep copies of pages, images and styles on your computer or phone. This is the most common cause, and it explains why a colleague sees the new page while you see the old one.
- 2. A cache on the site or the server. A caching plugin on the website, a cache run by the web server, or a service sitting in front of the site can keep a ready-made copy and hand it to every visitor until it is refreshed. If everyone sees the old page, this is the next suspect. A CDN is one such service, and what a CDN is and whether you need one is its own topic.
- 3. DNS, but only after a hosting or domain change. DNS decides which server a domain name leads to. If you recently moved hosting or changed domain settings, some devices may still be sent to the old server, which holds the old site. If nothing has moved, DNS is an unlikely cause, so do not start there. How DNS lookups work is explained separately and not repeated here.
A fourth possibility is worth ruling out early: the change was never saved or uploaded in the first place. That is covered below. And if the old text is only in Google search results, not on your own screen, you have a different problem, covered in why a website is not showing on Google.
The test sequence: four checks in about five minutes
Run these in order and write down what you see at each step. That short record is also what support will ask for if you need help.
- Hard refresh. A normal reload may reuse saved files, while a hard refresh asks for fresh ones. On Windows, in most browsers, hold Ctrl and press F5, or press Ctrl+Shift+R. On a Mac, in most browsers, hold Command+Shift+R. Safari and some other browsers use different shortcuts, so search your browser’s name with “hard refresh” if these do nothing. On a phone, close the tab or the app completely and open the page again.
- Private window. Open the same address in a private window, which browsers name differently (Incognito, InPrivate or Private). It starts without the copies saved during normal browsing. If the new version shows here but not in your normal window, the cause is your browser’s saved copy.
- Another device on mobile data. Use a phone with Wi-Fi switched off. A different device has its own saved copies, and mobile data uses a different network path, so this also rules out something local to your office network.
- Another browser. If you have a second browser installed, open the page there. It does not share saved copies with the first.
Now read the pattern. New in the private window but old in your normal one: your browser. Old on every device and every browser: not your browser, so look at the site, the server or the change itself. Different on office Wi-Fi and on mobile data: something about the network, or DNS if you recently moved. Clearing a browser’s saved files for one site is safe: it removes saved copies, not your website.

Never saved, or cached? Check before you blame the cache
Sometimes the change is simply not on the server. The edit was made in a draft, the upload failed, the file went into a different folder, or you worked on a test copy while the live site is separate. (If you use a test copy, how a staging site works explains why the live site does not change until you publish.) Here is how to tell:
- In an editor or page builder: reload the editor itself and confirm your change is still there. Check whether the page is marked draft or published, and whether the tool has a separate Publish or Update button.
- In File Manager: in cPanel, File Manager lists each file with a last-modified date and time. Find the file you changed. If its date is older than your edit, your upload did not replace it. If the date matches your edit, the new file is on the server, and the old view is a saved copy somewhere.
- In the right folder: a site is served from one specific folder. A file uploaded to a similarly named folder has no effect. If you are unsure which folder your site uses, ask your web designer or support before moving anything.
- At the file’s own address: for an image or a style file, open its address directly in a private window. You see the file the server is actually holding.
- Mind the clock: the time shown is usually the server’s, which may not match your local time, so compare the order and rough gap rather than the exact hour.
| What you find | What it means | Next step | |
|---|---|---|
| File date is older than your edit | The save or upload never reached the server | Save or upload once more, check the folder, then check the date again | |
| File date matches your edit, but a private window on mobile data shows old | A cache on the site, server or in front of it | Use the site’s own clear-cache option if it has one, then ask support | |
| File date matches and the private window shows new | Only your browser holds the old copy | Hard refresh, or clear saved files for that site | |
| You edited a draft or a test copy | The live page was never changed | Publish, or copy the change to the live site | |
Why images and styles can stay old while the text updates
A page is made of many files, and each is saved separately, often for different lengths of time. The words are in the page file. Style files, scripts, images and fonts are usually kept longer because they rarely change. That is why you can get new words with an old look, or a new price beside an old logo.
- Same file name. If you replace logo.png with a new file also named logo.png, a browser may think it already has logo.png and keep showing the old one. The simplest fix is to save the new file under a new name, such as logo-2026.png, and point the page to it.
- Style files. A colour or layout change lives in a style file. Until the browser fetches the new one, the page can look unchanged. Many sites add a version number to the file name or address to force this, so ask your web designer how yours is set up.
- Several sizes of one image. Some website tools create smaller copies of an uploaded image. Replacing the original may not replace those copies, so the old picture can keep appearing in some places.
- Link previews. When you share a page on a messaging or social app, the preview picture and title can be kept by that app for a while, separately from your browser. If the preview is old but the page is new, this is likely why.
- PDFs and price lists. A PDF is a file like any other. If you replace a price list with the same name, expect the same effect, and consider a new name.
What a caching plugin or server cache can hold back
If your site runs on a platform with plugins, such as WordPress, it may use a caching plugin that saves ready-made copies of pages so they load faster. It will keep serving the saved copy until the copy expires or is cleared. A cache run by the web server, or by a service in front of the site, works on the same idea. What they can hold back is not only the page you edited, but also pages that show it, such as a home page that lists your latest products, a menu, a footer or a price that appears in several places.
If your site uses a caching plugin, its own clear-cache button is the usual next step. Look in that plugin’s own settings, or in the toolbar of your site’s admin screen, because the name and the place differ by plugin. Clearing a cache removes saved copies, not your actual pages or files. Clear one layer at a time and run the four checks again, so you learn which one made the difference. If a CDN sits in front of the site, it is another layer, and it may have its own clear option.
A server cache is different, because you may not control it yourself. Whether your hosting plan keeps one, how long it keeps pages and whether you can clear it are questions for your host, not something this guide can answer. Ask in writing:
- Does my plan keep a cache of my pages at the server, and how long does it keep them?
- Can I clear it myself, and where?
- Does it also apply to images and style files?
- Do you recommend a caching plugin on my site, or could the two conflict?
For how web servers handle caching in general, see LiteSpeed vs Apache hosting. Keep in mind that removing caching altogether is rarely a good fix, because pages usually load slower without it, and site speed is its own concern.
When DNS is the cause
DNS only comes into play when the website moved or the domain’s settings changed: a new host, new nameservers, or an edited record that points the name at a server. After a change like that, some devices can keep being sent to the old server for a while, while others reach the new one. The old server holds the old site, so this is not a stale copy but a different place. How long the switch takes varies and cannot be promised, so confirm with an online DNS lookup tool or with support.
Signs that point to DNS:
- You moved hosting or changed domain settings in the last few days.
- Different people, devices or networks see different versions of the site.
- Mobile data shows one version and your office Wi-Fi shows another.
- Your edits on the new account appear nowhere you look, while the old site is still visible.
If this is you, do not keep re-uploading. Check first that you are editing the account the domain now points to, because after a move it is easy to keep editing the old one. The steps for moving safely are in moving a website without downtime. If you have not changed hosting or domain settings, set DNS aside.
What to tell a customer who reports an old page
A customer who reports an old page is a useful data point. If they see the old version while you see the new one, their browser, or a cache between you and them, is the likely cause. Keep your reply short, polite and free of jargon, give them one thing to try, and ask for the details you need. Before replying, open the page in a private window yourself so you know what is live right now.
Suggest a private window first, not “clear your cache”. A private window is harmless and quick, while clearing all browsing data can sign people out of other sites. This is an example, with made-up names (a bakery called Melur Bakery and customers Mr Tan and Puan Aisyah), in three languages. Adapt it freely.
- English: “Hi Mr Tan, thanks for telling us. We updated the price list this morning, so you may be seeing a saved copy of the old page. Could you try opening the page in a private or incognito window, or on your phone using mobile data? If you still see the old prices, please send us a screenshot and the time you checked, and we will look into it. Sorry for the confusion. Melur Bakery”
- Bahasa Malaysia: “Hai Puan Aisyah, terima kasih kerana memaklumkan. Kami mengemas kini senarai harga pagi tadi, jadi anda mungkin masih melihat salinan lama halaman itu yang disimpan. Boleh cuba buka halaman dalam tetingkap peribadi (incognito) atau pada telefon menggunakan data mudah alih? Jika masih nampak harga lama, sila hantar tangkapan skrin dan masa anda menyemaknya, dan kami akan menyemaknya. Maaf atas kekeliruan. Melur Bakery”
- Chinese: “陈先生您好,感谢您告诉我们。我们今早更新了价目表,您看到的可能是浏览器保存的旧页面。请您试试用无痕(隐私)窗口打开该页面,或用手机的移动数据打开。如果仍然是旧价格,请把截图和您查看的时间发给我们,我们会跟进处理。给您带来困扰,非常抱歉。Melur Bakery”
When to open a ticket, and exactly what to include
Ask for help when the four checks still show the old page on every device, the file date in File Manager is new, and you have used any clear-cache option your site has. Also ask if the file date stays old after you uploaded once more, if results differ for several days after a hosting or domain change, or if you cannot find where a cache is controlled. A support person can do much more with precise details than with “my website is not updating”. Include:
- The page address. The exact address of the page, with https and the full path. For an image or style file, give that file’s own address.
- What you changed. What the change was, where you made it (editor or File Manager) and, for a file, its name and folder.
- The time. The date, time and time zone you made the change, and the time you checked.
- Screenshots from two devices. For example a laptop in a private window and a phone on mobile data, each showing the old content, with the address bar visible.
- What you tried. The four checks and what each showed, and whether you used a caching plugin’s clear button and when.
- Recent changes. A hosting move, a domain or DNS change, or a newly installed plugin.
- No passwords. A ticket never needs your password.
A short template: “On [date] at about [time] (MYT) I changed [what] on [page address] using [editor or File Manager]. At [time] the page still shows the old version on my laptop (private window) and on my phone (mobile data); screenshots attached. File Manager shows the file last modified [date and time]. I have tried a hard refresh and [plugin clear-cache button, if any]. Recent changes: [hosting or domain change, if any].”
Quick decision table
| What you see | Most likely cause | What to do next | |
|---|---|---|
| New in a private window, old in your normal window | Your browser’s saved copy | Hard refresh, or clear saved files for that site | |
| Old on every device, and the file date is old | Never saved or uploaded | Save or upload once, check the folder and the date | |
| Old on every device, but the file date is new | A cache on the site, server or in front of it | Use the plugin’s clear-cache button, then ask support about any server cache | |
| New text, old images or colours | Separately saved files, often with the same name | Use a new file name, or ask how style files are versioned | |
| Old on office Wi-Fi, new on mobile data | Something local to that network, or DNS after a move | Test again later and ask support if it persists | |
| Different people see different sites after a move | DNS, with the old server still answering | Confirm you edit the right account, wait, then ask support | |
| Old title or snippet only in Google results | A search engine’s own copy | See why a site is not showing on Google | |
| A customer sees old, you see new | The customer’s browser or a cache between | Send the short reply above | |
Common mistakes
- Re-uploading the same file ten times. If File Manager shows a new date, the file is already there. More uploads change nothing.
- Restoring a backup to fix a cache. A restore swaps your current files for an older copy, so it can wipe recent edits, posts or orders, and it does not touch what a browser or cache has saved. Backups are for recovery, not for display problems.
- Clearing every cache at once. You fix it but never learn which layer was responsible, so it happens again.
- Testing in the same window. Always test in a private window or another device, not the tab that showed the old page.
- Blaming DNS without a move. If you have not changed hosting or domain settings, DNS is unlikely.
- Switching caching off for good. The page may update, but it can load more slowly for everyone.
- Editing the old host after a move. The domain points to the new account, so edits to the old one never show.
- Telling customers to “clear your cache” with no explanation. Ask them to try a private window first.
- Waiting without a record. Note the time of your change and your checks, so support can find it in their logs.
Where Gotka Technologies fits
Gotka runs cPanel hosting on LiteSpeed web servers, and cPanel is where most owners find File Manager for checking a file and its date. Plans also include daily backups, which help you recover files but do not fix a page that looks old. Gotka offers domain registration from RM10/yr, and a web design service that runs from design through ongoing maintenance, which can suit owners who would rather not edit the site themselves.
This guide does not state whether Gotka plans use a server cache, how a cache behaves, how long pages are kept, whether you can clear one from the client area or cPanel, which caching plugin to use or whether a CDN is involved, because none of that is published in the material it can cite. Ask support the questions above in writing through the client-area ticket system, or call or WhatsApp +60 11-6331 6630, Monday to Friday, 9am to 6pm (MYT).
Key terms used in this guide
- Cache: a saved copy kept so a page or file can be shown faster next time. It can be old.
- Browser cache: copies of pages, images and styles stored by your browser on your device.
- Hard refresh: a reload that asks for fresh copies instead of reusing saved ones.
- Private (incognito) window: a browser window that starts without the copies saved in normal browsing.
- Caching plugin: an add-on for a website platform that saves ready-made copies of pages.
- Server cache: a cache kept by the web server or a service in front of it. Whether it exists depends on the host.
- CDN: a service that keeps copies of a site at locations nearer visitors. Covered in its own guide.
- DNS: the system that links a domain name to the server behind it.
- Propagation: the time it takes for a DNS change to be seen everywhere. It varies and is not guaranteed.
- File Manager: a cPanel tool for browsing a site’s files and checking their dates.
- Last modified: the date and time a file was last changed on the server.
- Cache busting: changing a file’s name or address so caches fetch the new version.
Why does my website still show the old version after I updated it?
Usually because a saved copy is being shown instead of your new one. The most common place is your own browser, then a cache on the site or server, and only after a hosting or domain change, DNS. It can also be that the change was never saved or uploaded. Test with a hard refresh, a private window, a phone on mobile data and a second browser to find out which.
How do I do a hard refresh?
On Windows, in most browsers, hold Ctrl and press F5, or press Ctrl+Shift+R. On a Mac, in most browsers, hold Command+Shift+R. Safari and some other browsers use a different shortcut, so check your browser’s help page. On a phone, close the tab or app completely and reopen the page, or use a private tab. If the page still looks old, try another device.
How can I tell whether my change was never saved or is just cached?
Open File Manager or your editor and look at the file and its last-modified date and time. If the date is older than your edit, the save or upload did not happen. If it matches your edit, the new file is on the server and the old view is a saved copy somewhere. The server clock may differ from yours, so compare the order, not the exact hour.
Why do my images and colours look old when the text has updated?
Each file on a page is saved separately, and images, style files and scripts are often kept longer than the page text. If you replaced a file using the same name, the browser may think it already has it. Upload the new image under a new file name, or ask your web designer how style files are versioned.
When is DNS the reason my website looks old?
Only after a hosting or domain change, such as moving to a new host or changing nameservers or records. For a while, some devices may still reach the old server while others reach the new one. How long this takes varies, so confirm with a DNS lookup tool or support. If nothing has moved, DNS is an unlikely cause.
What should I send support when my website shows an old page?
Send the exact page address, what you changed and where, the time you changed it and the time you checked, and screenshots from two devices, such as a laptop and a phone on mobile data. Add what you tried and any recent hosting or domain change. Never send passwords. Gotka customers can use the client-area ticket system.
Does this guide say how Gotka’s caching works?
No. It does not state whether Gotka plans use a server cache, how long pages are kept, whether a clear-cache option exists, which plugin to use or whether a CDN is involved, because none of that is in the material it can cite. Ask in writing through the client-area ticket system, or call or WhatsApp +60 11-6331 6630, Monday to Friday, 9am to 6pm (MYT).
Do You Need a CDN? What It Does (and Does Not Do) for a Malaysian Small-Business Website
A CDN serves copies of your images, CSS and scripts from nearby locations. See what it fixes, what it does not, who needs one and how to test before and after.
HostingWhat 99.9% Uptime Means in Minutes per Month (and What It Does Not Cover)
What 99.9% uptime means in minutes per month: 43.2 in a 30-day month. See the arithmetic, how it is measured and what it does not tell you about your site.
HostingHow Much Website Storage Does a Small Business Actually Need?
Most small business sites use just a few hundred MB to a few GB of storage in year one. What fills it up, and how to pick a Gotka plan from 50GB to 400GB.


