What to check, in what order, when something stops working - on WordPress, Drupal, your own application or the server underneath. Written from the cases that actually reach us.
Drupal 10 stops receiving security fixes on 9 December 2026. If your site runs on it, you have weeks left to decide - and the cost depends mostly on which version you are starting from.
Read the guideMost failed AI projects do not fall over on the technology, but on the choice of process. So we start with what is countable and repetitive, not with what looks most impressive.
Read the guideA slow site is never one fault, it is the sum of several. We start by measuring, because without that optimisation is guesswork - and usually speeds up what was already fast.
Read the guideInstead of your site, visitors get a red warning and have to click through "proceed anyway". Most of these cases are an expired certificate or a renewal that never finished.
Read the guideA migration goes well or badly depending on the order of the steps. The most expensive mistake is switching DNS before checking that the site works on the new server at all.
Read the guideVisitors land on somebody else's site, and Google shows spam where your offer used to be. That is a break-in, not a fault - and cleaning the files alone will not hold.
Read the guideHTTP 500 is the server saying something interrupted the code. On its own it tells you nothing - the whole job is getting to the log.
Read the guideInstead of your site you get blank white. It is one of the most common symptoms, and in most cases it can be defused in a quarter of an hour.
Read the guide