Your Site Is Returning 200 OK and It Is Completely Broken

Traditional uptime monitoring answers one narrow question: Did the server respond? Most basic uptime checks request a URL—often the homepage—at regular intervals. If the server returns a successful HTTP status such as 200 OK, the dashboard stays green. If it times out or returns a server error, you receive an alert. That model is useful. … Read more

WordPress Plugin Keeps Deactivating After an Update? Check the Database

WordPress Plugins Keep Deactivating at 3 AM? Check the Database There is a specific kind of WordPress problem that can waste an entire afternoon. A plugin deactivates after an update. You reactivate it. Everything looks fine. Then it deactivates again. There may be no fatal error on screen. The site still loads normally for visitors. … Read more

Debug Log

Quick answer: The WordPress debug log records PHP errors, warnings and notices to a file. Turning it on takes three lines in wp-config.php. Reading it usefully means knowing which severity levels matter, which are safe to ignore, and never leaving errors displayed on a live site. The debug log is the closest thing WordPress has … Read more

Plugin Conflicts

Quick answer: A WordPress plugin conflict happens when two plugins (or a plugin and your theme) interfere with each other — usually after an update. The symptoms range from broken layouts to complete site failure. The fastest way to catch conflicts before visitors do is to monitor plugin status changes automatically. The average WordPress site … Read more

MyISAM tables in an InnoDB world

Quick answer: WordPress database table errors — including overhead accumulation, collation mismatches, and table corruption — build up silently and slow your site before causing visible failures. Most site owners only discover them when something breaks. Almost every other WordPress problem announces itself. A broken plugin throws a white screen. A bad theme update mangles … Read more

WP-Cron

Quick answer: WP-Cron isn’t a real cron job. It only runs when someone visits your site, which means scheduled tasks on a low-traffic site can be hours late — or fire many times at once on a busy one. Switching to a server cron fixes both problems in about five minutes. If you’ve ever wondered … Read more

404 Floods

Quick answer: A 404 flood — hundreds or thousands of 404 errors generated in a short period — wastes your crawl budget, dilutes your site’s authority signals, and can cause search engines to de-prioritise your healthy pages. The most common causes are bot sweeps, deleted pages with inbound links, and broken redirects. Let’s start with … Read more

Every Plugin on the Site Deactivated Itself, Every Night, Between 3 and 6 AM

A client site started turning itself off. Not the site — the plugins. All of them. Every morning I’d get a report that something was broken, log in, and find the plugins list completely deactivated. Turn them back on, everything works, site’s fine all day. Next morning, off again. Somewhere between 3 and 6 AM, … Read more