Why some visitors still see your old site right after launch

The difference between DNS caching and browser caching

Launch happened. You've been checking the new site obsessively since then, and it looks right every single time you look. Then a text arrives: your cousin says they're still seeing the old one on their phone. Panic sets in fast, and the awkward part is you're not even sure what question to ask anyone to figure out what's actually going on.

Here's the boring, unglamorous explanation. It's almost always caching, and it resolves on its own without anyone having to do anything at all.

That's genuinely the whole story, most of the time. Nobody broke anything. The switch worked exactly as it should have. It's just taking a beat to reach every corner of the internet still checking its old notes.

There are two separate kinds of memory at play here, and they're genuinely easy to confuse. DNS caching happens at the network level: your internet provider, your router at home, sometimes your phone's carrier, all remember where your domain used to point, and take a while to notice it changed at all.

Browser caching is a completely separate thing, and it happens on a single device. Your browser saved a copy of the old page earlier, and shows you that saved copy instead of fetching a fresh one from the server. Both problems cause the exact same visible symptom, an old-looking site, but they get resolved in different ways.

Neither one means the launch went wrong. Both are just memory, doing what memory is supposed to do, a little too well for this one particular moment in time.

Knowing which kind you're dealing with tells you where to look for a fix, and where not to bother looking at all right now.

Why your phone and your laptop can show different versions at once

Each device, each browser, even each network you happen to be connected to, keeps its own separate memory of your site. Your phone on cellular data might already show the new site while your laptop on home WiFi still shows the old one. They're simply checking entirely different cached records, stored in different places.

This isn't a sign that anything is actually broken behind the scenes. It just means the update is arriving at different times to different places, the way a single piece of mail can reach two addresses on two different days depending on the route it travels.

There's no fix to apply here, because nothing is actually wrong. It just needs a little time to finish catching up on its own, quietly, in the background of every device involved.

What's actually happening behind the scenes while it settles

When the DNS change goes in, it doesn't broadcast instantly to every corner of the internet at once. Each network checks in on its own separate schedule and updates what it has stored locally. Until that check-in happens, that particular network keeps serving its old, cached answer to anyone who asks.

Browsers do something similar on a much smaller scale, holding onto a saved copy of a page to make everyday browsing feel noticeably faster. Both of these processes exist to make the internet quicker for everyone, day to day. They just create this one temporary side effect right after a change like yours goes live.

Give it a few hours before worrying about it at all. Give it a full day before treating it as anything more than ordinary settling.

How to check which version a visitor is seeing

A private or incognito browser window is the fastest check available to you, since it skips most saved data and fetches a genuinely fresh copy directly from the server. If the new site shows up there, the update has already reached that particular network. Any old version someone else happens to be seeing is sitting in their own device's memory, not a sign that the launch actually failed.

You can also simply ask the person seeing the old site to switch networks, from WiFi over to cellular data, for instance. If the new site shows up there instead, that confirms it's a caching issue rather than something genuinely broken with the launch itself.

Neither check takes more than a minute. Both are worth doing before assuming the worst about a launch that went fine. A quick text back to the family member saying "try your data instead of WiFi" usually settles it on the spot.

When this is normal and when it means something's wrong

A mixed picture in the hours right after launch is completely normal and expected. What's not normal is the old site still showing up everywhere, on every device and every network, well beyond that early window has passed.

If a private browser window on a fresh network still pulls up the old site, flag that directly to whoever handled the switch. It may mean the DNS change itself needs a second look, not just more waiting around for it to settle on its own.

The short version is simple. Patchy and inconsistent right after launch is expected, and nothing to lose sleep over. Consistent and unchanging days later is not, and deserves a direct question to whoever handled the technical side of the switch.

Will your website go down during a redesign covers whether this kind of thing counts as real downtime, and mostly it does not. If it doesn't resolve on its own the way it's supposed to, having a rollback plan for your website launch day covers what to do next.

For where this fits into the day as a whole, see what happens on website launch day, and for the bigger picture, how to redesign a website without losing what works.

More from the blog

All posts