A WordPress outage is fixed by a WordPress developer or by whoever runs your ongoing technical care - and that is not always the same person who built the site. Fixing WordPress means finding the element that blew up (usually a plugin, the theme or a server setting), disconnecting it and getting the site running again without losing content or orders. A typical outage is hours of work, not days: a simple conflict after an update usually goes away the same day, while more serious cases - an infection, a corrupted database, dead hosting - can take from one to a few working days.
Below it is laid out practically: what to do in the first fifteen minutes, who to turn to for which symptom, how long it takes and what access to prepare.
What to do in the first 15 minutes
Before you start looking for help, gather the facts - that shortens the repair more than anything else. Someone who receives a complete set of information starts with diagnosis rather than an interrogation.
- Write down the exact message - a screenshot of the whole window, including the address bar. “It does not work” is not enough, “There has been a critical error on this website” is already a lead
- Check whether the whole site is down or only part of it - home page, an inner page, the cart, the
/wp-adminpanel. Open each one - Check in a private browser window and on your phone - sometimes it is only cache on your side
- Recall what changed - a plugin update, a new plugin, a PHP version change, an expired domain, an expired certificate, a late hosting payment
- Look in the admin mailbox - on a serious error WordPress sends an email naming the guilty plugin with a link to recovery mode. Check spam too
- Do not delete anything - do not remove plugins, do not reinstall WordPress, do not “clean up” files on the server
That sixth point is the most important. Most repairs that end up expensive are expensive not because of the outage itself, but because of nervous moves made before help arrived.
Who actually fixes WordPress
There are four doors worth knocking on, and each has a different scope. Here is who handles what:
| Who | What they will actually fix | When it is the best choice | Typical response time |
|---|---|---|---|
| Hosting support | The server, PHP version, memory limits, the SSL certificate, restoring from their backup | The site reports a server error, the host writes about a problem themselves, the certificate expired | From tens of minutes to a day, depending on the plan |
| Plugin or theme author | A bug in that specific plugin, if you have an active licence | You know exactly which plugin took the site down and it is a commercial one | Usually 1-3 working days, in English |
| WordPress developer | Everything: conflicts, the theme, the database, an infection, integrations, WooCommerce | Nobody knows what happened, or the problem touches the store and money | From hours to one working day |
| Ongoing technical care | The same as above, only before you notice | The site earns money and downtime costs more than the retainer | The response time is agreed up front in the contract |
In practice the most common mistake looks like this: the store has been down for three days because the owner is waiting for a reply from a plugin author abroad. The plugin can be switched off in five minutes with a workaround put in its place, and the author’s fix can be applied calmly a week later. In an outage you restore sales first and look for the culprit second.
How long a WordPress repair takes
Repair time depends mainly on whether the cause sits in the site’s content or in the server. The brackets below are typical working times on a site where I have normal access - they are not a promise, because two identical-looking outages can have completely different bottoms.
| Symptom | Usual cause | Typical repair time |
|---|---|---|
| Critical error after an update | A plugin conflicting with the theme or the PHP version | Tens of minutes to 2 hours |
| A white, empty page | A PHP error with error display switched off | 1-3 hours |
| Error establishing a database connection | Wrong credentials, an overloaded or damaged database server | From 30 minutes to half a day, depending on the host |
| The cart or payments stop working | A change at the payment gateway, a plugin conflict, an expired API key | 2-4 hours |
| The site suddenly “very slow” | A bloated database, no caching, exhausted hosting resources | Half a day to two days |
| Foreign content, redirects, a Google warning | An infection - it has to be cleaned, the way in closed and the site submitted for review | 1-3 working days plus waiting on Google |
| The site has vanished completely, no backup | A deleted hosting account or an expired domain | From a day upwards, sometimes unrecoverable |
Two notes on that table. First, a backup shortens almost every row to tens of minutes - which is why “do you have a backup” is always the second question asked, and how to set one up properly I covered in the piece on WordPress backups. Second, with an infection the technical repair is half the job - the rest is getting the search engine warning removed, and that moves at Google’s pace; the order of the steps is laid out in the rescue plan for a hacked site.
What to prepare so the repair can start immediately
The person fixing the site needs three things - and that is usually what the waiting is for, not the work itself.
- Access to the hosting panel - this is the important one. It gives files, the database, error logs and backups. Without it, fixing a serious outage is guesswork
- An administrator account in WordPress - ideally freshly created for the contractor, to be deleted after the job
- Contact details for whoever holds the domain - some outages (certificates, redirects, DNS) mean going in there
If you are missing something, do not let that block the start. Say it straight: “I only have the WordPress panel, the hosting is with the previous contractor”. You can begin with diagnosis and recover access in parallel. It is worse when this only comes out halfway through.
Signs you found the right person
In an outage you decide fast and under pressure, so it is worth knowing a few simple markers. Good WordPress technical help:
- Starts with a backup before touching anything - even when the site is already down
- Explains what happened in plain language and shows the cause, not just the effect
- Gives the scope and the price before the work, not after
- Does not propose rebuilding the site in response to an outage - those are two different conversations, and mixing them is a warning sign
- Leaves the site stable, meaning that after the repair they tell you what needs fixing so it does not come back
A red light goes on when someone immediately proposes building the site again from scratch. Sometimes that really is the right road, but almost never on the day of the outage and without looking at what is there.
What a repair costs and what drives the price
The price of a repair depends on the time needed for diagnosis, and diagnosis is shorter the more is known about the site. A minor outage after an update is a different order of magnitude from cleaning an infected store with a thousand products, which is why nobody honest will quote a figure over the phone without looking inside.
With me it works like this: the diagnosis is free - I look at the site, say what is broken and how much work it takes. For bigger work (a rebuild, an integration, serious cleaning) I give a quote in writing before we start, at a fixed price - projects of that kind usually land in the range of around 5,000-10,000 PLN net (Polish market rates). If outages happen regularly, ongoing technical care makes more sense than firefighting: Basic from 1,000 PLN, Pro from 2,000 PLN, Premium from 3,500 PLN net per month, with updates, backups and a response to problems before you notice them. More on the rates on the market and what you are actually paying for is in the piece on how much a WordPress developer costs.
How not to come back to this every month
An outage is almost always an effect, not a cause. The cause is often a missing rhythm: updates done in bulk once every six months, a backup nobody has ever restored, a plugin abandoned by its author two years ago, hosting chosen for a site that was small and then grew.
Three things reduce the number of outages more than anything else:
- A backup stored off the site’s server and a restore test now and then - a backup nobody has checked is not a backup
- Updates in a rhythm, with a backup before and a check of the site after - instead of two big jumps a year
- Cleaning out plugins - every unnecessary one is one more place where something can break
If you would rather first understand what you are seeing on screen, I have separate pieces on the WordPress critical error and on the white screen - both walk through the repair step by step, without any knowledge of code.
What it looks like when you come to me
I start with a free diagnosis - I look at the site, the logs and the hosting, and say straight what happened, how long it will take and whether it can be done today. If the outage is minor, it often ends with a same-day fix. If it turns out there is a bigger problem underneath - a neglected core, an infection, hosting that cannot carry the load - you get the scope and the price in writing before we begin, so no figure appears after the fact. I work personally, so you talk to the person actually inside your site.
Frequently asked questions
Who fixes WordPress sites? A developer specialising in WordPress, or whoever provides ongoing technical care. Hosting support will only fix things on the server side (PHP, limits, certificate, restoring a backup), and a plugin author only a bug in their own product, usually with a delay of several days.
How long does a WordPress repair take? A typical outage after an update takes from tens of minutes to a few hours. More serious cases - a corrupted database, an infection, no backup - take one to three working days, and with an infection you add the time Google needs to remove its warning.
Will I lose content and orders in an outage? Usually not - posts, products and orders sit in the database, which an ordinary outage does not touch. The risk only appears with rash moves: deleting files, reinstalling WordPress or overwriting the database with an old copy.
Can a site be fixed without hosting access? Partly. With just an administrator account you can switch a plugin off or swap the theme, but on a critical error the panel is often unreachable, and without server logs the diagnosis is guesswork. It is worth recovering hosting access before you need it.
Would rather not watch over it every month yourself? I take sites and stores under ongoing care - backups, updates, monitoring, and priority when something breaks. Tell me what you run and I will send back scope and price.