My website has stopped working.

What you’re seeing

Your site is down, blank, stuck on an error message or showing something that clearly is not right. Perhaps customers have told you they cannot open it. Perhaps the homepage works but the booking form, checkout or admin area does not. You may not know what changed, and you should not need to diagnose it before asking for help.

If the site is part of how people find, trust or contact your business, even a short outage matters. I start by establishing what visitors can see, when the problem began and whether it affects the whole site or one part of it. That gives us useful facts without making you translate technical language.

What usually causes it

A site can stop working because a hosting service is unavailable, a domain or SSL certificate has expired, an update has conflicted with older code, or a server has run out of a resource it needs. A broken plugin, a changed password, a DNS edit or a compromised website can produce very similar symptoms.

That is why I do not begin by reinstalling things or changing several settings at once. Guessing can hide the original fault and make recovery harder. I check the domain, DNS, certificate, server response, logs and recent changes in a sensible order, then isolate the failing layer.

What I’d do

First I confirm the failure and preserve what is there. If I have access, I take or verify a backup before making risky changes. I then reproduce the problem, inspect the relevant logs and identify the smallest safe fix. That might mean correcting DNS, renewing a certificate, rolling back one update, repairing code, restoring clean files or working with your host.

I will tell you what I found in plain English, what I recommend and what it will cost before I begin paid work. If there is a temporary way to restore the important part of the site while a permanent repair is prepared, I will explain that option too.

Urgent outages are triaged as soon as availability allows. A straightforward configuration problem may be resolved in one session; a damaged or compromised site can take longer because it needs to be checked rather than merely made visible again. Once it is working, I test the public pages and key actions, document what changed and point out any practical step that reduces the chance of a repeat.