Skip to main content
All fixes

Broken After a Change

Your Site Looks Fine to You but Broken to Visitors

Updated

What's happening

When your site looks fine to you but broken to visitors, you're almost always being shown two different copies of it, and yours is the good one. The usual cause is caching: as the logged-in owner you see the live site, while visitors get a stored copy that was saved at a bad moment.

Someone tells you your website is broken — missing images, a mangled layout, an old price, a page that won't load. You check, and it looks perfectly fine. You refresh. Still fine. The temptation is to assume the customer got it wrong. They usually haven't. If it's the other way round, and the site won't load for you but works for others, here's how to tell whether it's down for everyone.

Why it happens

Most often, this is caching. To make sites fast, your host, your caching plugin, and any CDN in front of your site can each keep pre-built copies of your pages and hand those out instead of rebuilding each page from scratch. When you're logged in as the owner, most of that is skipped so you always see the live version — which is exactly why you can't see what everyone else sees.

So when a stored copy is built at a bad moment — mid-update, or while a plugin was misbehaving — that broken snapshot gets served to every visitor until something clears it. Yours never was. The same split shows up with styling files that failed to update, and with anything that behaves differently for logged-out visitors.

What you can safely try

  • Look at your site in a private browser window. It's the most useful first check, and it only takes a moment.
  • Ask the person who reported it what they saw and on what device — a screenshot is worth a lot here.
  • Clear your caching plugin's stored pages if you have one and know where the button is. This alone often fixes it.
  • Check whether it started right after an update. That timing points straight at the cause.
  • Don't stack more caching or optimization plugins on top to try to force it. Layers of caching fighting each other is how this problem gets much harder to unpick.

When to call us

The repair is finding which layer is holding the bad copy, clearing it in the right order, and fixing whatever produced it — so it doesn't quietly happen again next month. If your site is showing visitors something you can't see, we'll sort it out and make sure the same snapshot doesn't come back.

Common questions

How can I see what visitors actually see?
Open your site in a private or incognito browser window, which loads it as a stranger with no login and no saved files. Checking on a phone using mobile data rather than your home wifi is another quick way to get a genuinely fresh look.
Why does being logged in change anything?
Most caching setups skip the cache for logged-in users, so you're served a freshly built page every time while visitors get a stored copy. That's deliberate and useful — but it means you're the last person to notice when the stored copy goes wrong.

Want this fixed for you?

Emergency WordPress Fixes

From $149, flat rate. You approve the price before we start.

Not an emergency? Get a free audit of your site, done by a person, no obligation.