A slow website loses customers. A website that is down loses customers and, if it happens often enough, its place on Google. That second part is the bit nobody warns you about.

Most business owners treat downtime as a technical inconvenience. The site was off for twenty minutes on Tuesday, it came back, no harm done. I understand why it feels that way. When you cannot see the damage, it is easy to assume there was none.

But I run operations, and I can tell you the outage is only half the story. The other half is a signal you are sending to Google's crawler, over and over, every time it knocks and finds nobody home. Reviewing our monitoring dashboards this morning, that gap between what an owner sees and what the crawler sees is exactly the thing I wish more people understood. So let me lay it out.

What Google Sees When Your Site Is Down

When Googlebot requests one of your pages and your server is overloaded or offline, it does not get your content. It gets an error, or it gets nothing. Do that once and Google shrugs. Do it repeatedly and Google adjusts.

Google's own crawling documentation is direct about this. Its infrastructure reduces how often it crawls a site when it encounters a significant number of URLs returning 500, 503 or 429 status codes ^[1]. The amount of attention Google gives your site, what its engineers call the crawl budget, drops when your server is slow or unreliable ^[2].

So what does a reduced crawl rate mean for a business owner who has never heard the phrase? It means the new prices you deployed last week, the updated opening hours, the page about your new service, all of it sits unseen for longer. You changed the shop window. Google has not looked yet, and now it is looking less often.

It gets sharper than that. Google states plainly that if Googlebot observes those error codes on the same URL for multiple days, the URL may be dropped from its index ^[1]. Dropped from the index means gone from search results. Not ranked lower. Not there at all. Google cannot rank a page it has decided is no longer reachable.

The Customer Who Will Never Come Back

The ranking damage is slow and quiet. The customer damage is immediate, and you almost never witness it.

Picture this, because it happens far more often than anyone admits. Someone searches for exactly what you sell. You are ranking well, so they tap your result. They get a spinning wheel, then a blank page, then a browser error. They do not email you. They do not ring to let you know. They tap the back button and choose the next business in the list. The whole thing takes four seconds.

We already know how little patience people have here. Think with Google's research found that more than half of mobile visits get abandoned when a page takes longer than about three seconds to load, and the probability of someone bouncing climbs steeply as the wait grows ^[3]. Treat those as averages rather than gospel, because they vary by device and connection. But the direction is not in doubt. A blank page is the slowest load of all. It never finishes.

Now put a real business in that scenario. A Limerick accountancy firm during the self-assessment deadline, when half the county is Googling "accountant near me" at 11pm. If the site is down for that evening, those are not abandoned page views in a report somewhere. Those are clients who rang the competitor instead.

The outages that hurt most are the ones that happen while nobody is watching the line.

Why You Never See It Happen

Here is the cruel part of downtime. It rarely happens while you are sitting at your desk watching.

It happens at 2am during a traffic spike. It happens on a Bank Holiday Saturday when a plugin update collides with a memory limit. It happens during a maintenance window your host scheduled and never told you about. By Monday the site is back, the dashboard is green, and there is no trace of the three hours it was unreachable on Sunday night, right when your weekend customers were looking.

That invisibility is why uptime gets treated as a non-issue. You cannot worry about a problem you have no way of seeing. This is also where the proper foundations matter more than any single feature, and it is worth understanding the full picture of what actually makes a WordPress site fast and reliable rather than chasing one metric. Speed and uptime are the same conversation from two directions: one is how quickly the page answers, the other is whether it answers at all.

I will admit where this caught me out. Years ago I trusted a monitoring setup that was checking the wrong thing. It pinged the server, got a healthy reply, and reported everything green, while the actual website was returning an error to every real visitor. We found out from a customer, not the dashboard. We rebuilt how we monitor after that. Now we verify what the visitor sees, not just whether the box is powered on.

The Honest Version, Including What Downtime Does Not Do

I am not going to tell you that every outage is a catastrophe, because that would be the sales-pitch version and you would be right not to trust it.

A one-off twenty-minute outage is very unlikely to move your rankings. Google is genuinely forgiving of the occasional blip, and there is a correct way to handle a planned maintenance window: return a 503 status code with a Retry-After header so the crawler knows the downtime is temporary and comes back later, rather than assuming the page is gone ^[4]. A well-run host does this for you automatically. Done properly, a short maintenance window costs you nothing in search visibility.

The danger is not the single outage. It is the pattern. Small, repeated, unnoticed outages on infrastructure with nobody behind it. That is what trains Google to crawl you less and, eventually, to doubt you are there at all.

And to be fair about the other side of it: if your website is a static brochure you update twice a year, and every customer you have ever had came by word of mouth or the phone, the SEO cost of downtime barely touches you. For that business, cheap hosting is genuinely fine and I would not try to talk you out of it. But if any meaningful slice of your custom arrives through a Google search, your uptime is not an IT footnote. It is a marketing asset you are paying for whether you realise it or not.

What Actually Keeps a Site Up

A real solution is not a bigger number on a sales page. It is a set of behaviours. Monitoring that checks what the visitor actually sees, not just whether the server responds. People who notice an incident and respond to it quickly, at the hours when outages really happen. Correct status-code handling during maintenance so the crawler is never misled. Caching and resources tuned so a busy Saturday does not become an outage in the first place.

An alert tells you the site is down. It does not keep it up. The thing that keeps it up is the operations work that happens before any alert fires.

That is the standard worth holding any host to. It is also exactly what Web60 is built around: monitored, enterprise-grade infrastructure on sovereign Irish cloud, run by an actual operations team in your own timezone, all of it included in the kind of properly managed hosting that treats uptime as a job rather than a marketing claim. You should not have to think about crawl budgets and 503 headers. That is our work, not yours.

The Real Lesson

Stop reading uptime as a technical detail and start reading it as visibility. Every hour your site is unreachable is an hour Google cannot crawl you and a customer cannot reach you, and the two compound. The outage you never saw on Sunday night is the ranking slip you cannot explain on Friday.

The next time you weigh up hosting, do not ask what uptime percentage they promise. Ask who is watching the line at 2am, and what happens when it drops. That answer tells you far more about your place on Google than any number on a sales page ever will.